Governance and Compliance
Maintaining the records, decisions, and accountability the program requires.
Programs without governance drift; programs without compliance cannot prove what they do. This is a continuous practice every role participates in — not a separate department imposing rules.
Start here
Core tasks
Decision-record maintenance
Ensure every structural decision produces a decision record, linked into the canon it governs.
Steering-file discipline
Keep small, governed files describing how specific topics — credentials, security, dependencies — are handled.
Canonical-drift monitoring
Periodically compare canon to actual behavior and raise gaps.
Compliance attestation
Translate the continuous streams of evidence into the formats regulators, partners, or auditors require.
From knowing to running
Knowing SPEED and running it are two different things. When you're ready to practice the methodology inside a program that runs it, the implementor path is where you begin.
Begin the implementor path