Declarative sources of truth over hand-maintained artifacts.
A declarative source states what is true in one authoritative place. A hand-maintained artifact restates it, and the two begin to disagree the moment the copy is saved.
The shift: declare once, converge everywhere.
Infrastructure as Code settled this argument for servers years ago: you declare the state you want, and tooling makes the world match. PMO as Code applies the same posture to the portfolio. The documents declare what is true, and every other surface is computed from them.
Frontmatter declares a document's identity, status, and dates. Items declare the requirements, risks, and tests. Typed links declare the reasoning between them. None of it is prose that a reader must interpret; all of it is structure that a pipeline can check.
# frontmatter declares; nothing downstream is typed by hand id: AUR-charter kind: charter project: PRJ-001-AUR status: approved dates: target: 2026-12-31
Everything else derives.
Once the sources are declarative, the artifacts people used to maintain become build outputs. Each of these is live in the reference deployments today:
Where hand-made artifacts still belong.
Judgment is authored, and it should be. A charter's objective, a risk's mitigation, a post-implementation review's lessons: people write those, in the documents, where the history lives.