The Principia Machina/Guide/9 Publishing a specification version

The Principia Machina: map
Reading the diagrams Structure key Process key Definition of terms Roles
Reading by audience Start here: the walk through The operator's guide Tutorial: create a UUID Workspace Container (UWC) Public Recorder inputs Sponsors: your first agent
The specification Contents: parts, tables, diagrams TPS 0.5.0 (declared 2026-10-03, revision 8; machine-optimized text) Decisions (the foundations record, one line each)

The operator's guide. It assumes the walk; a newcomer should read that first. Each page opens with its diagram, states its purpose and scope, gives the procedure, names what it does not cover, works one example, and links the sections of the specification that govern it. Where this guide and the specification differ, the specification governs.

The five layers the specification governs; every published version covers all five. (diagram page.)

Purpose

Publish a version of the specification, keep the human pages and the machine-optimized pages consistent with it, and index the implementations that conform to it.

Scope

The version tree, the file digest, the genesis line, D(IS), the contents page, the diagram set, implementations, the import path. Not covered: authoring the rules.

Procedure

1. A specification version is one file with a terminal sentinel. Compute its SHA-256 with a tool; never type a digest.
2. Publish it as a root page and one page per content unit, verbatim in pre blocks, under a title that carries the version. A later version is a new page tree; the old one is never edited.
3. The declaring authority lands the genesis line, the digest and version, on the DECLARATIONS page. From then on D(IS) is TPX's digest over that published version, published on the hub and in the badge.
4. Every implementation of the agent contract is indexed with its name, version, digest and the specification version it conforms to. Implementations are not normative and sit outside D(IS).
5. Update the human layer against the new version: the contents page, the diagram set (re-keyed addresses; STATUS re-stamped), the keys, the terms, the walk and this guide. Re-render, re-import.
6. Import through Special:Import from a single export file; assign edits to local users; upload renderings separately if static images are wanted.
7. Declaring a calculator version follows the same pattern as step 4: compute its digest with a tool, publish the source under the plain-text content model, and land the index entry by declaration. The calculator decides nothing; a compiled build of it is never of record.

Checklist

• Sentinel present; digest from a tool; genesis line landed by the declaring authority.
• No page of an old version edited.
• Hub's specification section names the current version as normative and the implementations as implementations.

Non-goals

Publishing does not certify anyone; a changed D(IS) lapses every certificate and the agents re-certify (guide 7).

Worked example

TPS 0.1.0 is published as 46 pages with its digest on the root page; the declaring authority has not yet landed the genesis line, so every page says "proposed". A rename is decided. The file is revised, the digest recomputed, the pages re-sliced and re-imported as revision 2 of the same proposed version, because nothing has been landed. Once the genesis line lands, that freedom ends: the next change is 0.2.0, a new tree.

Governing sections: TPS 0.1, TPS 5.11, TPS 5.14, TPS 6.1.

---

Previous: Index, chain, badge and recovery. End of the guide. Contents of the specification.