Canonical public release
Architecture v1.0.1.
The first canonical public edition of the Agentic PMO reference architecture: clear enough to enter in one session, structured enough to challenge and implement.
01 / Public source
One canonical release.
The public repository is the source of truth for this edition. A future public architecture release gets its own tag and release page; earlier releases remain readable and are not silently overwritten.
| Field | Value |
|---|---|
| Repository | PMO-City/agentic-pmo-architecture |
| Release | v1.0.1 |
| Edition root | architecture/v1.0/ |
| License | CC BY 4.0 |
| Public treatment | Readable edition with explanatory website mirrors; not an independent standards body. |
02 / Public scope
A deliberate first slice.
The first public release prioritizes comprehension, traceability, and evaluation. It omits unpublished implementation detail and does not claim universal certification.
Category definition, operating loop, human–AI boundary, audience paths, and current baseline.
Public overview of the nine-node loop, constitutional principles, and reading paths.
Claim boundary. Evaluation remains a scoped, evidence-backed question—not a certification label. State the version, responsibilities, scenarios, limits, evidence, exceptions, and review date.
03 / Contribution
Contribute like a regular GitHub project.
For now, keep it simple: open an issue for a question or challenge, or a pull request for a correction, example, documentation improvement, or accessibility fix.
Before submitting: stay within the public scope, do not include private material or credentials, distinguish aspiration from evidence, preserve the nine-step loop and human authority, and explain any change that could affect meaning. Read CONTRIBUTING.md · Open an issue · Review pull requests.
04 / Release evidence
Every release leaves a trail.
The public repository carries scope, governance, license, and release notes. The website adds readable mirrors, navigation, and a worked-example entry point.
Public edition: release v1.0.1 · worked example · machine-readable release metadata
05 / Evolution
New meaning gets a new version.
Patch versions correct or clarify without changing meaning. Minor versions add backward-compatible extensions. Major versions may change architectural meaning and require migration guidance.
The current public site is a draft review publication. Production promotion remains a separate, explicitly authorized decision.