Training Program
One program, two tracks
The training program has a shared core everyone takes, and two tracks you pick from based on your relationship to the work.
If you are a contributor — a developer, a steward of the authoritative documents, a continuous-integration engineer — you want the Contributor track. You will come out of it able to land a reviewed change without review blockers: metadata valid, schemas green, drift scan clean, tests covering the change.
If you are an operator — a program user, an auditor, an integrator — you want the Operator track. You will come out of it able to run the discovery and drift tools against your own environment, interpret the findings, and trace every output artifact back to the authoritative source it came from.
Both tracks start at the same place: a shared core that establishes the vocabulary, the topology (authoritative documents are the source of truth; everything else is a consumer), the consumer rule, and how a change lands. Once that is internalized, the two tracks diverge into their track-specific modules.
Assessment
Training is done when you have landed a reviewed change (Contributor) or produced a clean discovery and drift run and correctly interpreted its output (Operator). The program is not a certification — it is a path to doing the real work.
Companion pages
- Education — narrative-led onboarding for anyone new to the approach
- Test plans — what tests govern what
Cleaned extraction for project use.