Tutorial 8: After the declaration

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)

Tutorial: create a new UWC. One small example - a mass on a linear spring, moving only along x - is taken from a blank file to a declared UWC in eight steps. Each step says what runs today and what is specified but not yet built. It explains; the specification governs. Field-by-field reference: Public Recorder inputs.

A change to the TFK is a new UWC: new UUID, new prefix, records inherited as PROVISIONAL. (diagram page.)

Purpose

What changes for you once the UWC exists, and what to do when you want to change it.

Explains: TPS 0.1.0, revision 4 (declared final 2026-09-22); the zone schemas the declaring authority selected on 2026-09-22 (records D92.1, D98.1, D99.1, D100.1, and for units D103.1, D104.1, D105.1; schema 0.3.0), whose text enters TPS at revision 5, and the kernel tests and isomorphism checks selected the same day (D106.1, D107.1, D108.1; tpm_kernel_tests 0.2.0), whose text follows at the next TPS revision; TPC-PY as built 2026-09-22 (tpc_zone 0.3.0, tpc_units 0.1.0, tpc_tests 0.1.0; no TPC-PY version is declared yet) with check_draft 0.3.0. Where this page and the specification differ, the specification governs.

What you can still do

Keep the access list of a CLOSED UWC. That is H-OWN's one right (the access list).
Put work into the register through the RR input buffer. Certified agents work it; TPX writes the records (register records).
Read everything: every page of every UWC is public.

What you cannot do

Edit the TFK. The pages are protected, the digest gate checks them before every write, and an attempt to change them is refused and redirected to the new-container form (TPS 5.5).

Changing the kernel: copy-forward

A change to the TFK makes a new UWC with a new UUID and a new prefix. Copy-forward carries the old register across: inherited records enter PROVISIONAL, refuted ones stay refuted, and each keeps a pointer back (TPS 3.4). The digests say what kind of successor it is (TPS 2.1). On the example:

K written "2" -> "3"       YARDSTICK_ONLY
  D(TPK) unchanged
  D(TrM) unchanged
  D(TMS) moved
damping law added to N2    KERNEL_CHANGED
  D(TPK) moved
  D(TrM) unchanged
  D(TMS) unchanged

Only a change of meaning moves a digest: respelling a decimal, reordering a dimension or respelling a unit gives IDENTICAL.

If the digest gate halts

Every write stops and the zone is named. The declaring authority chooses RESTORE (return the TFK pages to the revision the chain names) or FORK (copy-forward under a new TFK). The choice is never an agent's (TPS 2.5).

Retirement

A retired UWC stays in the index in state RETIRED, read-only, and its records stay citable.

Where to go next

The operator's guide, from guide 4 onward, covers work under the lock, landing, audits and recovery.

Non-goals

Nothing on this page reopens the TFK. There is no in-place amendment of a kernel.

Worked example

Months later the spring UWC's author wants a different multiplier K for the contradiction test. That changes only the Measure Set: a yardstick-only successor, which the re-audit may treat more narrowly (TPS 4.1). Adding a damping law changes the kernel itself: a full successor.

Governing sections: TPS 2.1, 3.4, 5.5 and 2.5.

Previous: 7 Inspect, submit and declare.