Governance visual guide
The Orchard content lifecycle
How discovery, currency review, owner gates, authoring, release, and live verification form one governed content lifecycle.
A governed content lifecycle with discovery, currency, and request-intake lanes feeding owner Gate 1; approved work proceeds through authoring and review to digest-bound Gate 2, commit, release, and live verification, while denials stop delivery or return work for revision.
Read the visual
What this shows
The Orchard joins discovery and currency signals with an explicit request path, owner approval gates, evidence-backed authoring and review, release, and live verification. Dashed nodes distinguish designed work that is not yet implemented from running controls.
Carry this forward
Key takeaways
- Discovery and currency findings enter one governed queue.
- Owner approval gates establish delivery and publication authority.
- Designed but unimplemented steps remain visibly distinct from running controls.