Concepts
Adoption stages

CSDM maturity is a journey — crawl, walk, run, fly — and a model that emits fly-stage artifacts into a crawl-stage program creates noise, not maturity. ServiceMatch stages its output to match where the program actually is.
Capture is never gated
The stage never limits what ServiceMatch learns. Stakeholder claims, evidence, and attribution are captured in full at every stage. What the stage governs is what gets emitted: which workbook sheets are produced, which service relationships ship, which structural entities appear in exports.
| Stage | What emission looks like |
|---|---|
| Crawl | Device CIs and governance artifacts — the foundation, clean. |
| Walk | Technology-management-parented service structure begins to ship; the business layer stays captured but held. |
| Run | Business-service offerings and evidence-confirmed placements ship alongside the management layer. |
| Fly | The full model, including structural capability entities, ships to the instance. |
Promotion is a decision, not a drift
Design Principle
Moving between stages is a governed operator decision that lands on the decision record. The system warns and asks; it never blocks capture and it never promotes silently.
All docs
OverviewGolden records & identitySource precedenceClassificationEvidence & reasoningUncertainty & failure modesField coverage & gapsAdoption stagesThe CSDM 5.0 modelAttribution & coverageQuality & scopeConductor & ProGovernance decisionsThe decision recordReview & overridesDeliverablesThe import packageGlossaryPoliciesDiscovery sourcesDeployment model