Curriculum control

Curriculum needs versioning, ownership, delivery posture, and usage proof.

The curriculum route prepares the operating body for lessons, modules, facilitator materials, cohort use, and licensing packages.

Explore curriculum fitCommand Center brand surface
Operating proof

Curriculum is not controlled unless versions, access, use, and outcomes are visible.

WordPress role

Home, landing, trust, SEO, and public discovery entry remain on WordPress until an approved cutover.

GitHub app role

This app owns the body: curriculum pages, certification paths, cohort proof, and Command Center sync.

Circle body

What this surface now controls

Versioning

Track what curriculum version exists, who can use it, and where it has been applied.

Delivery posture

Separate self-paced, facilitated, cohort, enterprise, and certification paths.

Outcome evidence

Connect completion, assessment, reflection, and leader behavior change into proof.

Receipt targets
  • curriculum version
  • module use
  • cohort delivery
  • learning outcome
Genesis AI rails
  • Genesis App curriculum cards
  • Command Center IP usage
  • AI Brain learning summary
Next build gate

Move from public body to app-owned intake: validation, sanitized client response, server logs, receipt payload, and durable Command Center proof.