This standard governs its own development.
The portfolio that builds PMO as Code is run as PMO as Code, in public. Every claim on this page is a link to the live artifact, so you can check rather than trust.
The live portfolio.
Three deployments derive their status from documents right now. The badges below are fetched live from each one; whatever they say is the current derivation, and this page has no say in it.
The governing documents.
The dashboards above are compiled from Markdown in a public repository. The sources are one click deep:
The gates, observable.
Every document change to the portfolio passes the same gate this site tells you to build, and the runs are public. The Actions history shows every audit; branch protection blocks a merge whose checks fail, whoever authored it.
One complete chain, followable end to end: the scope for this site's rewrite was approved by merging a documents pull request, the merge scaffolded the delivery stories within seconds, the delivery pull request closed the stories on merge, and the features closed themselves when their last story did.
The colors are derived.
Whatever color the checks derive at build time is the color the dashboards show. A project lead can flag a concern and pull a color down; nothing anyone types can turn a failing derivation green. If a project page shows amber when you open it, that is the state of the checks, published anyway.
The rules of that derivation have their own explainer: derived status over self-reported status.
Measured adoption.
Adoption is counted, never estimated, and published from day zero, small numbers included. This section regenerates on every deploy and at least monthly.