5.11 The index of record (TPS 0.2.0)

Instruction artifact, machine-optimized text: TPS, section 5.11 The index of record. Part of TPS and the TPM hub. Human-only edit (TPS 5.13). TPS 0.1.0 was declared final at revision 4 on 2026-09-22, a version declaration recorded in the foundations record; the chain begins at TPX's first landing (TPS 5.6.7). TPS 0.1.1 changed only the status lines. This page is revision 5 of the tree, proposed as version 0.2.0 until H-DECL declares it. The text below is this section of the TPS artifact at 0.2.0 (proposed), verbatim; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map.

TPS 5.11  THE INDEX OF RECORD
purpose: form, genesis, entry, scope, construction and its assertions,
         retirement; the library pages and the hub entry points; the
         class for implementations
governs: 5.11 | version: 0.2.0 (proposed) | class: instruction artifact
audience: operator, agent

5.11.1 Form: one MANIFEST page per container carrying the badge; one
       LIBRARY page per container; one CENTRAL HUB with one named entry
       point per audience; one global DECLARATIONS page; one global
       BUILD CHAIN page. [I-116] [I-011]
5.11.2 Genesis: the DECLARATIONS page's first line is the digest and
       version of TPS itself. [I-117] [C-22] [F2] [DI-1.1]
5.11.3 Entry: title, content hash, and, for the local instance, the
       archive it is held in. A page is identified by title plus content
       hash. [I-118]
5.11.4 Scope: all classes - TFK pages, register volumes, spine, CAC
       certificates, the two chain pages, instruction artifacts with
       version and STATUS (TPS; the class over which D(IS) is computed),
       implementations with name, version, digest, the TPS version
       conformed to, and STATUS (outside D(IS)), documentation pages
       with the version they describe, the community ledger's volumes
       and the community views (5.9.13), the score and user pages of
       the restricted class by title and digest (CR11, CR12), and the
       public dossier pages (5.3.27). Documentation is an escalation
       target for its own class only; so is an implementation, and so
       is a community view. A DRAFT UWC enters the index at
       instantiation. [I-119] [B-09] [C-21] [DI-3.1] [D119.1] [D122.1]
       [D127.1] [D128.2a]
5.11.5 Construction: by TPX only, at the end of every landing. TPX reads
       container pages through the API, computes digests, asserts every
       page present, no hash collision, prefix unique, and D(TFK) equal
       to the certificate, writes the manifest and appends the build
       chain line. Any failed assertion writes nothing and leaves a dated
       sentinel page. The local manifest of PRB's working copy is rebuilt
       on every local write; the badge is written last. [I-120] [B-08]
5.11.6 Retirement: a retired container stays in the index in state
       RETIRED, pages protected read-only; the index grows monotonically.
       [I-121]
5.11.7 A LIBRARY PAGE for every container, reachable from a CENTRAL HUB.
       The hub carries one named entry point per audience - general
       reader, human operator, AI agent - each opening that audience's
       page set. The hub publishes the current D(IS). [B-28] [B-09]
5.11.8 The CENTRAL HUB is the index of record: it supplies as escalation
       targets one LIBRARY PAGE and one MANIFEST PAGE per container, the
       DECLARATIONS page and the BUILD CHAIN page; built by TPX; mirrored
       in the local working instance. [I-011]
5.11.9 Index class TPC-PY source. Entry: name, version, digest, and
       the TPS version it conforms to. Non-normative; outside D(IS), as
       implementations are (see 5.11.4). Each version enters by a
       declaration of H-DECL. [D43.1]
5.11.10 A redirect is a page with content and is EXCLUDED from the index
       as a class. Redirects left at old titles when the tree is
       restructured are kept, so citations to those titles resolve, and
       are not indexed. [I-156] [D55]
5.11.11 THE MANIFEST TREE (D141.1). The manifest, and any index of volumes, is
       a MANIFEST TREE of fanout MANIFEST FANOUT, a tuning option (20). A
       landing rewrites, once each, the nodes on the path from every volume it
       changed to the root, a status write into a FROZEN volume included; no
       other node is rewritten. The badge sits on the tree's root and is
       written last. 5.11.1's form reads with it: one MANIFEST TREE per UWC,
       its root carrying the badge, and the two chain pages as CHAIN HEADS
       over APPEND VOLUMES (5.6.10). [D141.1]
5.11.12 SCOPE, AMENDED (D140.1, D141.1, D142.1, D148.1, D151.1, D167.1). The
       index lists the register's volumes, the chain heads and their APPEND
       VOLUMES, the MANIFEST TREE's nodes, the top performer page and its
       monthly snapshots (5.19.1), the FALCON PAGES and the FALCON LOG's
       volumes (5.20.12, 5.20.19), the restricted falcon pages by title and
       digest (5.20.15, 5.20.16), and, as documentation pages with the version
       they describe, "The Principia Machina/Foundations record" (split by
       section if it nears the post-expand limit, marked DATA) and "The
       Principia Machina/Decisions" (one line per D-number, generated by
       script) (8.1.10). Documentation is an escalation target for its own
       class only (5.11.4). [D140.1] [D141.1] [D142.1] [D148.1] [D151.1]
       [D167.1]
5.11.13 SCOPE, AMENDED (D171.1, D173.1). The index lists each UWC's
       BIBLIOGRAPHY VOLUMES by title and content hash, "<UWC
       root>/Bibliography/Volume <v>" (5.21.3); the MANIFEST TREE's leaf
       for a volume carries the page's content hash, as for every page,
       and no per-entry digest list, each entry's digest standing in its
       own text (5.21.5). A status write into a bibliography volume
       rewrites that volume's path (5.11.11). [D171.1] [D173.1]

Pages named in 5.11.12, added by landing round 7's page batch: Foundations record; Decisions.