v1
Share

Press & share kit.

Facts you can verify, copy you can quote, boilerplate you can paste, and images of the real product. The chips below are claims; each one links to the artifact that backs it.

The ten-second version.

“Project status is a build artifact.”
That is the whole idea. For status to be built rather than reported, the documents underneath it have to be structured, tested, and gated. The tool that does the testing is docassert: “unit testing for business documents.”
Boilerplate · 50 words
PMO as Code makes project status a build artifact. Charters, BRDs, and risk registers live in Git as structured Markdown. Changes are tested and cannot merge until they pass, and the passing documents compile into red, amber, or green. There is no field where anyone types a status.
Boilerplate · 100 words
PMO as Code is an open standard for running a project management office from version-controlled files. Business documents (charters, BRDs, PRDs, risk registers) are structured Markdown with schemas and audit criteria, validated on every pull request by docassert, the Apache-licensed reference implementation. Requirements carry stable ids and typed links, which turns “which requirements have no test?” into a query. Project status is compiled from the documents and published as a live dashboard with no edit button. The project runs its own portfolio this way, gates and all, in public repositories, so every claim it makes about itself can be checked.

Assets.

Free to use when covering the project. The dashboard screenshots are captures of live pages, taken with whatever states the portfolio actually had that day.

Download everything (zip, ~0.5 MB) ↓

The live portfolio dashboard — five projects, derived health
Portfolio dashboard
PNG · 2880×1800 · live capture
↓ file
A project status page — verdict, coverage, risk matrix, sequence chart
Project dashboard
PNG · 2880×1800 · live capture
↓ file
PMO as Code social card
Social card
PNG · 1200×630
↓ file
PMO as Code logomark on dark
PMO as Code logomark on light
Logomark
SVG · scales to any size
↓ file
Animated demo: a weak charter is blocked, fixed, and cleared
Demo animation
SVG · animates in-place
↓ file
# PMO as Code — fact sheet
- One-liner: project status is a build artifact
- Tool: docassert, stable 1.x, Apache-2.0
- Spec: v0.8 · 73 conformance cases
- Contact: [email protected] …
Fact sheet
Markdown · plain text
↓ file

Three story angles.

01Infrastructure-as-Code, pointed at the PMO

DevOps solved “the wiki is stale and the spreadsheet lies” for infrastructure a decade ago. Declare truth in files, validate every change, derive state instead of reporting it. PMO as Code points that playbook at project governance, with the same Git and the same gates.

The principles →
02It governs itself, and you can check

The portfolio that builds PMO as Code is run as PMO as Code: five projects, every scope change through a gated pull request, a public dashboard rebuilt from the governing documents on every merge. A skeptical reader can audit any claim from their couch.

The live portfolio dashboard →
03Dashboards that can’t lie

There is no text box for status. Coverage comes from the traceability graph, risk from a scored register with a declared appetite, delivery from real issue states, and an amber page has to say why it is amber. A real project converted from a Word BRD shows the whole loop running.

The case-study dashboard →

Press boilerplate.

Third-person paragraphs for the foot of an article, usable verbatim without approval. The launch press release is on the news feed. Media contact: [email protected]. Release-tied announcements run on the news feed (RSS).

About PMO as Code
PMO as Code is an open, vendor-neutral standard for running a project management office from version-controlled files. Business documents live in Git as structured Markdown, every change is tested and gated before it merges, and project status is compiled from the documents rather than reported by hand. The standard, its specification, and its reference implementation are Apache-2.0 and free to adopt at pmoascode.com.
About docassert
docassert is the reference implementation of PMO as Code: a command-line tool that validates business documents the way a test suite validates code. It reached a stability-guaranteed 1.0 in July 2026, is installable from PyPI, and ships the schemas, audit criteria, templates, and delivery profiles of the standard. Details at docassert.com.
About the author
PMO as Code was created by John Tanner, founder of C4G Enterprises Inc. His career spans kicking off a DevOps movement at the White House Communications Agency, development-practice consulting for Fortune 500 companies worldwide, delivery modernization at Freddie Mac, and leading the PMO at a Fortune 200 company. He publishes the standard and its tooling as open source.

Share copy.

A neutral blurb anyone may share as their own. The numbers in it are real.

SHORT · X / MASTODON / BLUESKY
Your project charter should fail CI.

PMO as Code: business documents as version-controlled Markdown, unit-tested on every PR, status compiled instead of typed. The tool (docassert) just hit stable 1.0. Apache-2.0.

pmoascode.com

Fact sheet.

What it isA vendor-neutral standard for running a PMO from version-controlled files. Business documents are structured Markdown, validated like code on every change. Requirements trace end to end, and project status is compiled from the documents.
The tooldocassert · Python 3.10–3.14 · pipx install docassert · brew install c4g-john/tap/docassert
The scopeTwenty-one document kinds. Two tiers of checks: deterministic structural checks gate the merge, and AI-graded semantic checks only advise. An execution bridge turns approved stories into GitHub issues, and the dashboards are compiled from the documents.
The caveatThe tool is stable at 1.0. The specification is v0.8 and still a draft; its conformance rules may tighten before a spec 1.0.
WhoJohn Tanner, C4G Enterprises Inc. · linkedin.com/in/tannerjs · why he wrote this
Press contact[email protected]
Names“PMO as Code” is the standard. The tool is lowercase “docassert”, tagline “unit testing for business documents”.