Jump to content

Guide 9: Publishing a specification version

From The Invariance Itself
Revision as of 05:42, 25 September 2026 by DeltaS Zero (talk | contribs) (Guide 9: the version-free page tree (D55) and the actual history (revision 4 declared final 2026-09-22; a later revision imports onto the same titles); the walk through)
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 through; 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 version-free titles. A later version is a new revision of the same pages, imported onto the same titles; an earlier version is read from a page's history, not found at a separate title.
  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 through and this guide. Re-render, re-import.
  6. Import through Special:Import from a single export file, every revision stamped later than its page's latest revision; assign edits to local users; never re-run a completed import; 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.
  • Every imported revision stamped later than its page's latest revision; no completed import re-run.
  • 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 was published on 2026-09-16 as a page tree whose titles carried the version, with its file digest on the root page, every page saying "proposed". While nothing had been landed, the file was revised, its digest recomputed and the pages re-sliced and re-imported as revisions 2 and 3 of the same proposed version. On 2026-09-21 the tree was moved to version-free titles, every page keeping its history and leaving a redirect; on 2026-09-22 revision 4 was imported onto the moved titles and the declaring authority declared version 0.1.0 final. A later revision, revision 5, is imported onto the same titles as a new revision of each page. The genesis line waits for TPX's first landing; once it lands, that freedom ends: a change of the rules is a new version, 0.2.0, on the same titles.

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.

Retrieved from "https://invarians.org/index.php?title=The_Principia_Machina/Guide/9_Publishing_a_specification_version&oldid=3248"