Governance visual guide
The Orchard content lifecycle
How Orchard content moves from discovery, monthly currency review, or a requested topic through two owner-approval gates to a published, verified course.
Read the visual
What this shows
Discovery, the monthly currency track, and a designed request-intake path all feed one shared queue and one Gate 1 owner approval, so nothing reaches a model before the owner approves. Approved work moves through a research, authoring, and review ensemble to a second Gate 2 approval bound to the exact artifact digest; editing the artifact after that point invalidates the approval. A Gate 2 denial carries a reason and returns the work for rework. Approved work is committed, pushed, and, once wired, verified live. Discovery runs monthly on the 1st, currency review on the 15th, both at 06:00 UTC. Request intake and live verification are designed and not yet built, and only the currency track's inspection step runs today.
Carry this forward
Key takeaways
- Two gates protect the pipeline. Nothing reaches a model before Gate 1, and Gate 2 binds approval to one exact artifact digest.
- Discovery, currency review, and requested topics are three intake paths that converge on the same queue and the same Gate 1 decision.
- The diagram marks what is designed but not built: request intake, live verification, and every currency step past inspection.