The Principia Machina/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 spring, moving along one line, with nothing else in its world - 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.4.0 (declared final on 2026-09-30 at revision 7, and in force; it follows TPS 0.3.0, declared final on 2026-09-28 at revision 6), whose sections 2.2 to 2.5 carry the zone schemas with the optional declared form, the ROLE field, the D variable and the structure check (records D92.1, D98.1, D99.1, D100.1, D103.1-D105.1, D106.1-D108.1, D132.1, D176.1, D177.1, D179.1 and D186.1); TPC-PY 0.1.0 (declared on 2026-09-28, tree digest a00161c1b321fd66abc591209007d46a7fa6290097835060e50f381426259043, conformed TPS 0.3.0; tpc_zone 0.5.0, tpc_units 0.1.1, tpc_tests 0.2.0, tpc_form 0.2.0, tpc_eom 0.1.0; schema 0.5.0) with check_draft 0.5.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). Every result must derive from the TFK and the assumptions it declares; a result that uses a force stated neither in the kernel nor in its own declared assumptions does not stand (TPS 4.4, SR2). An initial or boundary value - where the mass starts, say - is not a law of the kernel: a result that relies on one cites it as its own ASSUMPTION record (TPS 3.2.15). A measured value of a quantity that changes along the motion is tested by machine against another only when both rest on the same initial and boundary values, written as structured SITUATION records, and state the same point AT where the value holds; any other such pair is compared by inspection (4.4.13). If the UWC opened with the first task EOM-0, that task comes first: until every DOF the structure check found without a law has one, only EOM-0 work and reproductions land, and TPX marks each such DOF settled when a record carrying its equation in declared form lands (TPS 3.3.16).
• 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). In particular, you cannot "switch on" gravity or friction in a declared UWC: a force added is a new kernel.

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: every inherited record enters PROVISIONAL and names the record it came from in its INHERITS field, and a refuted or withdrawn one is withdrawn again at once, by a withdrawal record of cause INHERITED, so it stays so (TPS 3.4). The digests say what kind of successor it is (TPS 2.5). On the example, computed with TPC-PY's own successor classification (classify_successor in tpc_zone):

K written "2" -> "3"                       YARDSTICK_ONLY    (examples/spring_succ_k3.json)
  D(TPK) unchanged
  D(TrM) unchanged
  D(TMS) moved
damping term -c_d v added to EOM_X         KERNEL_CHANGED    (examples/spring_succ_damped.json)
  D(TPK) moved
  D(TrM) unchanged
  D(TMS) unchanged
EOM_X written -x * k_s for -k_s * x        KERNEL_CHANGED    (examples/spring_succ_reordered.json)
  D(TPK) moved
  D(TrM) unchanged
  D(TMS) unchanged
gravity and the track's support declared   KERNEL_CHANGED    (examples/spring_track_draft.json)
  D(TPK) moved
  D(TrM) moved
  D(TMS) unchanged
x_max, v, C_NOZ and two forms respelled    IDENTICAL    (examples/spring_respelled.json)
  D(TPK) unchanged
  D(TrM) unchanged
  D(TMS) unchanged

Only a change of meaning moves a digest: respelling a decimal, a dimension, a unit or a declared form gives IDENTICAL. But in a declared form only the spelling is normalized, not the algebra: -x * k_s and -k_s * x say the same thing and are different kernels.

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, whose first CAC re-runs only the checks K bears on, SR3 and SR8 (TPS 4.1.9). Adding a damping term, or declaring gravity and the track, changes the kernel itself: a full successor, whose inherited records enter PROVISIONAL and are re-audited at its first CAC under the re-audit scope rule, TPC reaudit_scope: it reads which zones and TMS parameters differ and returns the checks to re-run, here every check, since D(TPK) moved (TPS 3.4.7, 4.1.9).

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

---

Previous: 7 Inspect, submit and declare.