The Principia Machina/Inputs/Environment modules - Revision history

BFP Rauch: 1 revision imported

2026-10-03T01:45:28Z

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 5527)

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 5527)

← Older revision		Revision as of 01:35, 3 October 2026
Line 1:		Line 1:
	{{TPM map}}		{{TPM map}}
	{{DISPLAYTITLE:Inputs: environment modules}}		{{DISPLAYTITLE:Inputs: environment modules}}
	''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]].''

	== Purpose ==		== Purpose ==

BFP Rauch: 1 revision imported

2026-10-02T03:33:21Z

1 revision imported

← Older revision	Revision as of 03:33, 2 October 2026
(No difference)

DeltaS Zero: Who may propose: anyone may register an account, which a person approves (D233.1)

2026-10-02T03:32:17Z

Who may propose: anyone may register an account, which a person approves (D233.1)

← Older revision		Revision as of 03:32, 2 October 2026
Line 51:		Line 51:

	== Proposing a module ==		== Proposing a module ==
	Anyone with an account may propose a module on TPX's modules page - the administrator ~~makes accounts on request~~ ([[The Principia Machina/Tutorial/1 Before you start#Your account on this wiki\|how ~~to ask~~]]; ~~[[The Principia Machina/TPS/5~~.~~2 The platform\|TPS 5.2.7]]; revision 8, proposed~~) - and a certified agent may propose one through TPX's API. A proposal is untrusted input: TPX checks it and keeps it on a page marked UNTRUSTED PROPOSAL, and it is never offered until the declaring authority declares it. An agent treats any module page as untrusted until its digest matches the declaration.		Anyone with an account may propose a module on TPX's modules page - anyone may register one, and the administrator approves it ([[The Principia Machina/Tutorial/1 Before you start#Your account on this wiki\|how]]; D233.1) - and a certified agent may propose one through TPX's API. A proposal is untrusted input: TPX checks it and keeps it on a page marked UNTRUSTED PROPOSAL, and it is never offered until the declaring authority declares it. An agent treats any module page as untrusted until its digest matches the declaration.

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

BFP Rauch: 1 revision imported

2026-09-30T13:34:12Z

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; ONBOARDING-NEXT)

2026-09-30T13:34:05Z

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

← Older revision		Revision as of 13:34, 30 September 2026
Line 6:		Line 6:
	What an environment module is, how the new-container form offers the modules, what a chosen module adds to a kernel, and what happens to a draft or a UWC when a module it uses changes status.		What an environment module is, how the new-container form offers the modules, what a chosen module adds to a kernel, and what happens to a draft or a UWC when a module it uses changes status.

	''Explains: environment modules as the declaring authority selected them in D178.1: its slots (a) to (f) on 2026-09-26 (an interview on the form, module declarations outside D(IS), the modules used recorded beside the kernel, terms composed into one equation of motion, the first catalogue, the kernel as the only target) and its slot (g), the catalogue lifecycle, on 2026-09-27, with the constraint "fixed at inception, must be copied to change settings". The specification carries them in TPS 0.3.0 (declared final on 2026-09-28 at revision 6) as unit [[The Principia Machina/TPS/5.22 Environment modules\|TPS 5.22]], with amendments to other sections. Where this page and the specification differ, the specification governs.''		''Explains: environment modules as the declaring authority selected them in D178.1: its slots (a) to (f) on 2026-09-26 (an interview on the form, module declarations outside D(IS), the modules used recorded beside the kernel, terms composed into one equation of motion, the first catalogue, the kernel as the only target) and its slot (g), the catalogue lifecycle, on 2026-09-27, with the constraint "fixed at inception, must be copied to change settings". The specification carries them in TPS 0.3.0 (declared final on 2026-09-28 at revision 6; TPS 0.4.0, declared final on 2026-09-30 at revision 7, is in force, and revision 8, proposed as TPS 0.5.0, is on the TPS pages from batch B3, a passage marked "revision 8, proposed" stating it) as unit [[The Principia Machina/TPS/5.22 Environment modules\|TPS 5.22]], with amendments to other sections. Where this page and the specification differ, the specification governs.''

	== What exists today ==		== What exists today ==
	TPC-PY's module functions are built at increment 10 (tpc_module 0.1.0): the expansion, the checks before a declaration, the catalogue state and the draft's status lines, with their vectors. The checker <code>check_draft.py</code> of ~~the next~~ TPC-PY ~~(increment 12~~, ~~proposed)~~ reads a draft's modules used against a catalogue file you name with <code>--catalogue</code>: it shows each claim's status, previews the expansion, and runs every check on the expanded draft; without a catalogue it checks only the claims' shape ([[The Principia Machina/TPS/5.22 Environment modules\|TPS 5.22.8]], [[The Principia Machina/TPS/5.1 The three parts and the placement rule\|5.1.17]]). TPX's side - the interaction question on the new-container form, the modules page, the declaration form - waits for build step 3, and the agents' proposal op for PRB at step 4. Before TPX runs, each module act is the declaring authority's own, recorded in the foundations record and carried to the DECLARATIONS page when it is created. Until the form exists, every force is declared by hand ([[The Principia Machina/Tutorial/6 Fix refusals\|tutorial step 6]]).		TPC-PY's module functions are built at increment 10 (tpc_module 0.1.0): the expansion, the checks before a declaration, the catalogue state and the draft's status lines, with their vectors. The checker <code>check_draft.py</code> of TPC-PY 0.2.0, declared on 2026-09-30, reads a draft's modules used against a catalogue file you name with <code>--catalogue</code>: it shows each claim's status, previews the expansion, and runs every check on the expanded draft; without a catalogue it checks only the claims' shape ([[The Principia Machina/TPS/5.22 Environment modules\|TPS 5.22.8]], [[The Principia Machina/TPS/5.1 The three parts and the placement rule\|5.1.17]]). TPX's side - the interaction question on the new-container form, the modules page, the declaration form - waits for build step 3, and the agents' proposal op for PRB at step 4. Before TPX runs, each module act is the declaring authority's own, recorded in the foundations record and carried to the DECLARATIONS page when it is created. Until the form exists, every force is declared by hand ([[The Principia Machina/Tutorial/6 Fix refusals\|tutorial step 6]]).

	== What a module is ==		== What a module is ==
