DeltaS Zero: New page: a complete draft TFK that passes the gate, in pieces with a note on every field and the lists that repeat marked; Special:TpmCheck (TPX 0.2.0) starts with its blocks

2026-10-01T05:13:45Z

New page: a complete draft TFK that passes the gate, in pieces with a note on every field and the lists that repeat marked; Special:TpmCheck (TPX 0.2.0) starts with its blocks

New page

{{TPM map}}
{{DISPLAYTITLE:The TFK template}}
''A help page for anyone writing a draft Full Kernel (TFK): an author of a new UWC, an operator, or an AI agent testing The Principia Machina. It explains; the specification governs. Start at [[The Principia Machina/Inputs|the inputs index]]; for a guided walk from a blank file to a declared UWC, follow [[The Principia Machina/Tutorial|the tutorial]].''

== Purpose ==
A complete draft TFK that passes the new-UWC gate as written, shown in pieces with a note before each piece: what every field holds, which fields may be left out, and which lists repeat. The box on [[Special:TpmCheck]] starts with this draft. Run it as it is to see a passing result, then change it into your own system.

''Explains: the zone schemas of [[The Principia Machina/TPS/2.2 The Prime Kernel|TPS 2.2]], [[The Principia Machina/TPS/2.3 The Translation Manifold|2.3]] and [[The Principia Machina/TPS/2.4 The Measure Set|2.4]] (schema 0.5.0) and the gate of [[The Principia Machina/TPS/5.5 The new-container flow|TPS 5.5]]. Checked on 2026-10-01 with TPC-PY's check_draft 0.6.0 and with TPC-PHP, the calculator TPX runs: PASS in both, labelled ''structurally regular'', D(TFK) <code>d8b7fb01cff25e80820ceefbf9dd29ebe3676b45f110fb63ac5a5552edeb4a9c</code>. Where this page and the specification differ, the specification governs.''

== How to read this page ==
* The grey blocks in the three zone sections, read from top to bottom, are one JSON object: the draft. The note above each block explains it. Nothing in a note is part of the draft.
* JSON has no comments. Notes stay on this page, never in your draft: the gate refuses any field it does not know, so a field called <code>COMMENT</code> or <code>NOTE</code> is refused, not ignored.
* The notes use four marks:
{| class="wikitable"
! Mark !! Meaning
|-
| REQUIRED || must be present.
|-
| OPTIONAL || may be left out.
|-
| DEFAULT || may be left out, and then means the value shown. Written out or left out, the digest is the same.
|-
| REPEATS || a list. Write one item per thing your system has, separated by commas, as many as it needs. The order of the items changes nothing, the digest included, except in a yardstick's KEY, where order is the meaning.
|}
* '''Names''' are letters, digits and the underscore, ASCII only, not starting with a digit, and unique across the whole Prime Kernel, not only within one kind: a DOF and a constant may not share a name.
* '''Numbers''': a decimal is a string in quotes (<code>"0.05"</code>, <code>"6.674e-11"</code>); the two whole numbers N_X and S_MAX are not in quotes. The other way round is refused as the wrong type. Respelling a decimal (<code>"0.050"</code> for <code>"0.05"</code>) changes no digest.
* '''Dimensions''' are base dimensions with their exponents, the exponent always written: <code>L1 T-1</code>, <code>M1 L1 T-2</code>, <code>1</code> for a pure number. '''Units''' are SI symbols with exponents: <code>m</code>, <code>kg m s-2</code>. Both are on [[The Principia Machina/Inputs/Text and numbers|Text and numbers]].
* Field by field, in full: [[The Principia Machina/Inputs/Prime Kernel|the Prime Kernel]], [[The Principia Machina/Inputs/Translation Manifold|the Translation Manifold]], [[The Principia Machina/Inputs/Measure Set|the Measure Set]] and [[The Principia Machina/Inputs/Yardsticks|yardsticks]]. When the gate refuses: [[The Principia Machina/Inputs/Refusal messages|refusal messages]].

== What the template describes ==
A mass <code>m</code> on a spring of stiffness <code>k_s</code>, moving along the spring's axis (<code>x</code>, with velocity <code>v</code>, in time <code>t</code>), driven along that axis by a force <code>F</code> the kernel takes as given, with motion across the axis (<code>z</code>) fixed at 0, asserted only while <code>|x| < x_max</code>. It is [[The Principia Machina/Tutorial|the tutorial]]'s spring with one addition, the driving force, and with every optional part used once, so that every field of every zone appears.

