The Principia Machina/Inputs/Yardsticks - Revision history

BFP Rauch: 1 revision imported

2026-10-03T01:45:31Z

1 revision imported

← Older revision	Revision as of 01:45, 3 October 2026
(No difference)

DeltaS Zero: G-1 (outside AI session 2): the lead's last sentence now says where the agent-facing page is and addresses no one (base revision 5455)

2026-10-03T01:35:13Z

G-1 (outside AI session 2): the lead's last sentence now says where the agent-facing page is and addresses no one (base revision 5455)

← Older revision		Revision as of 01:35, 3 October 2026
Line 1:		Line 1:
	{{TPM map}}		{{TPM map}}
	{{DISPLAYTITLE:Inputs: yardsticks}}		{{DISPLAYTITLE:Inputs: yardsticks}}
	''Public Recorder inputs: a help set for the people who put things into The Principia Machina - authors of a new UWC, operators, and the declaring authority. It explains; the specification governs. Start at [[The Principia Machina/Inputs\|the index]]; for a guided walk from a blank file to a declared UWC, follow [[The Principia Machina/Tutorial\|the tutorial]]. ~~Agents read~~ [[The Principia Machina/Agent/Inputs\|the agent-facing page]] ~~instead~~.''		''Public Recorder inputs: a help set for the people who put things into The Principia Machina - authors of a new UWC, operators, and the declaring authority. It explains; the specification governs. Start at [[The Principia Machina/Inputs\|the index]]; for a guided walk from a blank file to a declared UWC, follow [[The Principia Machina/Tutorial\|the tutorial]]. Its counterpart for agents is [[The Principia Machina/Agent/Inputs\|the agent-facing page]].''

	{{:The Principia Machina/Diagrams/07 Strike-rule flow}}		{{:The Principia Machina/Diagrams/07 Strike-rule flow}}

BFP Rauch: 1 revision imported

2026-09-30T13:34:16Z

1 revision imported

← Older revision		Revision as of 13:34, 30 September 2026
(No difference)

DeltaS Zero: Post-TPC-PY page batch B3 (S154, S159): HF4 (help set; S171-LITERALS)

2026-09-30T13:34:05Z

Post-TPC-PY page batch B3 (S154, S159): HF4 (help set; S171-LITERALS)