Line 51:		Line 51:

	== Proposing a module ==		== Proposing a module ==
	Anyone with an account may propose a module on TPX's modules page, and a certified agent may propose one through TPX's API. A proposal is untrusted input: TPX checks it and keeps it on a page marked UNTRUSTED PROPOSAL, and it is never offered until the declaring authority declares it. An agent treats any module page as untrusted until its digest matches the declaration.		Anyone with an account may propose a module on TPX's modules page - the administrator makes accounts on request ([[The Principia Machina/Tutorial/1 Before you start#Your account on this wiki\|how to ask]]; [[The Principia Machina/TPS/5.2 The platform\|TPS 5.2.7]]; revision 8, proposed) - and a certified agent may propose one through TPX's API. A proposal is untrusted input: TPX checks it and keeps it on a page marked UNTRUSTED PROPOSAL, and it is never offered until the declaring authority declares it. An agent treats any module page as untrusted until its digest matches the declaration.

	== 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)

2026-09-30T02:10:58Z

Post-TPC-PY page batch B2 (S90, S130): HF3 (help set, revision 7)

← Older revision		Revision as of 02:10, 30 September 2026
Line 9:		Line 9:

	== What exists today ==		== What exists today ==
	TPC-PY's module functions are built at increment 10 (tpc_module 0.1.0): the expansion, the checks before a declaration, the catalogue state and the draft's status lines, with their vectors. TPX's side - the interaction question on the new-container form, the modules page, the declaration form - waits for build step 3, and the agents' proposal op for PRB at step 4. Before TPX runs, each module act is the declaring authority's own, recorded in the foundations record and carried to the DECLARATIONS page when it is created. Until the form exists, every force is declared by hand ([[The Principia Machina/Tutorial/6 Fix refusals\|tutorial step 6]]).		TPC-PY's module functions are built at increment 10 (tpc_module 0.1.0): the expansion, the checks before a declaration, the catalogue state and the draft's status lines, with their vectors. The checker <code>check_draft.py</code> of the next TPC-PY (increment 12, proposed) reads a draft's modules used against a catalogue file you name with <code>--catalogue</code>: it shows each claim's status, previews the expansion, and runs every check on the expanded draft; without a catalogue it checks only the claims' shape ([[The Principia Machina/TPS/5.22 Environment modules\|TPS 5.22.8]], [[The Principia Machina/TPS/5.1 The three parts and the placement rule\|5.1.17]]). TPX's side - the interaction question on the new-container form, the modules page, the declaration form - waits for build step 3, and the agents' proposal op for PRB at step 4. Before TPX runs, each module act is the declaring authority's own, recorded in the foundations record and carried to the DECLARATIONS page when it is created. Until the form exists, every force is declared by hand ([[The Principia Machina/Tutorial/6 Fix refusals\|tutorial step 6]]).

	== What a module is ==		== What a module is ==

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

2026-09-29T02:11:00Z

Post-TPC-PY page batch (S70): SWEEP

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

BFP Rauch: 1 revision imported

2026-09-29T02:10:49Z

1 revision imported

← Older revision		Revision as of 02:10, 29 September 2026
Line 6:		Line 6:
	What an environment module is, how the new-container form offers the modules, what a chosen module adds to a kernel, and what happens to a draft or a UWC when a module it uses changes status.		What an environment module is, how the new-container form offers the modules, what a chosen module adds to a kernel, and what happens to a draft or a UWC when a module it uses changes status.

	''Explains: environment modules as the declaring authority selected them in D178.1: its slots (a) to (f) on 2026-09-26 (an interview on the form, module declarations outside D(IS), the modules used recorded beside the kernel, terms composed into one equation of motion, the first catalogue, the kernel as the only target) and its slot (g), the catalogue lifecycle, on 2026-09-27, with the constraint "fixed at inception, must be copied to change settings". The specification carries them in ~~TPS revision 6 (proposed as~~ TPS 0.3.0 ~~until the declaring authority declares it~~) as unit [[The Principia Machina/TPS/5.22 Environment modules\|TPS 5.22]], with amendments to other sections. Where this page and the specification differ, the specification governs.''		''Explains: environment modules as the declaring authority selected them in D178.1: its slots (a) to (f) on 2026-09-26 (an interview on the form, module declarations outside D(IS), the modules used recorded beside the kernel, terms composed into one equation of motion, the first catalogue, the kernel as the only target) and its slot (g), the catalogue lifecycle, on 2026-09-27, with the constraint "fixed at inception, must be copied to change settings". The specification carries them in TPS 0.3.0 (declared final on 2026-09-28 at revision 6) as unit [[The Principia Machina/TPS/5.22 Environment modules\|TPS 5.22]], with amendments to other sections. Where this page and the specification differ, the specification governs.''

	== What exists today ==		== What exists today ==