The kernel is a closed world: it contains these laws and nothing else. There is no gravity, friction, air resistance or electric force in it, because none is declared. To add one, declare it: a constant and a term in a law ([[The Principia Machina/Inputs/Prime Kernel|the Prime Kernel]], first section).

One top-level field is left out: <code>MODULES_USED</code>, the list of ENVIRONMENT MODULES a draft claims. No ENVIRONMENT MODULE is declared yet, so the gate can satisfy no claim; leave it out.

== The Prime Kernel (TPK) ==
The draft opens, and the first zone begins. <code>PARAMETERS</code> is DEFAULT, with one field, <code>D_VARIABLES</code>: <code>"ONE"</code> (the default) when every derivative <code>D(x, s)</code> in the kernel is taken with respect to one variable, here the time <code>t</code>; <code>"SEVERAL"</code> for laws that change in space and in time. The six kinds that follow may come in any order, and a kind you do not need may be left out.
<pre class="tfk-template">
{
"TPK": {
"PARAMETERS": {"D_VARIABLES": "ONE"},
</pre>

'''DOF''', REPEATS: one object per degree of freedom, a variable the laws leave free to relate. NAME and DIMENSION are REQUIRED. ROLE is OPTIONAL and has one value, <code>"INPUT"</code>: a quantity the kernel takes as given, such as the driving force <code>F</code> here, which needs no equation of motion of its own. If a law takes a derivative, its variable (here <code>t</code>) is a DOF too, and no constraint may fix or remove it. Every DOF must be named in the REFS of some law (T5).
<pre class="tfk-template">
"DOF": [
{"NAME": "t", "DIMENSION": "T1"},
{"NAME": "x", "DIMENSION": "L1"},
{"NAME": "v", "DIMENSION": "L1 T-1"},
{"NAME": "z", "DIMENSION": "L1"},
{"NAME": "F", "DIMENSION": "M1 L1 T-2", "ROLE": "INPUT"}
],
</pre>

'''CONSTANT''', REPEATS: one object per named physical quantity. NAME and DIMENSION are REQUIRED. VALUE, UNIT and UNCERTAINTY are OPTIONAL, with three rules: a VALUE needs a UNIT and a UNIT needs a VALUE; UNCERTAINTY needs a VALUE, is not negative, and is in the same UNIT; the UNIT must have the constant's DIMENSION. Here <code>m</code> and <code>k_s</code> are left symbolic and <code>x_max</code> has a value. A law whose every name has a value is evaluated at the final pass and must not be false (T3).
<pre class="tfk-template">
"CONSTANT": [
{"NAME": "m", "DIMENSION": "M1"},
{"NAME": "k_s", "DIMENSION": "M1 T-2"},
{"NAME": "x_max", "DIMENSION": "L1", "VALUE": "0.05", "UNIT": "m", "UNCERTAINTY": "0.001"}
],
</pre>

'''LAW''', REPEATS: one object per statement the kernel takes as given. NAME, STATEMENT (prose), REFS and ROLE are REQUIRED; EQUATION is OPTIONAL.
* '''REFS''', REPEATS: every DOF and CONSTANT the law uses, each once, in any order. A law cites no other law.
* '''ROLE''': <code>EOM(x)</code> when the law is the equation of motion of the DOF <code>x</code>; <code>CONSTRAINT</code> for a relation the motion must keep; <code>CONSTITUTIVE</code> for a law giving a force or a material's response; <code>INVARIANT</code> for a quantity the motion keeps; <code>DEFINITION</code> for a law defining one quantity from others. Capitals, no spaces.
* '''EQUATION''': the same law in the declared form. It must name exactly the names in REFS, and both sides must have one dimension (T4). <code>D(v, t)</code> is the derivative of <code>v</code> with respect to <code>t</code>; <code>D(z, t, 2)</code> the second derivative. The grammar is in TPS 2.2.
* '''Equations of motion''': every DOF except the time, an INPUT DOF and a DOF a constraint fixes or removes needs exactly one law with ROLE <code>EOM(</code>its name<code>)</code>. Here <code>KIN</code> gives <code>x</code> and <code>EOM_X</code> gives <code>v</code>. <code>EOM_Z</code> restates the motion of <code>z</code>, which the constraint <code>C_NOZ</code> fixes, so its ROLE is <code>CONSTRAINT</code>, not <code>EOM(z)</code>. The structure check reads these at the final pass; it refuses nothing, and a missing equation is a named gap the UWC must fill first (EOM-0).
<pre class="tfk-template">
"LAW": [
{
"NAME": "EOM_X",
"STATEMENT": "m dv/dt = -k_s x + F",
"REFS": ["m", "v", "k_s", "x", "F", "t"],
"ROLE": "EOM(v)",
"EQUATION": "m * D(v, t) = -k_s * x + F"
},
{
"NAME": "KIN",
"STATEMENT": "dx/dt = v",
"REFS": ["x", "v", "t"],
"ROLE": "EOM(x)",
"EQUATION": "D(x, t) = v"
},
{
"NAME": "EOM_Z",
"STATEMENT": "m d2z/dt2 = 0",
"REFS": ["m", "z", "t"],
"ROLE": "CONSTRAINT",
"EQUATION": "m * D(z, t, 2) = 0"
}
],
</pre>

'''ASSUMPTION''', REPEATS: one object per proposition taken as given that the laws do not already say. NAME, PROPOSITION (prose) and REFS are REQUIRED; REFS REPEATS and may be empty, <code>[]</code>. One proposition each: <code>"k_s and m are positive"</code> is two claims and is refused (T2), so it is written as the two entries below.
<pre class="tfk-template">
"ASSUMPTION": [
{"NAME": "A_kpos", "PROPOSITION": "k_s is positive", "REFS": ["k_s"]},
{"NAME": "A_mpos", "PROPOSITION": "m is positive", "REFS": ["m"]}
],
</pre>

'''CONSTRAINT''', REPEATS: one object per restriction on one DOF. NAME, TARGET (the one DOF), ACTION and STATEMENT (prose) are REQUIRED. ACTION is <code>"FIX"</code> or <code>"REMOVE"</code>. FIX needs a VALUE and a UNIT with the TARGET's dimension; REMOVE takes neither. A fixed DOF keeps its Translation Manifold entry, as <code>z</code> does below; a removed DOF must have none. The TARGET must be named by some law (T5). A constraint restricts which motions the kernel describes; it declares no force.
<pre class="tfk-template">
"CONSTRAINT": [
{
"NAME": "C_NOZ",
"TARGET": "z",
"ACTION": "FIX",
"VALUE": "0",
"UNIT": "m",
"STATEMENT": "only motion on the spring axis is described: z = 0"
}
],
</pre>

'''BOUNDARY''', REPEATS: one object per region condition. Several boundaries all hold together; with none, the kernel is asserted everywhere. NAME, PREDICATE (prose, true where the kernel is asserted) and REFS are REQUIRED; CONDITION, the predicate in the declared form, is OPTIONAL, and must be decided for every value (T6). The last line closes the Prime Kernel.
<pre class="tfk-template">
"BOUNDARY": [
{
"NAME": "B_small",
"PREDICATE": "|x| < x_max",
"REFS": ["x", "x_max"],
"CONDITION": "abs(x) < x_max"
}
]
},
</pre>

== The Translation Manifold (TrM) ==
The second zone says what each DOF is in the environment the kernel describes. It has two REQUIRED parts, <code>HEADER</code> and <code>ENTRIES</code>. The header's three parts are REQUIRED too, but each is a list that may be empty, <code>[]</code>.

'''ENVIRONMENT_INVENTORY''', REPEATS: the measurable quantities of the environment, each with ENVIRONMENT_QUANTITY (a name, unique in the inventory) and DIMENSION, both REQUIRED. Every quantity listed must be identified by some entry below (IC1). Name them for what the kernel contains: a quantity called <code>height</code> suggests a gravity this kernel does not have.
<pre class="tfk-template">
"TrM": {
"HEADER": {
"ENVIRONMENT_INVENTORY": [
{"ENVIRONMENT_QUANTITY": "time", "DIMENSION": "T1"},
{"ENVIRONMENT_QUANTITY": "position", "DIMENSION": "L1"},
{"ENVIRONMENT_QUANTITY": "velocity", "DIMENSION": "L1 T-1"},
{"ENVIRONMENT_QUANTITY": "transverse_position", "DIMENSION": "L1"},
{"ENVIRONMENT_QUANTITY": "applied_force", "DIMENSION": "M1 L1 T-2"}
],
</pre>

'''SIGNATURE''', REPEATS, may be <code>[]</code>: the relations on the DOF that the identification must carry. NAME, OVER (REPEATS: the DOF it acts on) and IMAGE (prose: what it becomes in the environment) are REQUIRED. FORM and IMAGE_FORM are OPTIONAL, both or neither: FORM is the relation over the DOF, naming exactly OVER; IMAGE_FORM is the same relation over inventory quantities. With each DOF replaced by its entry's quantity, FORM must read exactly as IMAGE_FORM (IC4 (a)).
<pre class="tfk-template">
"SIGNATURE": [
{
"NAME": "time_derivative",
"OVER": ["x", "v", "t"],
"IMAGE": "d/dt maps position to velocity",
"FORM": "D(x, t) = v",
"IMAGE_FORM": "D(position, time) = velocity"
}
],
</pre>

'''TRANSFORMATIONS''', REPEATS, may be <code>[]</code>: the re-representations under which an identification stays the same, such as a shift of the time origin or a change of units. NAME and STATEMENT (prose) are REQUIRED. The last line closes the header.
<pre class="tfk-template">
"TRANSFORMATIONS": [
{"NAME": "time_translation", "STATEMENT": "t -> t + t0"}
]
},
</pre>

'''ENTRIES''', REPEATS: one entry for every DOF of the kernel except a removed one; a fixed DOF and an INPUT DOF have one too. All nine fields are REQUIRED:
* NAME, unique among entries; a measured result names it as its QUANTITY.
* DOF, the kernel DOF it identifies; ENVIRONMENT_QUANTITY, the inventory quantity that DOF is.
* DOMAIN, prose, not blank: where the identification holds.
* IDENTIFICATION, prose: the identification itself.
* FALSIFIER, prose, not blank: what would show the identification false.
* FALSIFIER_CLASS: <code>"F1"</code> (only an error in the author's own working shows it false), <code>"F2"</code> (a second party can test it from the fields alone) or <code>"F3"</code> (an external measurement could contradict it).
* BEARS, REPEATS, may be <code>[]</code>: the kernel LAW and CONSTRAINT names this entry carries into the environment.
* DIMENSION: equal to its DOF's and to its quantity's (IC4 (b)).
No DOF may have two entries, and no quantity two DOF (IC3). A DOF with no entry is an untied DOF: a named gap, or a refusal under IC2_POLICY <code>REJECT</code> (IC2).
<pre class="tfk-template">
"ENTRIES": [
{
"NAME": "E_t",
"DOF": "t",
"DOMAIN": "always",
"ENVIRONMENT_QUANTITY": "time",
"IDENTIFICATION": "t is the reading of a laboratory clock from an arbitrary origin",
"FALSIFIER": "a second clock whose readings differ from t by more than a constant offset beyond the stated uncertainty",
"FALSIFIER_CLASS": "F3",
"BEARS": [],
"DIMENSION": "T1"
},
</pre>

The other four entries: the same nine fields for <code>x</code>, <code>v</code>, <code>z</code> and <code>F</code>. The last line closes the Translation Manifold.
<pre class="tfk-template">
{
"NAME": "E_x",
"DOF": "x",
"DOMAIN": "|x| < x_max",
"ENVIRONMENT_QUANTITY": "position",
"IDENTIFICATION": "x is the displacement of the mass along the spring axis from the point where the spring exerts no force",
"FALSIFIER": "a measured spring force not proportional to x inside the domain",
"FALSIFIER_CLASS": "F3",
"BEARS": ["EOM_X", "KIN"],
"DIMENSION": "L1"
},
{
"NAME": "E_v",
"DOF": "v",
"DOMAIN": "|x| < x_max",
"ENVIRONMENT_QUANTITY": "velocity",
"IDENTIFICATION": "v is the rate of change of x with t",
"FALSIFIER": "a measured velocity that differs from the rate of change of the measured x beyond uncertainty",
"FALSIFIER_CLASS": "F2",
"BEARS": ["KIN"],
"DIMENSION": "L1 T-1"
},
{
"NAME": "E_z",
"DOF": "z",
"DOMAIN": "always",
"ENVIRONMENT_QUANTITY": "transverse_position",
"IDENTIFICATION": "z is the displacement of the mass perpendicular to the spring axis",
"FALSIFIER": "a measured z different from 0 beyond its uncertainty",
"FALSIFIER_CLASS": "F3",
"BEARS": ["EOM_Z", "C_NOZ"],
"DIMENSION": "L1"
},
{
"NAME": "E_F",
"DOF": "F",
"DOMAIN": "always",
"ENVIRONMENT_QUANTITY": "applied_force",
"IDENTIFICATION": "F is the force an external driver applies to the mass along the spring axis",
"FALSIFIER": "a force gauge in line with the driver reading a force different from F beyond its uncertainty",
"FALSIFIER_CLASS": "F3",
"BEARS": ["EOM_X"],
"DIMENSION": "M1 L1 T-2"
}
]
},
</pre>

== The Measure Set (TMS) ==
The third zone holds the numbers and conventions by which records in the UWC are compared and ordered. It holds no physics.

'''PARAMETERS''', REQUIRED:
* <code>STEP_CONVENTION</code>, REQUIRED, prose, not blank: what counts as one derivation step.
* <code>K</code>, REQUIRED, a positive decimal as a string: the multiplier in the test of whether two measured values contradict (SR3).
* <code>N_X</code>, REQUIRED, a whole number of at least 2, not in quotes: how many independent contradictions of a standing record open an audit on it (SR6).
* <code>S_MAX</code>, REQUIRED, a whole number of at least 1, not in quotes: the depth that bounds T3.
* <code>IC2_POLICY</code>, DEFAULT <code>"GAP"</code>: an untied DOF is a named gap; <code>"REJECT"</code> refuses it.
* <code>PROMOTION_FLOOR</code>, DEFAULT <code>"F2"</code>: the falsifier class a result must reach to be promoted; <code>"F1"</code>, <code>"F2"</code> or <code>"F3"</code>.
* <code>STRUCTURE_CHECK</code>, DEFAULT <code>"ON"</code>: whether the structure check of the equations of motion runs at the final pass. <code>"OFF"</code> gives the label ''Structure not Validated at Inception'', reason CHECK OFF.
<pre class="tfk-template">
"TMS": {
"PARAMETERS": {
"STEP_CONVENTION": "one application of an inference rule or algebraic identity is one step",
"K": "2",
"N_X": 2,
"S_MAX": 10,
"IC2_POLICY": "GAP",
"PROMOTION_FLOOR": "F2",
"STRUCTURE_CHECK": "ON"
},
</pre>

'''CONSTANTS''', REPEATS, OPTIONAL (left out means empty): the named weights a yardstick uses, each with NAME and VALUE (a decimal as a string), both REQUIRED. A yardstick contains no literal number, so every weight it uses is named here. They are not physics: a mass or a stiffness goes in the Prime Kernel.
<pre class="tfk-template">
"CONSTANTS": [
{"NAME": "w_a", "VALUE": "1"},
{"NAME": "w_s", "VALUE": "0.5"}
],
</pre>

'''YARDSTICKS''', REPEATS, OPTIONAL (left out means empty): the UWC's own rules for ordering records. NAME, KEY and LIMITING are all REQUIRED.
* '''KEY''', REPEATS, and here the order is the meaning: two records are compared term by term, first to last, and the first term that differs decides, the lower value closer. It begins with <code>SR1</code>, and <code>SR1</code> appears nowhere else. Terms: <code>A</code> (the number of assumptions), <code>S</code> (the number of steps), <code>NEG:</code>''term'', and <code>WSUM:</code>''weight''<code>*</code>''term''<code>;</code>... with each weight a name from CONSTANTS; no spaces inside a term. Adding an assumption must never bring a record closer (SR9 C2). The full list is on [[The Principia Machina/Inputs/Yardsticks|the yardsticks page]].
* '''LIMITING''', REPEATS, may be <code>[]</code> but not left out: limiting cases, each with DOMAIN (prose) and KEY. Inside that DOMAIN, and only there, its KEY replaces the main KEY.
The last lines close the Measure Set and the draft.
<pre class="tfk-template">
"YARDSTICKS": [
{
"NAME": "combined_distance",
"KEY": ["SR1", "WSUM:w_a*A;w_s*S", "S"],
"LIMITING": [
{"DOMAIN": "results that hold only at x = 0", "KEY": ["SR1", "S", "A"]}
]
}
]
}
}
</pre>

== What the gate prints for it ==
Run unchanged, the gate prints these lines first (a plain copy, not part of the draft). Then come the inspections the declaring authority still owes, the GATE line and the line naming TPX's version.
<pre>
TPK PASS
T2 PASS
T5 PASS
T4 PASS
T6 PASS
TrM PASS
IC1-IC4 PASS
TMS PASS
YARDSTICK combined_distance: C1 pass, C2 pass, C4 pass
FINAL T3 (constraints and laws) and IC2 PASS
STRUCTURE map (shown whatever STRUCTURE_CHECK says): analysis RUN; D variable t
F: INPUT
t: INDEPENDENT
v: DETERMINED (LAW EOM_X)
x: DETERMINED (LAW KIN)
z: FIXED
index 0, initial values 2 (the determined part; information)
closed: EOM_Z (ZERO)
STRUCTURE findings: none
STRUCTURE structurally regular

D(TPK) 44d25cd24f7cf812f79cfea910810b0de7e315d2866b872e33d67b9daff451aa
D(TrM) 8948b6e86fe5f2286053acb42b88d7db52bfb4bbb0f99cc2c68bf8d375aa4ee4
D(TMS) 3dce947d86f9826f98bb85e856cce2fcb8e347399b41806c7a597b1aa7681c50
D(TFK) d8b7fb01cff25e80820ceefbf9dd29ebe3676b45f110fb63ac5a5552edeb4a9c
</pre>
Change one character inside a block and the digests change; respell a decimal, a dimension, a unit or the spacing of a form, or reorder the items of a list other than a KEY, and they do not ([[The Principia Machina/TPS/2.5 Digests and the digest gate|TPS 2.5]]).

== Making it your own ==
# Write down your system's degrees of freedom, constants and laws before you touch the draft.
# Replace the template's entries kind by kind, keeping the shape: one object per item in each REPEATS list, commas between them, none after the last.
# Delete what you do not need: an OPTIONAL field; a kind of the Prime Kernel; the Measure Set's CONSTANTS and YARDSTICKS together; a header list, by writing <code>[]</code>.
# Run the gate after each change. When it refuses, the first problem it names is the one to fix; [[The Principia Machina/Inputs/Refusal messages|refusal messages]] explains each.
To start again from the template, open [[Special:TpmCheck]] afresh.

== Non-goals ==
The template shows a draft that is well formed and passes the gate. It does not show that the spring's physics is right for any real spring, and a draft that passes the gate is still a draft: nothing is stored and no UWC is created.

== For maintainers ==
[[Special:TpmCheck]] starts with the text of this page's blocks whose opening tag is exactly <code><nowiki><pre class="tfk-template"></nowiki></code> followed by a line break, joined in page order; TPX's setting <code>$wgTpxCheckTemplatePage</code> names this page. Other <code>pre</code> blocks are not read. After any edit, the joined blocks must still be one draft that passes the gate; run it there and update the digests above.

Governing sections: [[The Principia Machina/TPS/2.1 The Full Kernel and immutability|TPS 2.1]], [[The Principia Machina/TPS/2.2 The Prime Kernel|2.2]], [[The Principia Machina/TPS/2.3 The Translation Manifold|2.3]], [[The Principia Machina/TPS/2.4 The Measure Set|2.4]], [[The Principia Machina/TPS/2.5 Digests and the digest gate|2.5]] and [[The Principia Machina/TPS/5.5 The new-container flow|5.5]].

[[Category:The Principia Machina]]

The Principia Machina/TFK template - Revision history

BFP Rauch: 1 revision imported

DeltaS Zero: New page: a complete draft TFK that passes the gate, in pieces with a note on every field and the lists that repeat marked; Special:TpmCheck (TPX 0.2.0) starts with its blocks

← Older revision	Revision as of 05:21, 1 October 2026
(No difference)