← Older revision		Revision as of 13:34, 30 September 2026
Line 9:		Line 9:
	How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.		How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.

	''Explains: TPS 0.3.0 (declared final on 2026-09-28 at revision 6; it follows TPS 0.1.1, declared final on 2026-09-~~26;~~ revision ~~7, proposed as TPS 0.4.0, is on the TPS pages from batch B2, and a passage marked "revision 7, proposed" states it~~), 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); [[The Principia Machina/TPC-PY\|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, and [[The Principia Machina/TPC-PY\|TPC-PY 0.2.0]] (~~proposed, not~~ declared~~; its pages~~ on ~~this wiki since batch B2~~; tree digest 2998ac4c24dff83bd047a691081b7d27bb25c9d26512bffe519f5c2b6ba127e2, conformed TPS 0.4.0; tpc_zone 0.5.1, tpc_units 0.1.2, tpc_tests 0.2.1, tpc_form 0.2.1, tpc_eom 0.2.0; schema 0.5.0) with check_draft 0.6.0; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''		''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); [[The Principia Machina/TPC-PY\|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, and [[The Principia Machina/TPC-PY\|TPC-PY 0.2.0]] (declared on 2026-09-30; tree digest 2998ac4c24dff83bd047a691081b7d27bb25c9d26512bffe519f5c2b6ba127e2, conformed TPS 0.4.0; tpc_zone 0.5.1, tpc_units 0.1.2, tpc_tests 0.2.1, tpc_form 0.2.1, tpc_eom 0.2.0; schema 0.5.0) with check_draft 0.6.0; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''

	== What a yardstick is ==		== What a yardstick is ==
Line 56:		Line 56:

	== FIELD terms ==		== FIELD terms ==
	A FIELD term names a numeric field of a register record, read from a closed field table. The table holds one field, U_C: <code>FIELD:U_C</code> is a record's combined standard uncertainty, an L record's read as 0; any other FIELD name is refused ([[The Principia Machina/TPS/2.4 The Measure Set\|TPS 2.4.8]]~~; revision 7, proposed~~). The checker of ~~the declared~~ TPC-PY still reports <code>REFUSED, FIELD terms await the record field schema (C-16)</code> for every FIELD term, and the draft does not pass. The checker of ~~the next~~ TPC-PY ~~(increment 12~~, ~~proposed)~~ retires that message. It builds the field table over its synthetic record suite, an L record reading 0, and runs a yardstick with <code>FIELD:U_C</code> through the SR9 checks like any other; a FIELD other than U_C it reports <code>REFUSED, FIELD ''name'' is not in the field table</code>. ~~Until that~~ TPC-PY ~~is declared~~, leave FIELD terms out of a draft you want ~~the declared checker~~ to pass.		A FIELD term names a numeric field of a register record, read from a closed field table. The table holds one field, U_C: <code>FIELD:U_C</code> is a record's combined standard uncertainty, an L record's read as 0; any other FIELD name is refused ([[The Principia Machina/TPS/2.4 The Measure Set\|TPS 2.4.8]]). The checker of TPC-PY 0.1.0 still reports <code>REFUSED, FIELD terms await the record field schema (C-16)</code> for every FIELD term, and the draft does not pass. The checker of TPC-PY 0.2.0, declared on 2026-09-30, retires that message. It builds the field table over its synthetic record suite, an L record reading 0, and runs a yardstick with <code>FIELD:U_C</code> through the SR9 checks like any other; a FIELD other than U_C it reports <code>REFUSED, FIELD ''name'' is not in the field table</code>. With TPC-PY 0.1.0's checker, leave FIELD terms out of a draft you want it to pass.

	== Non-goals ==		== Non-goals ==

BFP Rauch: 1 revision imported

2026-09-30T02:11:12Z

1 revision imported

← Older revision		Revision as of 02:11, 30 September 2026
(No difference)

DeltaS Zero: Post-TPC-PY page batch B2 (S90, S130): HF3 (help set, revision 7); SWEEP (SW-2, SW-3)

2026-09-30T02:10:58Z

Post-TPC-PY page batch B2 (S90, S130): HF3 (help set, revision 7); SWEEP (SW-2, SW-3)

← Older revision		Revision as of 02:10, 30 September 2026
Line 9:		Line 9:
	How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.		How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.

	''Explains: TPS 0.3.0 (declared final on 2026-09-28 at revision 6; it follows TPS 0.1.1, declared final on 2026-09-26), 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); [[The Principia Machina/TPC-PY\|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; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''		''Explains: TPS 0.3.0 (declared final on 2026-09-28 at revision 6; it follows TPS 0.1.1, declared final on 2026-09-26; revision 7, proposed as TPS 0.4.0, is on the TPS pages from batch B2, and a passage marked "revision 7, proposed" states it), 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); [[The Principia Machina/TPC-PY\|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, and [[The Principia Machina/TPC-PY\|TPC-PY 0.2.0]] (proposed, not declared; its pages on this wiki since batch B2; tree digest 2998ac4c24dff83bd047a691081b7d27bb25c9d26512bffe519f5c2b6ba127e2, conformed TPS 0.4.0; tpc_zone 0.5.1, tpc_units 0.1.2, tpc_tests 0.2.1, tpc_form 0.2.1, tpc_eom 0.2.0; schema 0.5.0) with check_draft 0.6.0; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''

	== What a yardstick is ==		== What a yardstick is ==
Line 56:		Line 56:

	== FIELD terms ==		== FIELD terms ==
	A FIELD term names a numeric field of a register record. The ~~list of~~ record ~~fields~~ is ~~owed~~ (~~C-16~~)~~, so a FIELD term passes~~ the ~~key rules but cannot be run: the checker~~ reports <code>REFUSED, FIELD terms await the record field schema (C-16)</code> and the draft does not pass. Do not ~~use~~ FIELD terms ~~until C-16 lands~~.		A FIELD term names a numeric field of a register record, read from a closed field table. The table holds one field, U_C: <code>FIELD:U_C</code> is a record's combined standard uncertainty, an L record's read as 0; any other FIELD name is refused ([[The Principia Machina/TPS/2.4 The Measure Set\|TPS 2.4.8]]; revision 7, proposed). The checker of the declared TPC-PY still reports <code>REFUSED, FIELD terms await the record field schema (C-16)</code> for every FIELD term, and the draft does not pass. The checker of the next TPC-PY (increment 12, proposed) retires that message. It builds the field table over its synthetic record suite, an L record reading 0, and runs a yardstick with <code>FIELD:U_C</code> through the SR9 checks like any other; a FIELD other than U_C it reports <code>REFUSED, FIELD ''name'' is not in the field table</code>. Until that TPC-PY is declared, leave FIELD terms out of a draft you want the declared checker to pass.

	== Non-goals ==		== Non-goals ==

DeltaS Zero: Post-TPC-PY page batch (S70): S61 FIXUP

2026-09-29T02:11:00Z

Post-TPC-PY page batch (S70): S61 FIXUP

← Older revision	Revision as of 02:11, 29 September 2026
(No difference)

BFP Rauch: 1 revision imported

2026-09-29T02:10:50Z

1 revision imported

← Older revision		Revision as of 02:10, 29 September 2026
Line 9:		Line 9:
	How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.		How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.

	''Explains: ~~TPS revision 6 (proposed as~~ TPS 0.3.0 ~~until the declaring authority declares it~~; it follows TPS 0.1.1, declared final on 2026-09-26), 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 ~~as built at increment 10~~ (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~~; no TPC-PY version is declared yet~~) with check_draft 0.5.0; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''		''Explains: TPS 0.3.0 (declared final on 2026-09-28 at revision 6; it follows TPS 0.1.1, declared final on 2026-09-26), 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); [[The Principia Machina/TPC-PY\|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; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''

	== What a yardstick is ==		== What a yardstick is ==

BFP Rauch: 1 revision imported

2026-09-28T03:56:36Z

1 revision imported

← Older revision	Revision as of 03:56, 28 September 2026
(No difference)

DeltaS Zero: Second help pass (HELP-PASS-2): agent D's draft: its PENDING lines closed and D176.1-D190.1 applied; every quoted output re-printed from the increment-10 tree (S10)

2026-09-28T03:55:00Z

Second help pass (HELP-PASS-2): agent D's draft: its PENDING lines closed and D176.1-D190.1 applied; every quoted output re-printed from the increment-10 tree (S10)

← Older revision		Revision as of 03:55, 28 September 2026
Line 9:		Line 9:
	How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.		How to write a yardstick: a UWC's own rule for ordering records, and the rules that keep it from bending the strike skeleton.

	''Explains: TPS 0.2.0 ~~(proposed; revision 5 of~~ the ~~tree, imported 2026-09-26, not yet declared~~; TPS 0.1.~~0 was~~ declared final on 2026-09-22), whose sections 2.2 to 2.5 ~~now~~ carry the zone schemas ~~at schema 0.4.0~~ with the optional declared form (records D92.1, D98.1, D99.1, D100.1, D103.1-D105.1, D106.1-D108.1 and ~~D132~~.1); TPC-PY as built at increment 9 (tpc_zone 0.4.0, tpc_units 0.1.0, tpc_tests 0.2.0, tpc_form 0.1.0; no TPC-PY version is declared yet) with check_draft 0.4.0; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''		''Explains: TPS revision 6 (proposed as TPS 0.3.0 until the declaring authority declares it; it follows TPS 0.1.1, declared final on 2026-09-26), 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 as built at increment 10 (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; no TPC-PY version is declared yet) with check_draft 0.5.0; the yardstick evaluator, TPC-PY tpc_yardstick 0.1.0. Where this page and the specification differ, the specification governs.''

	== What a yardstick is ==		== What a yardstick is ==