Jump to content

Tutorial: create a new UWC

From The Invariance Itself
Revision as of 01:18, 23 September 2026 by BFP Rauch (talk | contribs) (1 revision imported)
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.

Draft and certify: this tutorial covers the first two stages. (diagram page.)

Purpose

Walk one UWC from nothing to its declaration, so that every input and every check is met once, in order, on a real example.

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 runs today, and what does not

You can do steps 1 to 6 today, on your own machine: write the draft, check it with TPC-PY, fix what it refuses, and read its digests. Steps 7 and 8 describe the specified flow on the wiki. TPX, the extension that will take the draft, and the new-container form it provides, are not built yet (implementation sequence step 3), and the DECLARATIONS page is created only at TPX's first landing. So no UWC can be declared yet. When TPX is built, steps 7 and 8 become runnable without changing steps 1 to 6: TPX runs the same checks, from the same calculator's residence of record. From then on the checker is optional for an author: a draft can go straight to the form, and TPC-PY only lets you see TPX's answer first (record D101.1; the calculator).

The steps

  1. Before you start
  2. Write the Prime Kernel
  3. Write the Translation Manifold
  4. Write the Measure Set
  5. Check the draft
  6. Fix refusals
  7. Inspect, submit and declare
  8. After the declaration

Who does what

  • You, the author - here also the initiator, who becomes the UWC's H-OWN - write the three zones and check them.
  • The declaring authority (H-DECL) inspects what no machine checks yet and declares the UWC.
  • The operator (H-OP) runs the wiki.
  • TPX computes every digest, obtains the UUID, allocates the prefix and writes the pages.

See Roles.

The example

A mass m on a spring of stiffness k_s moves along x with velocity v. The kernel also has a height z, which a constraint fixes at 0, so the motion is along x only. The linear law is asserted only for displacements smaller than x_max. It is deliberately small: three degrees of freedom, three laws, one assumption. Its four digests are fixed, so you can check your copy against them at step 5.

Non-goals

The tutorial does not teach physics or how to choose a good kernel. Its numbers are illustrative. It does not cover running work in a UWC once it exists; the operator's guide does.

Worked example

The whole tutorial is the worked example. The finished draft is on step 5.

Governing sections: TPS 5.5, 5.6 and 2.1.


Next: 1 Before you start.