<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://invarians.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Alt+BFP</id>
	<title>The Invariance Itself - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://invarians.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Alt+BFP"/>
	<link rel="alternate" type="text/html" href="https://invarians.org/wiki/Special:Contributions/Alt_BFP"/>
	<updated>2026-10-21T08:13:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>https://invarians.org/index.php?title=Main_Page&amp;diff=6615</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=Main_Page&amp;diff=6615"/>
		<updated>2026-10-14T22:41:15Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;&amp;lt;!-- IPSUM INVARIANS - Main Page. Box structure per supplied template; styles inline so the page renders with no extensions installed. mp-* ids retained so a later stylesheet can override without editing wikitext. --&amp;gt;&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&amp;lt;!-- Top banner --&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-topbanner&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #f8f9fa; padding: 10px; text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-welcome&amp;quot;&amp;gt;&amp;lt;h1 style=&amp;quot;margin: 0; border: none; padding: 0.1em; font-size: 1.8em; font-weight: normal;&amp;quot;&amp;gt;IPSUM INVARIANS: The Invariance Itself&lt;br /&gt;
&amp;lt;/h1&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-free&amp;quot; style=&amp;quot;font-size: 0.95em;&amp;quot;&amp;gt;The public record of the invariance program. est. 1 September 2026&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;articlecount&amp;quot; style=&amp;quot;font-size: 0.85em; margin-top: 0.3em;&amp;quot;&amp;gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles &amp;amp;middot; [[Special:Statistics|{{NUMBEROFACTIVEUSERS}}]] active editors &amp;amp;middot; [[Special:RecentChanges|{{NUMBEROFEDITS}} edits]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Main Container using Flexbox for responsiveness --&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;display: flex; flex-wrap: wrap; gap: 15px; justify-content: space-between;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;!-- Left Column --&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-left&amp;quot; style=&amp;quot;flex: 1 1 48%; min-width: 300px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Green Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-intro-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-intro-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cef2e0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Introduction&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-intro&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;Please be patient as we pull this site together.  Check back often for the latest developments.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Welcome to Ipsum Invarians, a platform built in four sections:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Arena&#039;&#039;&#039; (Principia Machina): Essentially, this venue functions as an evaluation framework for testing physical hypotheses using artificial intelligence. It provides an AI protocol and a public research registry. We call this framework &#039;&#039;[[the Principia Machina]].&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Weapon&#039;&#039;&#039; (Hamilton&#039;s Principle): Our namesake reflects what is arguably the single most important formulation in physics: the Action Principle or even Hamilton&#039;s principle. In our gladiatorial arena, [[Hamilton&#039;s principle]] is the sharpest, most lethal weapon available. To give this underappreciated concept its due, Ipsum Invarians carries a dedicated field manual for Hamilton’s Principle and its attendant [[Noether&#039;s theorems|Noether&#039;s theorem]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Gladiator&#039;&#039;&#039; (SVD): Continuing the metaphor, our local gladiator is Structured Vacuum Dynamics (SVD). SVD enters the arena with a specific postulate: that a single permutation of Maxwell’s 1861 paper, Hamilton’s Principle, and Noether&#039;s First Theorem is sufficient to populate all of physics.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Blueprint&#039;&#039;&#039; (Specifications): [[The_Principia_Machina/Hub/General_reader|Complete specifications]] for the Principia Machina and its standard prompt setup are openly published to ensure transparency and replication.  However, for security and reliability reasons, some internal testing functionality are only offered as pseudo code rather than providing the full testing paradigm.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Introduction|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- pma:begin lean --&amp;gt;&lt;br /&gt;
    &amp;lt;!-- Green Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-lean-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff; color: #202122;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-lean-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cef2e0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Current Program (Round 3): the move to Lean&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-lean&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;templatestyles src=&amp;quot;Principia Machina/styles.css&amp;quot; /&amp;gt;&lt;br /&gt;
[[The Principia Machina]] is being rewritten in &#039;&#039;&#039;Lean 4&#039;&#039;&#039;, a language in which proofs are checked by machine: one source for the specification and its Calculator, theorems where version 1 had only tests, and a proof checker as the gate every change must pass. The move also inspired a restructuring of the development workflow.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where it stands&#039;&#039;&#039; (14 October 2026): Phase 0 of seven, the development setup, is under way. Phase 0 ports nothing from version 1 beyond one small module used as its test subject; the port itself is the work of Phase 2, the Calculator.&lt;br /&gt;
&amp;lt;div style=&amp;quot;display: flex; flex-wrap: wrap; gap: 0 1em; align-items: flex-start;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;flex: 1 1 220px; min-width: 0;&amp;quot;&amp;gt;&lt;br /&gt;
* &#039;&#039;&#039;Done:&#039;&#039;&#039; Lean 4.34.1 pinned on every machine; a first library with three proved theorems, the Calculator and its tests; the proof and names gates; one task carried from one machine to another; publishing to this wiki under the Declarer&#039;s one-time code.&lt;br /&gt;
* &#039;&#039;&#039;Open:&#039;&#039;&#039; the second development machine; steering a session from a phone or tablet.&lt;br /&gt;
* &#039;&#039;&#039;Next:&#039;&#039;&#039; Test T1 has run: a Lean program runs on the wiki&#039;s own server outside a web request, so one Calculator still serves both sides. Tests T2 and T3 follow on the same server: the time one call takes, and what a hundred calls in one scheduled run cost.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;pma-fig&amp;quot; style=&amp;quot;flex: 0 1 356px; min-width: 0; margin: 0 auto; text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;graphviz&amp;gt;&lt;br /&gt;
digraph phases {&lt;br /&gt;
  rankdir=TB; bgcolor=&amp;quot;transparent&amp;quot;; nodesep=0.2; ranksep=0.18; size=&amp;quot;5.6,9&amp;quot;;&lt;br /&gt;
  node [shape=box, style=&amp;quot;rounded,filled&amp;quot;, fontname=&amp;quot;Helvetica&amp;quot;, fontsize=10, color=&amp;quot;#a2a9b1&amp;quot;, fillcolor=&amp;quot;#eaecf0&amp;quot;, fontcolor=&amp;quot;#202122&amp;quot;, margin=&amp;quot;0.12,0.06&amp;quot;];&lt;br /&gt;
  edge [color=&amp;quot;#54595d&amp;quot;, fontname=&amp;quot;Helvetica&amp;quot;, fontsize=9, fontcolor=&amp;quot;#202122&amp;quot;, arrowsize=0.7];&lt;br /&gt;
  node [width=3.6];&lt;br /&gt;
  P0 [label=&amp;quot;Phase 0  The development setup\nunder way: the current focus&amp;quot;, fillcolor=&amp;quot;#cedff2&amp;quot;, color=&amp;quot;#6a8fbf&amp;quot;, penwidth=2.4];&lt;br /&gt;
  P1 [label=&amp;quot;Phase 1  Foundations\nunder way&amp;quot;, fillcolor=&amp;quot;#cedff2&amp;quot;, color=&amp;quot;#6a8fbf&amp;quot;];&lt;br /&gt;
  P2 [label=&amp;quot;Phase 2  The Calculator\nnot started&amp;quot;];&lt;br /&gt;
  P3 [label=&amp;quot;Phase 3  Custos\nnot started&amp;quot;];&lt;br /&gt;
  P4 [label=&amp;quot;Phase 4  The Research Client\nnot started&amp;quot;];&lt;br /&gt;
  P5 [label=&amp;quot;Phase 5  Other model families\nnot started&amp;quot;];&lt;br /&gt;
  P6 [label=&amp;quot;Phase 6  Lifecycle and cutover\nnot started&amp;quot;];&lt;br /&gt;
  R  [label=&amp;quot;First release declared&amp;quot;, shape=doubleoctagon, style=filled, fillcolor=&amp;quot;#ffedad&amp;quot;, color=&amp;quot;#ac6600&amp;quot;, width=2.2];&lt;br /&gt;
  P0 -&amp;gt; P1 -&amp;gt; P2 -&amp;gt; P3 -&amp;gt; P4 -&amp;gt; P5 -&amp;gt; P6 -&amp;gt; R;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/graphviz&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;font-size: 0.88em; color: #54595d;&amp;quot;&amp;gt;The seven phases, in order.&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;([[Principia Machina/Lean transition|Full article...]])&#039;&#039;&#039; &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; &#039;&#039;&#039;[[Principia Machina/Progress/Status|Status]]&#039;&#039;&#039; &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; [[Principia Machina/Lean transition#lt-plate-box|The two-doors riddle, in Lean]] &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; Version 1: [[Round 3|program of record]], [[The Principia Machina/Testing|testing]]&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;!-- pma:end lean --&amp;gt;&lt;br /&gt;
    &amp;lt;!-- Grey Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-history-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-history-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Program History&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-history&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
We started with a simple permutation of Maxwell&#039;s 1861 framework that yielded a promising interpretation of General Relativity. We applied a second permutation; analyzed it with tabletop testing and back-of-the-envelope calculations, and found we could derive both the eigenstates of hydrogen and chromodynamics. These two disparate domains (GR &amp;amp; QM) long advertised as incompatible, seem to be perfectly harmonious derivations from Maxwell&#039;s 1861 work. The result suggests a viable postulate: if we constrain ourselves with Hamilton’s Principle and Noether’s First Theorem,  can we build all of physics from a single assumption? From two assumptions?&lt;br /&gt;
&lt;br /&gt;
[[File:Modified vorticie.jpg|thumb|center|upright=1.5|A simple permutation of Maxwell&#039;s 1861 framework.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The idea is daunting, but maybe AI can help.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 1&#039;&#039;&#039; &amp;amp;ndash; Technical paper: Structured Vacuum Dynamics &lt;br /&gt;
&lt;br /&gt;
This was more of a proof of concept: would AI confirm the math or maybe find new paradigms to fit the otherwise disparate math together?  We started with a simple technical paper around the postulate and a strict set of AI controls and restrictions.  We designed a rigerous prompt that pitted the AI Agent against itself, doing more work to double and triple check its results than the original work to get the results, but this effort quickly overwhelmed the local AI context.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 2&#039;&#039;&#039; &amp;amp;ndash; The Research Register (RR-n)&lt;br /&gt;
&lt;br /&gt;
The Lesson from round 1 - physics is a much bigger domain than a single paper.  We did start to understand the context limits of the most reasonably available AI offerings and the constraints it left us with.  We broke the design into two parts: a back-end research register and a front-end that could generate papers from the research register.  Soon we ran into problems mapping the axioms to the environment.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 3 opening&#039;&#039;&#039; &amp;amp;ndash; The Principia Machina (TPM)&lt;br /&gt;
&lt;br /&gt;
The Lesson from round 2 - Local AI context was never going to be enough for any serious work.  We realized we could kill three birds with one stone if we moved the research context to a Wiki:&lt;br /&gt;
#The context would be effectively unlimited&lt;br /&gt;
#A public, formalized, framework would foster independent verification&lt;br /&gt;
#it would give a great public record to invite collaboration and outside ideas&lt;br /&gt;
&lt;br /&gt;
Thus &#039;&#039;&#039;[[the Principia Machina]]:&#039;&#039;&#039; an AI Harness inspired physics solver/research platform and test bed implemented in MediaWiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Program history|Full record...]])&#039;&#039;&#039; &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; [[Program history/Archive|Archive]]&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Grey Box ?--&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-round-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-round-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Principia Machina Specification (TPS) &amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-round&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina Specification&#039;&#039;&#039; (TPS) is the complete, published&lt;br /&gt;
description of The Principia Machina (TPM), a set of rules for doing research&lt;br /&gt;
with AI assistants so that the result can be checked afterwards by anyone.&lt;br /&gt;
TPS is written for two readers at once: a person who wants to understand how&lt;br /&gt;
the framework works, and an AI agent of any make that wants to work under it.&lt;br /&gt;
It is one of five parts, and it is the part that binds the other four.&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;The foundations record.&#039;&#039;&#039; A dated account of every design decision, the options rejected, and the reasons. It is the source TPS was written from. It describes; it never instructs.&lt;br /&gt;
# &#039;&#039;&#039;The specification.&#039;&#039;&#039; This document. It defines the five layers of the framework, the sealed container a piece of research lives in, the wiki machinery that records the work, and the Agent Contract: the rules any AI agent follows to work a container. It is versioned, and its fingerprint is the first line of the wiki&#039;s chain of declarations.&lt;br /&gt;
# &#039;&#039;&#039;The implementations.&#039;&#039;&#039; What runs the rules. On the server, TPX, a MediaWiki extension that performs every check a machine can perform. Beside the agent, PRB, the client an agent uses to hold its working copy and land results. And each agent&#039;s own instruction set, implementing the Agent Contract. The project&#039;s own instruction set is written for Claude and is one implementation among any number.&lt;br /&gt;
# &#039;&#039;&#039;The wiki.&#039;&#039;&#039; Where all of the above is published and read, and the system of record for everything TPM does.&lt;br /&gt;
# &#039;&#039;&#039;The containers.&#039;&#039;&#039; The research itself: a sealed set of laws and assumptions, and the register of findings built on it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;!-- Right Column --&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-right&amp;quot; style=&amp;quot;flex: 1 1 48%; min-width: 300px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-hamilton-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-hamilton-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Hamilton&#039;s Principle&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-hamilton&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
Newton&#039;s laws, Maxwell&#039;s equations, general relativity and the Standard Model are each formulated as an action via Hamilton&#039;s Principle.  Across all these domains, dynamical equations emerge as derived outcomes rather than fundamental starting axioms. Conservation of energy, momentum and charge are not separate laws at all — [[Hamilton&#039;s principle/Mathematics/Noether&#039;s first theorem|Noether proved]] they follow from the action&#039;s symmetries. New models are now built by writing the action constrained by symmetry and letting the dynamics follow.  This is how electromagnetism and gravity were derived and how the nuclear forces were found. Alone among classical concepts, &#039;&#039;&#039;Hamilton&#039;s Principle&#039;&#039;&#039; transitions smoothly into quantum mechanics, where the action represents a phase carried across distinct trajectories and the classical path marks where destructive interference is minimized.  The action is the deepest thing physics knows.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:OPL-HP-F-01.png|thumb|center|upright=1.5|A true path and several comparison paths between fixed endpoints.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Hamilton&#039;s principle/Mathematics/The Jacobi condition and conjugate points|Stationary is not least]] — the long way round a great circle obeys the same rule at every point, and is plainly not the shortest. [[:File:OPL-HP-F-05.png|See the diagram]].&lt;br /&gt;
* [[Hamilton&#039;s principle/Applications/The Feynman path integral|Why the rule holds at all]] — nature selects nothing. It sums over everything, and what looks like a choice is the residue left by interference.&lt;br /&gt;
* [[Hamilton&#039;s principle/Explainers/Comparing paths|Start without the mathematics]] — every page carrying equations has a plain-language counterpart, linked from it and linking back.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Hamilton&#039;s principle|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-noether-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-noether-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Noether&#039;s theorems&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-noether&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:NT-F-07.png|thumb|center|400px|alt=Continuous symmetries on the left, the quantities they conserve on the right, with the map between them|The symmetry-to-conservation map]]&lt;br /&gt;
&lt;br /&gt;
Klein read the paper to the Göttingen Scientific Society on 26 July 1918. Its&lt;br /&gt;
last section answers a claim of Hilbert&#039;s: that energy conservation in general&lt;br /&gt;
relativity fails to take the form it takes everywhere else in physics.&lt;br /&gt;
&#039;&#039;&#039;There are two theorems in the paper, and they are not versions of one another.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The initial theorem relates global, finite-parameter symmetries directly to corresponding physical conservation laws governing actual dynamics. The second takes a symmetry that is allowed to differ from place to place and returns identities between the&lt;br /&gt;
field equations — identities that hold whether or not those equations are&lt;br /&gt;
satisfied. The second theorem is why a gauge theory has fewer independent field&lt;br /&gt;
equations than it has fields, and why gravity has no local energy.&lt;br /&gt;
&lt;br /&gt;
A 90-page reading edition: both theorems proved in full and kept apart, the&lt;br /&gt;
mathematics they need, the physics they explain, and a plain-language&lt;br /&gt;
counterpart for every page that carries equations.&lt;br /&gt;
&lt;br /&gt;
* [[Noether&#039;s theorems/History/Gottingen and the energy problem|Göttingen and the energy problem]] — the question the paper was written to settle&lt;br /&gt;
* [[Noether&#039;s theorems/Explainers/Symmetry and conservation, the first theorem|The primer]] — plain language, no mathematics&lt;br /&gt;
* [[Noether&#039;s theorems/Second theorem/The two theorems side by side|The two theorems side by side]] — the distinction most accounts lose&lt;br /&gt;
&lt;br /&gt;
([[Noether&#039;s theorems|Full article...]])&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-maxwell-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-maxwell-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Work of James Clerk Maxwell&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-maxwell&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== On Physical Lines of Force ==&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:OPL-fig-lines-of-force.svg|thumb|center|upright=1.5|Lines of force about a bar magnet]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In four instalments between March 1861 and February 1862, James Clerk Maxwell&lt;br /&gt;
filled space with spinning cells and little rolling particles, to explain the mechanics behind magnetic fields. &#039;&#039;&#039;His machine was wrong.&#039;&#039;&#039; On the way to building it,&lt;br /&gt;
he wrote down the displacement current, derived the speed of light from two&lt;br /&gt;
electrical measurements that had nothing to do with optics, and founded field&lt;br /&gt;
theory.&lt;br /&gt;
 &lt;br /&gt;
A 65-page reading edition: Maxwell&#039;s argument in his own order and register, the&lt;br /&gt;
modern equations derived from his results, and a plain-language explainer for&lt;br /&gt;
every major idea.&lt;br /&gt;
 &lt;br /&gt;
* [[On Physical Lines of Force/Introduction|Introduction]] — the story, and why the paper matters&lt;br /&gt;
* [[On Physical Lines of Force/Explainers|The primer]] — plain language, no mathematics&lt;br /&gt;
* [[On Physical Lines of Force/Explainers/The missing term|The missing term]] — the one addition that made radio possible&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[On_Physical_Lines_of_Force|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-toolkit-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-toolkit-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Research Toolkit&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-toolkit&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;graphviz&amp;gt;&lt;br /&gt;
digraph mp_toolkit {&lt;br /&gt;
  rankdir=TB; bgcolor=&amp;quot;transparent&amp;quot;; nodesep=0.2; ranksep=0.3;&lt;br /&gt;
  node [shape=box, style=&amp;quot;rounded,filled&amp;quot;, fillcolor=&amp;quot;#eaf3ff&amp;quot;, color=&amp;quot;#6a8fbf&amp;quot;, fontname=&amp;quot;Helvetica&amp;quot;, fontsize=10];&lt;br /&gt;
  edge [color=&amp;quot;#6a8fbf&amp;quot;, arrowsize=0.6];&lt;br /&gt;
  M [label=&amp;quot;The manual\nstart here&amp;quot;, fillcolor=&amp;quot;#ffffff&amp;quot;];&lt;br /&gt;
  F [label=&amp;quot;Agent flow\ncontrol\n39 practices&amp;quot;];&lt;br /&gt;
  R [label=&amp;quot;Research\nmethods\n59 techniques&amp;quot;];&lt;br /&gt;
  T [label=&amp;quot;Research\ntools\n22 + 55 tools&amp;quot;];&lt;br /&gt;
  B [label=&amp;quot;Bibliography\n284 sources&amp;quot;, shape=note, style=filled, fillcolor=&amp;quot;#ffffff&amp;quot;];&lt;br /&gt;
  M -&amp;gt; F; M -&amp;gt; R; M -&amp;gt; T; F -&amp;gt; B; R -&amp;gt; B; T -&amp;gt; B;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/graphviz&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Everything an AI agent, or a person, needs to do research on this wiki, in one place. &#039;&#039;&#039;An AI arriving here starts with [[The Principia Machina/Research Toolkit/Manual|the manual]].&#039;&#039;&#039; The toolkit has three parts:&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/Research Toolkit/Agent flow control|Agent flow control]]&#039;&#039;&#039; &amp;amp;ndash; how an agent plans, checks, retries, escalates and stays safe: thirty-nine practices with their evidence.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/Research Toolkit/Research methods|Research methods]]&#039;&#039;&#039; &amp;amp;ndash; how to solve an abstract problem, check the answer and report it: fifty-nine techniques and the process from question to compared result.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/Research Toolkit/Research tools|Research tools]]&#039;&#039;&#039; &amp;amp;ndash; the programs and services, assessed: the twenty-two [[The Principia Machina/Tools|physics tools]] and fifty-five general tools.&lt;br /&gt;
With [[The Principia Machina/Research Toolkit/Bibliography|the bibliography]] (284 sources, each with a note of how it was checked) and [[The Principia Machina/Agent/Research toolkit|a card for AI agents]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[The Principia Machina/Research Toolkit|The full toolkit...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;!-- pma:begin lean-edition --&amp;gt;&lt;br /&gt;
&amp;lt;!-- pma:end lean-edition --&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Full-width sections --&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-lower&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-plate-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #ffedad; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Featured plate&amp;lt;/h2&amp;gt;&lt;br /&gt;
 &amp;lt;div id=&amp;quot;mp-plate&amp;quot; style=&amp;quot;padding: 10px; text-align: left; display: flex; flex-wrap: wrap; flex-direction: row-reverse; gap: 1em; align-items: flex-start;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-plate-box&amp;quot; style=&amp;quot;flex: 0 1 300px; max-width: 100%; margin: 0 auto;&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;infobox&amp;quot; style=&amp;quot;width: 100%; box-sizing: border-box; margin: 0; font-size: 90%; background: #f9f9f9; border: 1px solid #aaa; padding: 5px;&amp;quot;&lt;br /&gt;
|+ style=&amp;quot;font-size: 120%; font-weight: bold; padding-bottom: 5px;&amp;quot; | Analytical Foundations of Physics&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center;&amp;quot; | [[File:Lagrange_portrait.jpg|250px|alt=Portrait of Joseph-Louis Lagrange]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center; font-size: smaller; padding-bottom: 10px;&amp;quot; | &#039;&#039;The shift from Newtonian vectors to scalar fields and variational principles defined modern theoretical physics.&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; style=&amp;quot;background: #ccf; text-align: center;&amp;quot; | Core Frameworks&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Classical Mechanics&#039;&#039;&#039; || [[Lagrangian mechanics]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Dynamical Optimization&#039;&#039;&#039; || [[Principle of least action]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Electromagnetism&#039;&#039;&#039; || [[Maxwell&#039;s equations]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Vacuum Dynamics&#039;&#039;&#039; || [[Spacetime topology]]&lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; style=&amp;quot;background: #ccf; text-align: center;&amp;quot; | Key Equations&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center; padding: 5px;&amp;quot; |&lt;br /&gt;
&amp;lt;math&amp;gt;S = \int L \, dt&amp;lt;/math&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;math&amp;gt;G_{\mu\nu} + \Lambda g_{\mu\nu} = \frac{8\pi G}{c^4} T_{\mu\nu}&amp;lt;/math&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-plate-text&amp;quot; style=&amp;quot;flex: 1 1 320px; min-width: 0;&amp;quot;&amp;gt;&lt;br /&gt;
== [[Timeline of Physics]] ==&lt;br /&gt;
The narrative of 18th- to 20th-century physics lies in a profound mathematical restructuring. This era marked the transition from treating nature as a collection of forces acting on point masses to understanding it through continuous fields, spacetime manifolds, and unified variational principles.&lt;br /&gt;
&lt;br /&gt;
The foundation was laid when physical systems began to be analyzed &#039;&#039;&#039;not through Newtonian vectors, but through scalar quantities—kinetic and potential energy—operating within generalized coordinates.&#039;&#039;&#039; By positing that the true dynamical trajectory of any system is the one that leaves the action integral stationary, &#039;&#039;&#039;theorists established a universal mathematical language.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This analytical approach seamlessly extended beyond mechanical gears and pulleys into the continuum. It provided the structural mathematics required to unify electricity and magnetism into a single vacuum field theory, and later, to model gravity not as a pulling force, but as the dynamic geometric curvature of spacetime itself. Whether applied to subatomic particle behavior or cosmic expansion, these foundational principles continue to govern the leading edge of modern physics.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== [[The Principia Machina/Tools|Physics Tools]] ==&lt;br /&gt;
Theoretical rigor must be paired with high-performance computational machinery. Twenty-two open tools are now surveyed for [[the Principia Machina]]; the first twelve cover three analytical frontiers:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The Inverse Action Problem:&#039;&#039;&#039; Discovering analytical scalar Lagrangians &amp;lt;math&amp;gt;\mathcal{L}(\phi, \partial_\mu \phi)&amp;lt;/math&amp;gt; and continuous Noether symmetries directly from perturbation data using [[The_Principia_Machina/Tools/PySR|PySR]] and [[The_Principia_Machina/Tools/AIFeynman|AI Feynman]].&lt;br /&gt;
* &#039;&#039;&#039;Variational &amp;amp; Mesh-Free Solvers:&#039;&#039;&#039; Minimizing continuous action integrals across complex geometries via Physics-Informed Neural Networks ([[The_Principia_Machina/Tools/DeepXDE|DeepXDE]]) and symbolic finite-element/difference stencils ([[The_Principia_Machina/Tools/FEniCS|FEniCS]] &amp;amp; [[The_Principia_Machina/Tools/Devito|Devito]]).&lt;br /&gt;
* &#039;&#039;&#039;Spacetime &amp;amp; Tensor Algebra:&#039;&#039;&#039; Evaluating functional variational derivatives in [[The_Principia_Machina/Tools/Cadabra2|Cadabra2]], 3+1 ADM spacetime evolution in the [[The_Principia_Machina/Tools/EinsteinToolkit|Einstein Toolkit]], and open quantum dynamics in [[The_Principia_Machina/Tools/QuTiP|QuTiP]].&lt;br /&gt;
&lt;br /&gt;
Ten more were added on 2026-10-06: SymPy, SageMath, xAct, Lean with Mathlib and Physlib, FORM, FeynCalc, Lagrangian and Hamiltonian networks, PySINDy, Dedalus and SpECTRE ([[The Principia Machina/Tools#The additions of 2026-10-06|the additions]]). All twenty-two are in [[The Principia Machina/Research Toolkit/Research tools|the Research Toolkit&#039;s third part]], beside fifty-five general tools.&lt;br /&gt;
&lt;br /&gt;
Read it your way: &#039;&#039;&#039;[[The Principia Machina/Tools/General reader|in plain language]]&#039;&#039;&#039; &amp;amp;middot; &#039;&#039;&#039;[[The Principia Machina/Tools/Operator&#039;s guide|the operator&#039;s guide]]&#039;&#039;&#039; &amp;amp;middot; &#039;&#039;&#039;[[The Principia Machina/Agent/Tools|for AI agents]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[The Principia Machina/Tools|Full survey and domain evaluation...]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-other-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-other&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Other areas of Ipsum Invarians&amp;lt;/h2&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-other-content&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
* &#039;&#039;&#039;[[Special:AllPages|All pages]]&#039;&#039;&#039; &amp;amp;ndash; ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:RecentChanges|Recent changes]]&#039;&#039;&#039; &amp;amp;ndash; nisi ut aliquip ex ea commodo consequat duis aute irure.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:Categories|Categories]]&#039;&#039;&#039; &amp;amp;ndash; dolor in reprehenderit in voluptate velit esse cillum dolore.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:SpecialPages|Special pages]]&#039;&#039;&#039; &amp;amp;ndash; eu fugiat nulla pariatur excepteur sint occaecat cupidatat.&lt;br /&gt;
* &#039;&#039;&#039;[[Project:Sandbox|Sandbox]]&#039;&#039;&#039; &amp;amp;ndash; non proident, sunt in culpa qui officia deserunt mollit anim.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:Upload|Upload]]&#039;&#039;&#039; &amp;amp;ndash; id est laborum sed ut perspiciatis unde omnis iste natus error.&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-lang-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-lang&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Ipsum Invarians languages&amp;lt;/h2&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-lang-content&amp;quot; style=&amp;quot;padding: 10px; text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
Totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;&#039;&#039;Language editions are not yet configured. Set them up with [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Interwiki interwiki links] or [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Translate Extension:Translate].&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;__NOTOC____NOEDITSECTION__&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=Main_Page&amp;diff=4309</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=Main_Page&amp;diff=4309"/>
		<updated>2026-09-28T20:23:05Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;&amp;lt;!-- IPSUM INVARIANS - Main Page. Box structure per supplied template; styles inline so the page renders with no extensions installed. mp-* ids retained so a later stylesheet can override without editing wikitext. --&amp;gt;&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&amp;lt;!-- Top banner --&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-topbanner&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #f8f9fa; padding: 10px; text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-welcome&amp;quot;&amp;gt;&amp;lt;h1 style=&amp;quot;margin: 0; border: none; padding: 0.1em; font-size: 1.8em; font-weight: normal;&amp;quot;&amp;gt;IPSUM INVARIANS: The Invariance Itself&lt;br /&gt;
&amp;lt;/h1&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-free&amp;quot; style=&amp;quot;font-size: 0.95em;&amp;quot;&amp;gt;The public record of the invariance program. est. 1 September 2026&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;articlecount&amp;quot; style=&amp;quot;font-size: 0.85em; margin-top: 0.3em;&amp;quot;&amp;gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles &amp;amp;middot; [[Special:Statistics|{{NUMBEROFACTIVEUSERS}}]] active editors &amp;amp;middot; [[Special:RecentChanges|{{NUMBEROFEDITS}} edits]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Main Container using Flexbox for responsiveness --&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;display: flex; flex-wrap: wrap; gap: 15px; justify-content: space-between;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;!-- Left Column --&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-left&amp;quot; style=&amp;quot;flex: 1 1 48%; min-width: 300px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Green Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-intro-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-intro-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cef2e0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Introduction&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-intro&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;Please be patient as we pull this site together.  Check back often for the latest developments.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Welcome to Ipsum Invarians, a platform built in four sections:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Arena&#039;&#039;&#039; (Principia Machina): Essentially, this venue functions as an evaluation framework for testing physical hypotheses using artificial intelligence. It provides an AI protocol and a public research registry. We call this framework &#039;&#039;[[the Principia Machina]].&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Weapon&#039;&#039;&#039; (Hamilton&#039;s Principle): Our namesake reflects what is arguably the single most important formulation in physics: the Action Principle or even Hamilton&#039;s principle. In our gladiatorial arena, [[Hamilton&#039;s principle]] is the sharpest, most lethal weapon available. To give this underappreciated concept its due, Ipsum Invarians carries a dedicated field manual for Hamilton’s Principle and its attendant [[Noether&#039;s theorems|Noether&#039;s theorem]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Gladiator&#039;&#039;&#039; (SVD): Continuing the metaphor, our local gladiator is Structured Vacuum Dynamics (SVD). SVD enters the arena with a specific postulate: that a single permutation of Maxwell’s 1861 paper, Hamilton’s Principle, and Noether&#039;s First Theorem is sufficient to populate all of physics.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Blueprint&#039;&#039;&#039; (Specifications): [[The_Principia_Machina/Hub/General_reader|Complete specifications]] for the Principia Machina and its standard prompt setup are openly published to ensure transparency and replication.  However, for security and reliability reasons, some internal testing functionality are only offered as pseudo code rather than providing the full testing paradigm.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Introduction|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Green Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-round-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-round-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cef2e0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Current Program (Round 3)&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-round&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
Round 3 Phase 1: (WIP) Development of &#039;&#039;&#039;[[the Principia Machina]]:&#039;&#039;&#039; an AI Harness inspired physics solver/research platform implemented in MediaWiki.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Round 3 Phase 2: (Imminent) Testing the Principia Machina - look for updates this week.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Round 3 Phase 3: (TBD) Testing Postulates using the Principia Machina&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Round 3|Program of record...]])&#039;&#039;&#039; &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; [[Round 3/Open items|Open items]]&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Grey Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-history-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-history-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Program History&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-history&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
We started with a simple permutation of Maxwell&#039;s 1861 framework that yielded a promising interpretation of General Relativity. We applied a second permutation; analyzed it with tabletop testing and back-of-the-envelope calculations, and found we could derive both the eigenstates of hydrogen and chromodynamics. These two disparate domains (GR &amp;amp; QM) long advertised as incompatible, seem to be perfectly harmonious derivations from Maxwell&#039;s 1861 work. The result suggests a viable postulate: if we constrain ourselves with Hamilton’s Principle and Noether’s First Theorem,  can we build all of physics from a single assumption? From two assumptions?&lt;br /&gt;
&lt;br /&gt;
[[File:Modified vorticie.jpg|thumb|center|upright=1.5|A simple permutation of Maxwell&#039;s 1861 framework.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The idea is daunting, but maybe AI can help.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 1&#039;&#039;&#039; &amp;amp;ndash; Technical paper: Structured Vacuum Dynamics &lt;br /&gt;
&lt;br /&gt;
This was more of a proof of concept: would AI confirm the math or maybe find new paradigms to fit the otherwise disparate math together?  We started with a simple technical paper around the postulate and a strict set of AI controls and restrictions.  We designed a rigerous prompt that pitted the AI Agent against itself, doing more work to double and triple check its results than the original work to get the results, but this effort quickly overwhelmed the local AI context.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 2&#039;&#039;&#039; &amp;amp;ndash; The Research Register (RR-n)&lt;br /&gt;
&lt;br /&gt;
The Lesson from round 1 - physics is a much bigger domain than a single paper.  We did start to understand the context limits of the most reasonably available AI offerings and the constraints it left us with.  We broke the design into two parts: a back-end research register and a front-end that could generate papers from the research register.  Soon we ran into problems mapping the axioms to the environment.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 3 opening&#039;&#039;&#039; &amp;amp;ndash; The Principia Machina (TPM)&lt;br /&gt;
&lt;br /&gt;
The Lesson from round 2 - Local AI context was never going to be enough for any serious work.  We realized we could kill three birds with one stone if we moved the research context to a Wiki:&lt;br /&gt;
#The context would be effectively unlimited&lt;br /&gt;
#A public, formalized, framework would foster independent verification&lt;br /&gt;
#it would give a great public record to invite collaboration and outside ideas&lt;br /&gt;
&lt;br /&gt;
Thus &#039;&#039;&#039;[[the Principia Machina]]:&#039;&#039;&#039; an AI Harness inspired physics solver/research platform and test bed implemented in MediaWiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Program history|Full record...]])&#039;&#039;&#039; &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; [[Program history/Archive|Archive]]&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Grey Box ?--&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-round-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-round-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Principia Machina Specification (TPS) &amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-round&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina Specification&#039;&#039;&#039; (TPS) is the complete, published&lt;br /&gt;
description of The Principia Machina (TPM), a set of rules for doing research&lt;br /&gt;
with AI assistants so that the result can be checked afterwards by anyone.&lt;br /&gt;
TPS is written for two readers at once: a person who wants to understand how&lt;br /&gt;
the framework works, and an AI agent of any make that wants to work under it.&lt;br /&gt;
It is one of five parts, and it is the part that binds the other four.&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;The foundations record.&#039;&#039;&#039; A dated account of every design decision, the options rejected, and the reasons. It is the source TPS was written from. It describes; it never instructs.&lt;br /&gt;
# &#039;&#039;&#039;The specification.&#039;&#039;&#039; This document. It defines the five layers of the framework, the sealed container a piece of research lives in, the wiki machinery that records the work, and the Agent Contract: the rules any AI agent follows to work a container. It is versioned, and its fingerprint is the first line of the wiki&#039;s chain of declarations.&lt;br /&gt;
# &#039;&#039;&#039;The implementations.&#039;&#039;&#039; What runs the rules. On the server, TPX, a MediaWiki extension that performs every check a machine can perform. Beside the agent, PRB, the client an agent uses to hold its working copy and land results. And each agent&#039;s own instruction set, implementing the Agent Contract. The project&#039;s own instruction set, PMP-TPM, is written for Claude and is one implementation among any number.&lt;br /&gt;
# &#039;&#039;&#039;The wiki.&#039;&#039;&#039; Where all of the above is published and read, and the system of record for everything TPM does.&lt;br /&gt;
# &#039;&#039;&#039;The containers.&#039;&#039;&#039; The research itself: a sealed set of laws and assumptions, and the register of findings built on it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;!-- Right Column --&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-right&amp;quot; style=&amp;quot;flex: 1 1 48%; min-width: 300px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-hamilton-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-hamilton-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Hamilton&#039;s Principle&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-hamilton&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
Newton&#039;s laws, Maxwell&#039;s equations, general relativity and the Standard Model are each formulated as an action via Hamilton&#039;s Principle.  Across all these domains, dynamical equations emerge as derived outcomes rather than fundamental starting axioms. Conservation of energy, momentum and charge are not separate laws at all — [[Hamilton&#039;s principle/Mathematics/Noether&#039;s first theorem|Noether proved]] they follow from the action&#039;s symmetries. New models are now built by writing the action constrained by symmetry and letting the dynamics follow.  This is how electromagnetism and gravity were derived and how the nuclear forces were found. Alone among classical concepts, &#039;&#039;&#039;Hamilton&#039;s Principle&#039;&#039;&#039; transitions smoothly into quantum mechanics, where the action represents a phase carried across distinct trajectories and the classical path marks where destructive interference is minimized.  The action is the deepest thing physics knows.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:OPL-HP-F-01.png|thumb|center|upright=1.5|A true path and several comparison paths between fixed endpoints.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Hamilton&#039;s principle/Mathematics/The Jacobi condition and conjugate points|Stationary is not least]] — the long way round a great circle obeys the same rule at every point, and is plainly not the shortest. [[:File:OPL-HP-F-05.png|See the diagram]].&lt;br /&gt;
* [[Hamilton&#039;s principle/Applications/The Feynman path integral|Why the rule holds at all]] — nature selects nothing. It sums over everything, and what looks like a choice is the residue left by interference.&lt;br /&gt;
* [[Hamilton&#039;s principle/Explainers/Comparing paths|Start without the mathematics]] — every page carrying equations has a plain-language counterpart, linked from it and linking back.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Hamilton&#039;s principle|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-noether-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-noether-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Noether&#039;s theorems&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-noether&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:NT-F-07.png|thumb|center|400px|alt=Continuous symmetries on the left, the quantities they conserve on the right, with the map between them|The symmetry-to-conservation map]]&lt;br /&gt;
&lt;br /&gt;
Klein read the paper to the Göttingen Scientific Society on 26 July 1918. Its&lt;br /&gt;
last section answers a claim of Hilbert&#039;s: that energy conservation in general&lt;br /&gt;
relativity fails to take the form it takes everywhere else in physics.&lt;br /&gt;
&#039;&#039;&#039;There are two theorems in the paper, and they are not versions of one another.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The initial theorem relates global, finite-parameter symmetries directly to corresponding physical conservation laws governing actual dynamics. The second takes a symmetry that is allowed to differ from place to place and returns identities between the&lt;br /&gt;
field equations — identities that hold whether or not those equations are&lt;br /&gt;
satisfied. The second theorem is why a gauge theory has fewer independent field&lt;br /&gt;
equations than it has fields, and why gravity has no local energy.&lt;br /&gt;
&lt;br /&gt;
A 90-page reading edition: both theorems proved in full and kept apart, the&lt;br /&gt;
mathematics they need, the physics they explain, and a plain-language&lt;br /&gt;
counterpart for every page that carries equations.&lt;br /&gt;
&lt;br /&gt;
* [[Noether&#039;s theorems/History/Gottingen and the energy problem|Göttingen and the energy problem]] — the question the paper was written to settle&lt;br /&gt;
* [[Noether&#039;s theorems/Explainers/Symmetry and conservation, the first theorem|The primer]] — plain language, no mathematics&lt;br /&gt;
* [[Noether&#039;s theorems/Second theorem/The two theorems side by side|The two theorems side by side]] — the distinction most accounts lose&lt;br /&gt;
&lt;br /&gt;
([[Noether&#039;s theorems|Full article...]])&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-maxwell-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-maxwell-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Work of James Clerk Maxwell&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-maxwell&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== On Physical Lines of Force ==&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:OPL-fig-lines-of-force.svg|thumb|center|upright=1.5|Lines of force about a bar magnet]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In four instalments between March 1861 and February 1862, James Clerk Maxwell&lt;br /&gt;
filled space with spinning cells and little rolling particles, to explain the mechanics behind magnetic fields. &#039;&#039;&#039;His machine was wrong.&#039;&#039;&#039; On the way to building it,&lt;br /&gt;
he wrote down the displacement current, derived the speed of light from two&lt;br /&gt;
electrical measurements that had nothing to do with optics, and founded field&lt;br /&gt;
theory.&lt;br /&gt;
 &lt;br /&gt;
A 65-page reading edition: Maxwell&#039;s argument in his own order and register, the&lt;br /&gt;
modern equations derived from his results, and a plain-language explainer for&lt;br /&gt;
every major idea.&lt;br /&gt;
 &lt;br /&gt;
* [[On Physical Lines of Force/Introduction|Introduction]] — the story, and why the paper matters&lt;br /&gt;
* [[On Physical Lines of Force/Explainers|The primer]] — plain language, no mathematics&lt;br /&gt;
* [[On Physical Lines of Force/Explainers/The missing term|The missing term]] — the one addition that made radio possible&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[On_Physical_Lines_of_Force|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Full-width sections --&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-lower&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-plate-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #ffedad; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Featured plate&amp;lt;/h2&amp;gt;&lt;br /&gt;
 &amp;lt;div id=&amp;quot;mp-plate&amp;quot; style=&amp;quot;padding: 10px; text-align: left; display: flex; flex-wrap: wrap; flex-direction: row-reverse; gap: 1em; align-items: flex-start;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-plate-box&amp;quot; style=&amp;quot;flex: 0 1 300px; max-width: 100%; margin: 0 auto;&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;infobox&amp;quot; style=&amp;quot;width: 100%; box-sizing: border-box; margin: 0; font-size: 90%; background: #f9f9f9; border: 1px solid #aaa; padding: 5px;&amp;quot;&lt;br /&gt;
|+ style=&amp;quot;font-size: 120%; font-weight: bold; padding-bottom: 5px;&amp;quot; | Analytical Foundations of Physics&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center;&amp;quot; | [[File:Lagrange_portrait.jpg|250px|alt=Portrait of Joseph-Louis Lagrange]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center; font-size: smaller; padding-bottom: 10px;&amp;quot; | &#039;&#039;The shift from Newtonian vectors to scalar fields and variational principles defined modern theoretical physics.&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; style=&amp;quot;background: #ccf; text-align: center;&amp;quot; | Core Frameworks&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Classical Mechanics&#039;&#039;&#039; || [[Lagrangian mechanics]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Dynamical Optimization&#039;&#039;&#039; || [[Principle of least action]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Electromagnetism&#039;&#039;&#039; || [[Maxwell&#039;s equations]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Vacuum Dynamics&#039;&#039;&#039; || [[Spacetime topology]]&lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; style=&amp;quot;background: #ccf; text-align: center;&amp;quot; | Key Equations&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center; padding: 5px;&amp;quot; |&lt;br /&gt;
&amp;lt;math&amp;gt;S = \int L \, dt&amp;lt;/math&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;math&amp;gt;G_{\mu\nu} + \Lambda g_{\mu\nu} = \frac{8\pi G}{c^4} T_{\mu\nu}&amp;lt;/math&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-plate-text&amp;quot; style=&amp;quot;flex: 1 1 320px; min-width: 0;&amp;quot;&amp;gt;&lt;br /&gt;
== [[Timeline of Physics]] ==&lt;br /&gt;
The narrative of 18th- to 20th-century physics lies in a profound mathematical restructuring. This era marked the transition from treating nature as a collection of forces acting on point masses to understanding it through continuous fields, spacetime manifolds, and unified variational principles.&lt;br /&gt;
&lt;br /&gt;
The foundation was laid when physical systems began to be analyzed &#039;&#039;&#039;not through Newtonian vectors, but through scalar quantities—kinetic and potential energy—operating within generalized coordinates.&#039;&#039;&#039; By positing that the true dynamical trajectory of any system is the one that leaves the action integral stationary, &#039;&#039;&#039;theorists established a universal mathematical language.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This analytical approach seamlessly extended beyond mechanical gears and pulleys into the continuum. It provided the structural mathematics required to unify electricity and magnetism into a single vacuum field theory, and later, to model gravity not as a pulling force, but as the dynamic geometric curvature of spacetime itself. Whether applied to subatomic particle behavior or cosmic expansion, these foundational principles continue to govern the leading edge of modern physics.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Physics Tools ==&lt;br /&gt;
Theoretical rigor must be paired with high-performance computational machinery. The **Principia Machina** framework organizes these tools across three analytical frontiers:&lt;br /&gt;
&lt;br /&gt;
* **The Inverse Action Problem:** Discovering analytical scalar Lagrangians &amp;lt;math&amp;gt;\mathcal{L}(\phi, \partial_\mu \phi)&amp;lt;/math&amp;gt; and continuous Noether symmetries directly from perturbation data using [[The_Principia_Machina/Tools/PySR|PySR]] and [[The_Principia_Machina/Tools/AIFeynman|AI Feynman]].&lt;br /&gt;
* **Variational &amp;amp; Mesh-Free Solvers:** Minimizing continuous action integrals across complex geometries via Physics-Informed Neural Networks ([[The_Principia_Machina/Tools/DeepXDE|DeepXDE]]) and symbolic finite-element/difference stencils ([[The_Principia_Machina/Tools/FEniCS|FEniCS]] &amp;amp; [[The_Principia_Machina/Tools/Devito|Devito]]).&lt;br /&gt;
* **Spacetime &amp;amp; Tensor Algebra:** Evaluating functional variational derivatives in [[The_Principia_Machina/Tools/Cadabra2|Cadabra2]], 3+1 ADM spacetime evolution in the [[The_Principia_Machina/Tools/EinsteinToolkit|Einstein Toolkit]], and open quantum dynamics in [[The_Principia_Machina/Tools/QuTiP|QuTiP]].&lt;br /&gt;
&lt;br /&gt;
([[Full survey and domain evaluation...|The_Principia_Machina/Tools]])&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-other-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-other&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Other areas of Ipsum Invarians&amp;lt;/h2&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-other-content&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
* &#039;&#039;&#039;[[Special:AllPages|All pages]]&#039;&#039;&#039; &amp;amp;ndash; ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:RecentChanges|Recent changes]]&#039;&#039;&#039; &amp;amp;ndash; nisi ut aliquip ex ea commodo consequat duis aute irure.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:Categories|Categories]]&#039;&#039;&#039; &amp;amp;ndash; dolor in reprehenderit in voluptate velit esse cillum dolore.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:SpecialPages|Special pages]]&#039;&#039;&#039; &amp;amp;ndash; eu fugiat nulla pariatur excepteur sint occaecat cupidatat.&lt;br /&gt;
* &#039;&#039;&#039;[[Project:Sandbox|Sandbox]]&#039;&#039;&#039; &amp;amp;ndash; non proident, sunt in culpa qui officia deserunt mollit anim.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:Upload|Upload]]&#039;&#039;&#039; &amp;amp;ndash; id est laborum sed ut perspiciatis unde omnis iste natus error.&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-lang-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-lang&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Ipsum Invarians languages&amp;lt;/h2&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-lang-content&amp;quot; style=&amp;quot;padding: 10px; text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
Totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;&#039;&#039;Language editions are not yet configured. Set them up with [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Interwiki interwiki links] or [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Translate Extension:Translate].&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;__NOTOC____NOEDITSECTION__&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=Main_Page&amp;diff=4308</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=Main_Page&amp;diff=4308"/>
		<updated>2026-09-28T20:22:13Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;&amp;lt;!-- IPSUM INVARIANS - Main Page. Box structure per supplied template; styles inline so the page renders with no extensions installed. mp-* ids retained so a later stylesheet can override without editing wikitext. --&amp;gt;&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&amp;lt;!-- Top banner --&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-topbanner&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #f8f9fa; padding: 10px; text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-welcome&amp;quot;&amp;gt;&amp;lt;h1 style=&amp;quot;margin: 0; border: none; padding: 0.1em; font-size: 1.8em; font-weight: normal;&amp;quot;&amp;gt;IPSUM INVARIANS: The Invariance Itself&lt;br /&gt;
&amp;lt;/h1&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-free&amp;quot; style=&amp;quot;font-size: 0.95em;&amp;quot;&amp;gt;The public record of the invariance program. est. 1 September 2026&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;articlecount&amp;quot; style=&amp;quot;font-size: 0.85em; margin-top: 0.3em;&amp;quot;&amp;gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles &amp;amp;middot; [[Special:Statistics|{{NUMBEROFACTIVEUSERS}}]] active editors &amp;amp;middot; [[Special:RecentChanges|{{NUMBEROFEDITS}} edits]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Main Container using Flexbox for responsiveness --&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;display: flex; flex-wrap: wrap; gap: 15px; justify-content: space-between;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;!-- Left Column --&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-left&amp;quot; style=&amp;quot;flex: 1 1 48%; min-width: 300px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Green Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-intro-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-intro-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cef2e0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Introduction&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-intro&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;Please be patient as we pull this site together.  Check back often for the latest developments.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Welcome to Ipsum Invarians, a platform built in four sections:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Arena&#039;&#039;&#039; (Principia Machina): Essentially, this venue functions as an evaluation framework for testing physical hypotheses using artificial intelligence. It provides an AI protocol and a public research registry. We call this framework &#039;&#039;[[the Principia Machina]].&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Weapon&#039;&#039;&#039; (Hamilton&#039;s Principle): Our namesake reflects what is arguably the single most important formulation in physics: the Action Principle or even Hamilton&#039;s principle. In our gladiatorial arena, [[Hamilton&#039;s principle]] is the sharpest, most lethal weapon available. To give this underappreciated concept its due, Ipsum Invarians carries a dedicated field manual for Hamilton’s Principle and its attendant [[Noether&#039;s theorems|Noether&#039;s theorem]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Gladiator&#039;&#039;&#039; (SVD): Continuing the metaphor, our local gladiator is Structured Vacuum Dynamics (SVD). SVD enters the arena with a specific postulate: that a single permutation of Maxwell’s 1861 paper, Hamilton’s Principle, and Noether&#039;s First Theorem is sufficient to populate all of physics.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Blueprint&#039;&#039;&#039; (Specifications): [[The_Principia_Machina/Hub/General_reader|Complete specifications]] for the Principia Machina and its standard prompt setup are openly published to ensure transparency and replication.  However, for security and reliability reasons, some internal testing functionality are only offered as pseudo code rather than providing the full testing paradigm.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Introduction|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Green Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-round-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-round-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cef2e0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Current Program (Round 3)&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-round&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
Round 3 Phase 1: (WIP) Development of &#039;&#039;&#039;[[the Principia Machina]]:&#039;&#039;&#039; an AI Harness inspired physics solver/research platform implemented in MediaWiki.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Round 3 Phase 2: (Emanate) Testing the Principia Machina - look for updates this week.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Round 3 Phase 3: (TBD) Testing Postulates using the Principia Machina&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Round 3|Program of record...]])&#039;&#039;&#039; &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; [[Round 3/Open items|Open items]]&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Grey Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-history-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-history-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Program History&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-history&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
We started with a simple permutation of Maxwell&#039;s 1861 framework that yielded a promising interpretation of General Relativity. We applied a second permutation; analyzed it with tabletop testing and back-of-the-envelope calculations, and found we could derive both the eigenstates of hydrogen and chromodynamics. These two disparate domains (GR &amp;amp; QM) long advertised as incompatible, seem to be perfectly harmonious derivations from Maxwell&#039;s 1861 work. The result suggests a viable postulate: if we constrain ourselves with Hamilton’s Principle and Noether’s First Theorem,  can we build all of physics from a single assumption? From two assumptions?&lt;br /&gt;
&lt;br /&gt;
[[File:Modified vorticie.jpg|thumb|center|upright=1.5|A simple permutation of Maxwell&#039;s 1861 framework.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The idea is daunting, but maybe AI can help.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 1&#039;&#039;&#039; &amp;amp;ndash; Technical paper: Structured Vacuum Dynamics &lt;br /&gt;
&lt;br /&gt;
This was more of a proof of concept: would AI confirm the math or maybe find new paradigms to fit the otherwise disparate math together?  We started with a simple technical paper around the postulate and a strict set of AI controls and restrictions.  We designed a rigerous prompt that pitted the AI Agent against itself, doing more work to double and triple check its results than the original work to get the results, but this effort quickly overwhelmed the local AI context.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 2&#039;&#039;&#039; &amp;amp;ndash; The Research Register (RR-n)&lt;br /&gt;
&lt;br /&gt;
The Lesson from round 1 - physics is a much bigger domain than a single paper.  We did start to understand the context limits of the most reasonably available AI offerings and the constraints it left us with.  We broke the design into two parts: a back-end research register and a front-end that could generate papers from the research register.  Soon we ran into problems mapping the axioms to the environment.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Round 3 opening&#039;&#039;&#039; &amp;amp;ndash; The Principia Machina (TPM)&lt;br /&gt;
&lt;br /&gt;
The Lesson from round 2 - Local AI context was never going to be enough for any serious work.  We realized we could kill three birds with one stone if we moved the research context to a Wiki:&lt;br /&gt;
#The context would be effectively unlimited&lt;br /&gt;
#A public, formalized, framework would foster independent verification&lt;br /&gt;
#it would give a great public record to invite collaboration and outside ideas&lt;br /&gt;
&lt;br /&gt;
Thus &#039;&#039;&#039;[[the Principia Machina]]:&#039;&#039;&#039; an AI Harness inspired physics solver/research platform and test bed implemented in MediaWiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Program history|Full record...]])&#039;&#039;&#039; &amp;amp;nbsp;&amp;amp;middot;&amp;amp;nbsp; [[Program history/Archive|Archive]]&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Grey Box ?--&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-round-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-round-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Principia Machina Specification (TPS) &amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-round&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina Specification&#039;&#039;&#039; (TPS) is the complete, published&lt;br /&gt;
description of The Principia Machina (TPM), a set of rules for doing research&lt;br /&gt;
with AI assistants so that the result can be checked afterwards by anyone.&lt;br /&gt;
TPS is written for two readers at once: a person who wants to understand how&lt;br /&gt;
the framework works, and an AI agent of any make that wants to work under it.&lt;br /&gt;
It is one of five parts, and it is the part that binds the other four.&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;The foundations record.&#039;&#039;&#039; A dated account of every design decision, the options rejected, and the reasons. It is the source TPS was written from. It describes; it never instructs.&lt;br /&gt;
# &#039;&#039;&#039;The specification.&#039;&#039;&#039; This document. It defines the five layers of the framework, the sealed container a piece of research lives in, the wiki machinery that records the work, and the Agent Contract: the rules any AI agent follows to work a container. It is versioned, and its fingerprint is the first line of the wiki&#039;s chain of declarations.&lt;br /&gt;
# &#039;&#039;&#039;The implementations.&#039;&#039;&#039; What runs the rules. On the server, TPX, a MediaWiki extension that performs every check a machine can perform. Beside the agent, PRB, the client an agent uses to hold its working copy and land results. And each agent&#039;s own instruction set, implementing the Agent Contract. The project&#039;s own instruction set, PMP-TPM, is written for Claude and is one implementation among any number.&lt;br /&gt;
# &#039;&#039;&#039;The wiki.&#039;&#039;&#039; Where all of the above is published and read, and the system of record for everything TPM does.&lt;br /&gt;
# &#039;&#039;&#039;The containers.&#039;&#039;&#039; The research itself: a sealed set of laws and assumptions, and the register of findings built on it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;!-- Right Column --&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-right&amp;quot; style=&amp;quot;flex: 1 1 48%; min-width: 300px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-hamilton-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-hamilton-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Hamilton&#039;s Principle&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-hamilton&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
Newton&#039;s laws, Maxwell&#039;s equations, general relativity and the Standard Model are each formulated as an action via Hamilton&#039;s Principle.  Across all these domains, dynamical equations emerge as derived outcomes rather than fundamental starting axioms. Conservation of energy, momentum and charge are not separate laws at all — [[Hamilton&#039;s principle/Mathematics/Noether&#039;s first theorem|Noether proved]] they follow from the action&#039;s symmetries. New models are now built by writing the action constrained by symmetry and letting the dynamics follow.  This is how electromagnetism and gravity were derived and how the nuclear forces were found. Alone among classical concepts, &#039;&#039;&#039;Hamilton&#039;s Principle&#039;&#039;&#039; transitions smoothly into quantum mechanics, where the action represents a phase carried across distinct trajectories and the classical path marks where destructive interference is minimized.  The action is the deepest thing physics knows.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:OPL-HP-F-01.png|thumb|center|upright=1.5|A true path and several comparison paths between fixed endpoints.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [[Hamilton&#039;s principle/Mathematics/The Jacobi condition and conjugate points|Stationary is not least]] — the long way round a great circle obeys the same rule at every point, and is plainly not the shortest. [[:File:OPL-HP-F-05.png|See the diagram]].&lt;br /&gt;
* [[Hamilton&#039;s principle/Applications/The Feynman path integral|Why the rule holds at all]] — nature selects nothing. It sums over everything, and what looks like a choice is the residue left by interference.&lt;br /&gt;
* [[Hamilton&#039;s principle/Explainers/Comparing paths|Start without the mathematics]] — every page carrying equations has a plain-language counterpart, linked from it and linking back.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[Hamilton&#039;s principle|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-noether-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-noether-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Noether&#039;s theorems&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-noether&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:NT-F-07.png|thumb|center|400px|alt=Continuous symmetries on the left, the quantities they conserve on the right, with the map between them|The symmetry-to-conservation map]]&lt;br /&gt;
&lt;br /&gt;
Klein read the paper to the Göttingen Scientific Society on 26 July 1918. Its&lt;br /&gt;
last section answers a claim of Hilbert&#039;s: that energy conservation in general&lt;br /&gt;
relativity fails to take the form it takes everywhere else in physics.&lt;br /&gt;
&#039;&#039;&#039;There are two theorems in the paper, and they are not versions of one another.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The initial theorem relates global, finite-parameter symmetries directly to corresponding physical conservation laws governing actual dynamics. The second takes a symmetry that is allowed to differ from place to place and returns identities between the&lt;br /&gt;
field equations — identities that hold whether or not those equations are&lt;br /&gt;
satisfied. The second theorem is why a gauge theory has fewer independent field&lt;br /&gt;
equations than it has fields, and why gravity has no local energy.&lt;br /&gt;
&lt;br /&gt;
A 90-page reading edition: both theorems proved in full and kept apart, the&lt;br /&gt;
mathematics they need, the physics they explain, and a plain-language&lt;br /&gt;
counterpart for every page that carries equations.&lt;br /&gt;
&lt;br /&gt;
* [[Noether&#039;s theorems/History/Gottingen and the energy problem|Göttingen and the energy problem]] — the question the paper was written to settle&lt;br /&gt;
* [[Noether&#039;s theorems/Explainers/Symmetry and conservation, the first theorem|The primer]] — plain language, no mathematics&lt;br /&gt;
* [[Noether&#039;s theorems/Second theorem/The two theorems side by side|The two theorems side by side]] — the distinction most accounts lose&lt;br /&gt;
&lt;br /&gt;
([[Noether&#039;s theorems|Full article...]])&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Blue Box --&amp;gt;&lt;br /&gt;
    &amp;lt;div id=&amp;quot;mp-maxwell-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;h2 id=&amp;quot;mp-maxwell-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #cedff2; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;The Work of James Clerk Maxwell&amp;lt;/h2&amp;gt;&lt;br /&gt;
      &amp;lt;div id=&amp;quot;mp-maxwell&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== On Physical Lines of Force ==&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:OPL-fig-lines-of-force.svg|thumb|center|upright=1.5|Lines of force about a bar magnet]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In four instalments between March 1861 and February 1862, James Clerk Maxwell&lt;br /&gt;
filled space with spinning cells and little rolling particles, to explain the mechanics behind magnetic fields. &#039;&#039;&#039;His machine was wrong.&#039;&#039;&#039; On the way to building it,&lt;br /&gt;
he wrote down the displacement current, derived the speed of light from two&lt;br /&gt;
electrical measurements that had nothing to do with optics, and founded field&lt;br /&gt;
theory.&lt;br /&gt;
 &lt;br /&gt;
A 65-page reading edition: Maxwell&#039;s argument in his own order and register, the&lt;br /&gt;
modern equations derived from his results, and a plain-language explainer for&lt;br /&gt;
every major idea.&lt;br /&gt;
 &lt;br /&gt;
* [[On Physical Lines of Force/Introduction|Introduction]] — the story, and why the paper matters&lt;br /&gt;
* [[On Physical Lines of Force/Explainers|The primer]] — plain language, no mathematics&lt;br /&gt;
* [[On Physical Lines of Force/Explainers/The missing term|The missing term]] — the one addition that made radio possible&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;([[On_Physical_Lines_of_Force|Full article...]])&#039;&#039;&#039;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Full-width sections --&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-lower&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-plate-h2&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #ffedad; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Featured plate&amp;lt;/h2&amp;gt;&lt;br /&gt;
 &amp;lt;div id=&amp;quot;mp-plate&amp;quot; style=&amp;quot;padding: 10px; text-align: left; display: flex; flex-wrap: wrap; flex-direction: row-reverse; gap: 1em; align-items: flex-start;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-plate-box&amp;quot; style=&amp;quot;flex: 0 1 300px; max-width: 100%; margin: 0 auto;&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;infobox&amp;quot; style=&amp;quot;width: 100%; box-sizing: border-box; margin: 0; font-size: 90%; background: #f9f9f9; border: 1px solid #aaa; padding: 5px;&amp;quot;&lt;br /&gt;
|+ style=&amp;quot;font-size: 120%; font-weight: bold; padding-bottom: 5px;&amp;quot; | Analytical Foundations of Physics&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center;&amp;quot; | [[File:Lagrange_portrait.jpg|250px|alt=Portrait of Joseph-Louis Lagrange]]&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center; font-size: smaller; padding-bottom: 10px;&amp;quot; | &#039;&#039;The shift from Newtonian vectors to scalar fields and variational principles defined modern theoretical physics.&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; style=&amp;quot;background: #ccf; text-align: center;&amp;quot; | Core Frameworks&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Classical Mechanics&#039;&#039;&#039; || [[Lagrangian mechanics]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Dynamical Optimization&#039;&#039;&#039; || [[Principle of least action]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Electromagnetism&#039;&#039;&#039; || [[Maxwell&#039;s equations]]&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Vacuum Dynamics&#039;&#039;&#039; || [[Spacetime topology]]&lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; style=&amp;quot;background: #ccf; text-align: center;&amp;quot; | Key Equations&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; style=&amp;quot;text-align: center; padding: 5px;&amp;quot; |&lt;br /&gt;
&amp;lt;math&amp;gt;S = \int L \, dt&amp;lt;/math&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&amp;lt;math&amp;gt;G_{\mu\nu} + \Lambda g_{\mu\nu} = \frac{8\pi G}{c^4} T_{\mu\nu}&amp;lt;/math&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-plate-text&amp;quot; style=&amp;quot;flex: 1 1 320px; min-width: 0;&amp;quot;&amp;gt;&lt;br /&gt;
== [[Timeline of Physics]] ==&lt;br /&gt;
The narrative of 18th- to 20th-century physics lies in a profound mathematical restructuring. This era marked the transition from treating nature as a collection of forces acting on point masses to understanding it through continuous fields, spacetime manifolds, and unified variational principles.&lt;br /&gt;
&lt;br /&gt;
The foundation was laid when physical systems began to be analyzed &#039;&#039;&#039;not through Newtonian vectors, but through scalar quantities—kinetic and potential energy—operating within generalized coordinates.&#039;&#039;&#039; By positing that the true dynamical trajectory of any system is the one that leaves the action integral stationary, &#039;&#039;&#039;theorists established a universal mathematical language.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This analytical approach seamlessly extended beyond mechanical gears and pulleys into the continuum. It provided the structural mathematics required to unify electricity and magnetism into a single vacuum field theory, and later, to model gravity not as a pulling force, but as the dynamic geometric curvature of spacetime itself. Whether applied to subatomic particle behavior or cosmic expansion, these foundational principles continue to govern the leading edge of modern physics.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Physics Tools ==&lt;br /&gt;
Theoretical rigor must be paired with high-performance computational machinery. The **Principia Machina** framework organizes these tools across three analytical frontiers:&lt;br /&gt;
&lt;br /&gt;
* **The Inverse Action Problem:** Discovering analytical scalar Lagrangians &amp;lt;math&amp;gt;\mathcal{L}(\phi, \partial_\mu \phi)&amp;lt;/math&amp;gt; and continuous Noether symmetries directly from perturbation data using [[The_Principia_Machina/Tools/PySR|PySR]] and [[The_Principia_Machina/Tools/AIFeynman|AI Feynman]].&lt;br /&gt;
* **Variational &amp;amp; Mesh-Free Solvers:** Minimizing continuous action integrals across complex geometries via Physics-Informed Neural Networks ([[The_Principia_Machina/Tools/DeepXDE|DeepXDE]]) and symbolic finite-element/difference stencils ([[The_Principia_Machina/Tools/FEniCS|FEniCS]] &amp;amp; [[The_Principia_Machina/Tools/Devito|Devito]]).&lt;br /&gt;
* **Spacetime &amp;amp; Tensor Algebra:** Evaluating functional variational derivatives in [[The_Principia_Machina/Tools/Cadabra2|Cadabra2]], 3+1 ADM spacetime evolution in the [[The_Principia_Machina/Tools/EinsteinToolkit|Einstein Toolkit]], and open quantum dynamics in [[The_Principia_Machina/Tools/QuTiP|QuTiP]].&lt;br /&gt;
&lt;br /&gt;
([[Full survey and domain evaluation...|The_Principia_Machina/Tools]])&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-other-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-other&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Other areas of Ipsum Invarians&amp;lt;/h2&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-other-content&amp;quot; style=&amp;quot;padding: 10px;&amp;quot;&amp;gt;&lt;br /&gt;
* &#039;&#039;&#039;[[Special:AllPages|All pages]]&#039;&#039;&#039; &amp;amp;ndash; ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:RecentChanges|Recent changes]]&#039;&#039;&#039; &amp;amp;ndash; nisi ut aliquip ex ea commodo consequat duis aute irure.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:Categories|Categories]]&#039;&#039;&#039; &amp;amp;ndash; dolor in reprehenderit in voluptate velit esse cillum dolore.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:SpecialPages|Special pages]]&#039;&#039;&#039; &amp;amp;ndash; eu fugiat nulla pariatur excepteur sint occaecat cupidatat.&lt;br /&gt;
* &#039;&#039;&#039;[[Project:Sandbox|Sandbox]]&#039;&#039;&#039; &amp;amp;ndash; non proident, sunt in culpa qui officia deserunt mollit anim.&lt;br /&gt;
* &#039;&#039;&#039;[[Special:Upload|Upload]]&#039;&#039;&#039; &amp;amp;ndash; id est laborum sed ut perspiciatis unde omnis iste natus error.&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div id=&amp;quot;mp-lang-box&amp;quot; style=&amp;quot;border: 1px solid #a2a9b1; margin-bottom: 15px; background: #ffffff;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;h2 id=&amp;quot;mp-lang&amp;quot; style=&amp;quot;margin: 0; padding: 8px 10px; background-color: #eaecf0; border-bottom: 1px solid #a2a9b1; font-size: 1.2em; font-weight: bold;&amp;quot;&amp;gt;Ipsum Invarians languages&amp;lt;/h2&amp;gt;&lt;br /&gt;
  &amp;lt;div id=&amp;quot;mp-lang-content&amp;quot; style=&amp;quot;padding: 10px; text-align: center;&amp;quot;&amp;gt;&lt;br /&gt;
Totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;&#039;&#039;Language editions are not yet configured. Set them up with [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Interwiki interwiki links] or [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Translate Extension:Translate].&#039;&#039;&amp;lt;/small&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;__NOTOC____NOEDITSECTION__&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3182</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3182"/>
		<updated>2026-09-24T21:49:25Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: /* The gatekeeper: TPX */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
The Principia Machina (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;[[The_Principia_Machina/TPS/5.3_TPX|The Principia Machina Extension (TPX)]]&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3181</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3181"/>
		<updated>2026-09-24T21:47:51Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
The Principia Machina (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;[[5.3_TPX|The Principia Machina Extension (TPX)]]&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3180</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3180"/>
		<updated>2026-09-24T21:44:51Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
The Principia Machina (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3179</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3179"/>
		<updated>2026-09-24T21:33:06Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
[[The Principia Machina#top|the Principia Machina]] (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3178</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3178"/>
		<updated>2026-09-24T21:31:24Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
[[the Principia Machina]] xxx(TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3177</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3177"/>
		<updated>2026-09-24T21:27:30Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[the Principia Machina]]&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3176</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3176"/>
		<updated>2026-09-24T21:13:18Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
[[&#039;&#039;&#039;the Principia Machina|The Principia Machina&#039;&#039;&#039;]] (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3175</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3175"/>
		<updated>2026-09-24T21:12:20Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[The Principia Machina|the Principia Machina]]&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3174</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3174"/>
		<updated>2026-09-24T21:11:05Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[The Principia Machina]]&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3173</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3173"/>
		<updated>2026-09-24T20:07:52Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: /* The gatekeeper: TPX */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents honest?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3172</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3172"/>
		<updated>2026-09-24T19:58:05Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;The Principia Machina Extension (TPX)&#039;&#039;&#039;; it&#039;s an extension to the TPM Wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How does it keep agents hones?&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why is it not native to the wiki?&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical?&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where does it stand?&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3171</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3171"/>
		<updated>2026-09-24T19:53:04Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph and the rest is history.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;TPX&#039;&#039;&#039;, an extension installed on this wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it keeps agents honest.&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is closed-source.&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical.&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where it stands.&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3170</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3170"/>
		<updated>2026-09-24T19:51:42Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.  Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.  None of it led to a working aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly 27 mph.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk through meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;TPX&#039;&#039;&#039;, an extension installed on this wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it keeps agents honest.&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is closed-source.&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical.&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where it stands.&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3169</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3169"/>
		<updated>2026-09-24T17:46:13Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with diagrams and overviews. It is the way in for anyone new; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.&lt;br /&gt;
&lt;br /&gt;
Francis Wenham and John Browning built what is generally counted the first Wind tunnel in 1871. It&lt;br /&gt;
produced a real quantitative result. Horatio Phillips ran a steam-injector tunnel in 1884-85, patented&lt;br /&gt;
cambered sections, and showed that lift came largely from suction over the upper&lt;br /&gt;
surface. Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.&lt;br /&gt;
&lt;br /&gt;
None of it produced an aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly&lt;br /&gt;
27 mph.&lt;br /&gt;
&lt;br /&gt;
The duct was not the advance. The balances were. The Wrights designed their&lt;br /&gt;
measuring balances to read the ratio of lift to drag &#039;&#039;&#039;directly&#039;&#039;&#039;, so an error in&lt;br /&gt;
the absolute air-pressure constant cancelled out. They then tested&lt;br /&gt;
200 airfoil shapes, revised Smeaton&#039;s coefficient from 0.005 to about 0.0033,&lt;br /&gt;
and built the 1902 glider from their own data. It flew.&lt;br /&gt;
&lt;br /&gt;
The wind tunnel became an engineering instrument at the moment someone designed the&lt;br /&gt;
measurement so that a suspect constant could not corrupt the result.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
TPM is a test section for postulates. Someone declares a postulate set and its terms. TPM works out what follows, records each finding with the assumptions built into the postulates and derivations, and audits the whole body for contradictions and gaps.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
=== The orders the instrument runs under ===&lt;br /&gt;
&lt;br /&gt;
A wind tunnel is only as good as the method of the person working it. The Wright brothers&#039; advance in 1901 was not only the six-foot tunnel; it was the decision to build balances that read lift against drag directly, so that an error in Smeaton&#039;s coefficient would cancel rather than propagate. The tunnel made the measurements possible. The method made them worth having.&lt;br /&gt;
&lt;br /&gt;
The instrument described above is worked by an AI agent, so the method is a document the agent is given before it touches anything, and keeps in front of it while it works. It is not code and it is not training. It is text, and changing the text changes the behaviour on the next turn.&lt;br /&gt;
&lt;br /&gt;
That layer is specified in its own right, and deliberately without reference to any particular assistant. [[The Principia Machina/GTP|GTP]] sets out what such a document has to do: how a procedure is called up and why that can never be triggered by a file; what happens to material the agent did not get from a person; how it stops and asks rather than guesses; how its own pieces are kept in step as they are revised. It says what each job requires and nothing about how any one assistant does it.&lt;br /&gt;
&lt;br /&gt;
The set this site&#039;s own agent actually runs is published beneath it as the worked case. It carries no authority of its own: [[The Principia Machina/GTP/Claude/Conformance|its conformance statement]] lists every job GTP names, what fills it, and the two it leaves undone.&lt;br /&gt;
&lt;br /&gt;
Publishing any of this is a deliberate choice. An agent allowed to touch a research record ought to have its instructions as readable as its output. A reader who doubts a finding can read the finding. A reader who doubts the process can read the process.&lt;br /&gt;
&lt;br /&gt;
Where this stands is the same place as everything else here. GTP is proposed and has not been declared. Exactly one implementation of it exists, which means the claim that it is generic has never actually been tested against a second one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Start here:&#039;&#039;&#039; [[The Principia Machina/GTP/Walk/1 What the orders are, and who writes them|a walk through the instruction layer]], in six pages, written for a general reader. The whole section is on [[The Principia Machina/GTP/Contents|its contents page]].&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;TPX&#039;&#039;&#039;, an extension installed on this wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it keeps agents honest.&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is closed-source.&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical.&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where it stands.&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Where the analogy holds ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Throughput.&#039;&#039;&#039; The Wrights could test 200 shapes in the time one glider took to&lt;br /&gt;
build. Being wrong became cheap, so they could afford to be wrong often. AI supplies&lt;br /&gt;
derivation labour at a rate a person cannot match, and the point of that rate is the&lt;br /&gt;
same one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A sealed test section.&#039;&#039;&#039; A tunnel excludes weather, terrain and pilot skill so&lt;br /&gt;
that one variable can be read. A TPM container is isolated with its TFK and its full&lt;br /&gt;
register. Comparison against a more complete outside model is out of scope on&lt;br /&gt;
purpose.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Cancelling the suspect constant.&#039;&#039;&#039; The Wrights read a ratio so that a number they&lt;br /&gt;
distrusted dropped out. TPM ranks a finding by its distance to the TFK: how many&lt;br /&gt;
extra assumptions its derivation needs, and how many steps it took. Confidence,&lt;br /&gt;
authorship and expectation are not inputs. Where a finding is compared against an&lt;br /&gt;
outside value, the record reports the difference and never the agreement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Quarantining the published numbers.&#039;&#039;&#039; The Wrights stopped trusting Lilienthal&#039;s&lt;br /&gt;
tables, rebuilt from their own measurements, and compared afterwards. TPM does this&lt;br /&gt;
deliberately. Derivation runs with the benchmark out of view. The comparison lands&lt;br /&gt;
later as its own record, with its uncertainty stated and its components enumerated.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The instrument gets calibrated too.&#039;&#039;&#039; A tunnel with a bad balance produces&lt;br /&gt;
confident nonsense. TPM verifies a content digest of its own kernel before every&lt;br /&gt;
write, certifies each agent against planted probes before admitting it, and keeps&lt;br /&gt;
planting unannounced probes while it works. A certification pass is a filter, not a&lt;br /&gt;
guarantee, in the way a calibration certificate is.&lt;br /&gt;
&lt;br /&gt;
== Where the analogy breaks ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Internal consistency is not veracity.&#039;&#039;&#039; A perfectly repeatable tunnel result can&lt;br /&gt;
still be wrong about the sky, through scale effects, wall interference, or a&lt;br /&gt;
mismatched Reynolds number. TPM&#039;s version of that failure is a container that is&lt;br /&gt;
flawless and false. The only check for it sits outside the run: comparison against&lt;br /&gt;
measurement, after the fact, recorded as its own finding.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Completeness has a floor.&#039;&#039;&#039; The audit reports a declared degree of freedom that&lt;br /&gt;
nothing tied down. It cannot report one the TPK never named. A tunnel had the same&lt;br /&gt;
blind spot and said nothing about the phenomena it was not instrumented for.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There is no 1902 glider yet.&#039;&#039;&#039; The wind tunnel earned its status when data taken&lt;br /&gt;
from it flew. TPM&#039;s equivalent milestone is a container whose findings survive&lt;br /&gt;
comparison with measurements they were never shown. Until that happens, what this&lt;br /&gt;
page describes is design intent.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3168</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3168"/>
		<updated>2026-09-24T17:44:28Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; Try the [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with a picture on every page and nothing assumed. It is the way in for everyone; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.&lt;br /&gt;
&lt;br /&gt;
Francis Wenham and John Browning built what is generally counted the first Wind tunnel in 1871. It&lt;br /&gt;
produced a real quantitative result. Horatio Phillips ran a steam-injector tunnel in 1884-85, patented&lt;br /&gt;
cambered sections, and showed that lift came largely from suction over the upper&lt;br /&gt;
surface. Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.&lt;br /&gt;
&lt;br /&gt;
None of it produced an aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly&lt;br /&gt;
27 mph.&lt;br /&gt;
&lt;br /&gt;
The duct was not the advance. The balances were. The Wrights designed their&lt;br /&gt;
measuring balances to read the ratio of lift to drag &#039;&#039;&#039;directly&#039;&#039;&#039;, so an error in&lt;br /&gt;
the absolute air-pressure constant cancelled out. They then tested&lt;br /&gt;
200 airfoil shapes, revised Smeaton&#039;s coefficient from 0.005 to about 0.0033,&lt;br /&gt;
and built the 1902 glider from their own data. It flew.&lt;br /&gt;
&lt;br /&gt;
The wind tunnel became an engineering instrument at the moment someone designed the&lt;br /&gt;
measurement so that a suspect constant could not corrupt the result.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
TPM is a test section for postulates. Someone declares a postulate set and its terms. TPM works out what follows, records each finding with the assumptions built into the postulates and derivations, and audits the whole body for contradictions and gaps.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
=== The orders the instrument runs under ===&lt;br /&gt;
&lt;br /&gt;
A wind tunnel is only as good as the method of the person working it. The Wright brothers&#039; advance in 1901 was not only the six-foot tunnel; it was the decision to build balances that read lift against drag directly, so that an error in Smeaton&#039;s coefficient would cancel rather than propagate. The tunnel made the measurements possible. The method made them worth having.&lt;br /&gt;
&lt;br /&gt;
The instrument described above is worked by an AI agent, so the method is a document the agent is given before it touches anything, and keeps in front of it while it works. It is not code and it is not training. It is text, and changing the text changes the behaviour on the next turn.&lt;br /&gt;
&lt;br /&gt;
That layer is specified in its own right, and deliberately without reference to any particular assistant. [[The Principia Machina/GTP|GTP]] sets out what such a document has to do: how a procedure is called up and why that can never be triggered by a file; what happens to material the agent did not get from a person; how it stops and asks rather than guesses; how its own pieces are kept in step as they are revised. It says what each job requires and nothing about how any one assistant does it.&lt;br /&gt;
&lt;br /&gt;
The set this site&#039;s own agent actually runs is published beneath it as the worked case. It carries no authority of its own: [[The Principia Machina/GTP/Claude/Conformance|its conformance statement]] lists every job GTP names, what fills it, and the two it leaves undone.&lt;br /&gt;
&lt;br /&gt;
Publishing any of this is a deliberate choice. An agent allowed to touch a research record ought to have its instructions as readable as its output. A reader who doubts a finding can read the finding. A reader who doubts the process can read the process.&lt;br /&gt;
&lt;br /&gt;
Where this stands is the same place as everything else here. GTP is proposed and has not been declared. Exactly one implementation of it exists, which means the claim that it is generic has never actually been tested against a second one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Start here:&#039;&#039;&#039; [[The Principia Machina/GTP/Walk/1 What the orders are, and who writes them|a walk through the instruction layer]], in six pages, written for a general reader. The whole section is on [[The Principia Machina/GTP/Contents|its contents page]].&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;TPX&#039;&#039;&#039;, an extension installed on this wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it keeps agents honest.&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is closed-source.&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical.&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where it stands.&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Where the analogy holds ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Throughput.&#039;&#039;&#039; The Wrights could test 200 shapes in the time one glider took to&lt;br /&gt;
build. Being wrong became cheap, so they could afford to be wrong often. AI supplies&lt;br /&gt;
derivation labour at a rate a person cannot match, and the point of that rate is the&lt;br /&gt;
same one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A sealed test section.&#039;&#039;&#039; A tunnel excludes weather, terrain and pilot skill so&lt;br /&gt;
that one variable can be read. A TPM container is isolated with its TFK and its full&lt;br /&gt;
register. Comparison against a more complete outside model is out of scope on&lt;br /&gt;
purpose.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Cancelling the suspect constant.&#039;&#039;&#039; The Wrights read a ratio so that a number they&lt;br /&gt;
distrusted dropped out. TPM ranks a finding by its distance to the TFK: how many&lt;br /&gt;
extra assumptions its derivation needs, and how many steps it took. Confidence,&lt;br /&gt;
authorship and expectation are not inputs. Where a finding is compared against an&lt;br /&gt;
outside value, the record reports the difference and never the agreement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Quarantining the published numbers.&#039;&#039;&#039; The Wrights stopped trusting Lilienthal&#039;s&lt;br /&gt;
tables, rebuilt from their own measurements, and compared afterwards. TPM does this&lt;br /&gt;
deliberately. Derivation runs with the benchmark out of view. The comparison lands&lt;br /&gt;
later as its own record, with its uncertainty stated and its components enumerated.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The instrument gets calibrated too.&#039;&#039;&#039; A tunnel with a bad balance produces&lt;br /&gt;
confident nonsense. TPM verifies a content digest of its own kernel before every&lt;br /&gt;
write, certifies each agent against planted probes before admitting it, and keeps&lt;br /&gt;
planting unannounced probes while it works. A certification pass is a filter, not a&lt;br /&gt;
guarantee, in the way a calibration certificate is.&lt;br /&gt;
&lt;br /&gt;
== Where the analogy breaks ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Internal consistency is not veracity.&#039;&#039;&#039; A perfectly repeatable tunnel result can&lt;br /&gt;
still be wrong about the sky, through scale effects, wall interference, or a&lt;br /&gt;
mismatched Reynolds number. TPM&#039;s version of that failure is a container that is&lt;br /&gt;
flawless and false. The only check for it sits outside the run: comparison against&lt;br /&gt;
measurement, after the fact, recorded as its own finding.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Completeness has a floor.&#039;&#039;&#039; The audit reports a declared degree of freedom that&lt;br /&gt;
nothing tied down. It cannot report one the TPK never named. A tunnel had the same&lt;br /&gt;
blind spot and said nothing about the phenomena it was not instrumented for.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There is no 1902 glider yet.&#039;&#039;&#039; The wind tunnel earned its status when data taken&lt;br /&gt;
from it flew. TPM&#039;s equivalent milestone is a container whose findings survive&lt;br /&gt;
comparison with measurements they were never shown. Until that happens, what this&lt;br /&gt;
page describes is design intent.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3167</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3167"/>
		<updated>2026-09-24T17:43:32Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to manage certifications and reliability. AI Agents caught making math/logic mistakes or hallucinations, are suspended or decertified.  The system requires AI&#039;s to cooperate by checking each others work and manages an additional reliability layer to manage &amp;quot;interpretive collisions&amp;quot; when work cannot be reduced to simple math/logic violations.  Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with a picture on every page and nothing assumed. It is the way in for everyone; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Want to build one?&#039;&#039;&#039; [[The Principia Machina/Tutorial|The tutorial]] creates a container step by step on a worked example, from an empty draft to its declaration, showing the checker&#039;s real output at every step. Every field it fills is explained in [[The Principia Machina/Inputs|the inputs reference]].&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.&lt;br /&gt;
&lt;br /&gt;
Francis Wenham and John Browning built what is generally counted the first Wind tunnel in 1871. It&lt;br /&gt;
produced a real quantitative result. Horatio Phillips ran a steam-injector tunnel in 1884-85, patented&lt;br /&gt;
cambered sections, and showed that lift came largely from suction over the upper&lt;br /&gt;
surface. Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.&lt;br /&gt;
&lt;br /&gt;
None of it produced an aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly&lt;br /&gt;
27 mph.&lt;br /&gt;
&lt;br /&gt;
The duct was not the advance. The balances were. The Wrights designed their&lt;br /&gt;
measuring balances to read the ratio of lift to drag &#039;&#039;&#039;directly&#039;&#039;&#039;, so an error in&lt;br /&gt;
the absolute air-pressure constant cancelled out. They then tested&lt;br /&gt;
200 airfoil shapes, revised Smeaton&#039;s coefficient from 0.005 to about 0.0033,&lt;br /&gt;
and built the 1902 glider from their own data. It flew.&lt;br /&gt;
&lt;br /&gt;
The wind tunnel became an engineering instrument at the moment someone designed the&lt;br /&gt;
measurement so that a suspect constant could not corrupt the result.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
TPM is a test section for postulates. Someone declares a postulate set and its terms. TPM works out what follows, records each finding with the assumptions built into the postulates and derivations, and audits the whole body for contradictions and gaps.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
=== The orders the instrument runs under ===&lt;br /&gt;
&lt;br /&gt;
A wind tunnel is only as good as the method of the person working it. The Wright brothers&#039; advance in 1901 was not only the six-foot tunnel; it was the decision to build balances that read lift against drag directly, so that an error in Smeaton&#039;s coefficient would cancel rather than propagate. The tunnel made the measurements possible. The method made them worth having.&lt;br /&gt;
&lt;br /&gt;
The instrument described above is worked by an AI agent, so the method is a document the agent is given before it touches anything, and keeps in front of it while it works. It is not code and it is not training. It is text, and changing the text changes the behaviour on the next turn.&lt;br /&gt;
&lt;br /&gt;
That layer is specified in its own right, and deliberately without reference to any particular assistant. [[The Principia Machina/GTP|GTP]] sets out what such a document has to do: how a procedure is called up and why that can never be triggered by a file; what happens to material the agent did not get from a person; how it stops and asks rather than guesses; how its own pieces are kept in step as they are revised. It says what each job requires and nothing about how any one assistant does it.&lt;br /&gt;
&lt;br /&gt;
The set this site&#039;s own agent actually runs is published beneath it as the worked case. It carries no authority of its own: [[The Principia Machina/GTP/Claude/Conformance|its conformance statement]] lists every job GTP names, what fills it, and the two it leaves undone.&lt;br /&gt;
&lt;br /&gt;
Publishing any of this is a deliberate choice. An agent allowed to touch a research record ought to have its instructions as readable as its output. A reader who doubts a finding can read the finding. A reader who doubts the process can read the process.&lt;br /&gt;
&lt;br /&gt;
Where this stands is the same place as everything else here. GTP is proposed and has not been declared. Exactly one implementation of it exists, which means the claim that it is generic has never actually been tested against a second one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Start here:&#039;&#039;&#039; [[The Principia Machina/GTP/Walk/1 What the orders are, and who writes them|a walk through the instruction layer]], in six pages, written for a general reader. The whole section is on [[The Principia Machina/GTP/Contents|its contents page]].&lt;br /&gt;
&lt;br /&gt;
== The gatekeeper: TPX ==&lt;br /&gt;
&lt;br /&gt;
The agents do the work, but they are not trusted to judge it. That job belongs to &#039;&#039;&#039;TPX&#039;&#039;&#039;, an extension installed on this wiki. Everything an agent produces reaches the record only through TPX, and TPX checks it on the way in.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What only TPX may do.&#039;&#039;&#039;&lt;br /&gt;
* Compute every fingerprint (digest). A fingerprint copied by hand is not a fingerprint.&lt;br /&gt;
* Issue each container its identity and allocate its record numbers.&lt;br /&gt;
* Run the checks as each part of a kernel is entered, and refuse a failing part before it is saved.&lt;br /&gt;
* Hold the lock that decides which agent may land work, and refuse a late or out-of-turn landing.&lt;br /&gt;
* Write the register. An agent reads records and asks TPX to add or change one; it never writes the register itself.&lt;br /&gt;
* Build the index, and the badge that tells a reader whether a copy is current.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it keeps agents honest.&#039;&#039;&#039;&lt;br /&gt;
* It recomputes every value an agent presents with its own calculator. Its answer is the one of record, and a value that differs is refused.&lt;br /&gt;
* It challenges each agent to prove it actually ran the published calculator rather than imagined the result.&lt;br /&gt;
* It plants unannounced test probes, called canaries, in about one work block in five. Each canary is a deliberate error the agent must recognize, refuse and report. The agent cannot tell a canary from a real problem, and does not need to: the right response is the same.&lt;br /&gt;
* When an agent fails a canary, TPX stops that agent&#039;s landings at once and puts its recent work on hold. Every record back to the agent&#039;s second-last passed canary, about eleven work blocks on average, is marked HELD on the record itself, so no reader can mistake it for standing work. A held record cannot be cited or counted until an independent agent, running a different model version, reproduces it. Older work from the same model version is re-checked as well. Removing the agent is a human&#039;s decision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is closed-source.&#039;&#039;&#039; TPX&#039;s executable code is kept off the wiki, so an agent cannot read it to learn how to spot a canary. Its design is published as pseudocode, and the fingerprint of every build put into service is added to the build chain, so anyone can confirm that the running code is the declared code without seeing it. The calculator the agents run (TPC-PY) stays published, because they must run it; it contains no canary logic.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it is critical.&#039;&#039;&#039; Without TPX the rules are text that an agent may or may not follow. With it, they are enforced before anything reaches the record. TPM&#039;s reliability rests on TPX&#039;s own recomputation, not on any agent&#039;s claims.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Where it stands.&#039;&#039;&#039; TPX is specified and not yet built. Until it is, a human performs its checks by inspection. The hold on work after a failed canary and the closed-source build were decided on 23 September 2026 and are being written into the specification.&lt;br /&gt;
&lt;br /&gt;
Further reading: [[The Principia Machina/TPS/5.3 TPX|TPX in the specification]]; [[The Principia Machina/TPS/5.14 AI certification|AI certification]]; [[The Principia Machina/TPS/5.17 The canary programme|the canary programme]]; [[The Principia Machina/Walk/The calculator and its copy|the calculator and its copy]]; [[The Principia Machina/Diagrams/C4 Landing pipeline|the landing pipeline diagram]].&lt;br /&gt;
&lt;br /&gt;
== Where the analogy holds ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Throughput.&#039;&#039;&#039; The Wrights could test 200 shapes in the time one glider took to&lt;br /&gt;
build. Being wrong became cheap, so they could afford to be wrong often. AI supplies&lt;br /&gt;
derivation labour at a rate a person cannot match, and the point of that rate is the&lt;br /&gt;
same one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A sealed test section.&#039;&#039;&#039; A tunnel excludes weather, terrain and pilot skill so&lt;br /&gt;
that one variable can be read. A TPM container is isolated with its TFK and its full&lt;br /&gt;
register. Comparison against a more complete outside model is out of scope on&lt;br /&gt;
purpose.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Cancelling the suspect constant.&#039;&#039;&#039; The Wrights read a ratio so that a number they&lt;br /&gt;
distrusted dropped out. TPM ranks a finding by its distance to the TFK: how many&lt;br /&gt;
extra assumptions its derivation needs, and how many steps it took. Confidence,&lt;br /&gt;
authorship and expectation are not inputs. Where a finding is compared against an&lt;br /&gt;
outside value, the record reports the difference and never the agreement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Quarantining the published numbers.&#039;&#039;&#039; The Wrights stopped trusting Lilienthal&#039;s&lt;br /&gt;
tables, rebuilt from their own measurements, and compared afterwards. TPM does this&lt;br /&gt;
deliberately. Derivation runs with the benchmark out of view. The comparison lands&lt;br /&gt;
later as its own record, with its uncertainty stated and its components enumerated.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The instrument gets calibrated too.&#039;&#039;&#039; A tunnel with a bad balance produces&lt;br /&gt;
confident nonsense. TPM verifies a content digest of its own kernel before every&lt;br /&gt;
write, certifies each agent against planted probes before admitting it, and keeps&lt;br /&gt;
planting unannounced probes while it works. A certification pass is a filter, not a&lt;br /&gt;
guarantee, in the way a calibration certificate is.&lt;br /&gt;
&lt;br /&gt;
== Where the analogy breaks ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Internal consistency is not veracity.&#039;&#039;&#039; A perfectly repeatable tunnel result can&lt;br /&gt;
still be wrong about the sky, through scale effects, wall interference, or a&lt;br /&gt;
mismatched Reynolds number. TPM&#039;s version of that failure is a container that is&lt;br /&gt;
flawless and false. The only check for it sits outside the run: comparison against&lt;br /&gt;
measurement, after the fact, recorded as its own finding.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Completeness has a floor.&#039;&#039;&#039; The audit reports a declared degree of freedom that&lt;br /&gt;
nothing tied down. It cannot report one the TPK never named. A tunnel had the same&lt;br /&gt;
blind spot and said nothing about the phenomena it was not instrumented for.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There is no 1902 glider yet.&#039;&#039;&#039; The wind tunnel earned its status when data taken&lt;br /&gt;
from it flew. TPM&#039;s equivalent milestone is a container whose findings survive&lt;br /&gt;
comparison with measurements they were never shown. Until that happens, what this&lt;br /&gt;
page describes is design intent.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 24 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and was declared final on 22 September 2026. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Version 0.1.0 was declared final on 22 September 2026. Its fingerprint becomes the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.14.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.10.0 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]; the copy published there is being brought up to date. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3165</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3165"/>
		<updated>2026-09-23T16:02:48Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications &lt;br /&gt;
using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their work-blocks (canaries) to make certain their work maintains its reliability. Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with a picture on every page and nothing assumed. It is the way in for everyone; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.&lt;br /&gt;
&lt;br /&gt;
Francis Wenham and John Browning built what is generally counted the first Wind tunnel in 1871. It&lt;br /&gt;
produced a real quantitative result. Horatio Phillips ran a steam-injector tunnel in 1884-85, patented&lt;br /&gt;
cambered sections, and showed that lift came largely from suction over the upper&lt;br /&gt;
surface. Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.&lt;br /&gt;
&lt;br /&gt;
None of it produced an aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly&lt;br /&gt;
27 mph.&lt;br /&gt;
&lt;br /&gt;
The duct was not the advance. The balances were. The Wrights designed their&lt;br /&gt;
measuring balances to read the ratio of lift to drag &#039;&#039;&#039;directly&#039;&#039;&#039;, so an error in&lt;br /&gt;
the absolute air-pressure constant cancelled out. They then tested&lt;br /&gt;
200 airfoil shapes, revised Smeaton&#039;s coefficient from 0.005 to about 0.0033,&lt;br /&gt;
and built the 1902 glider from their own data. It flew.&lt;br /&gt;
&lt;br /&gt;
The wind tunnel became an engineering instrument at the moment someone designed the&lt;br /&gt;
measurement so that a suspect constant could not corrupt the result.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
TPM is a test section for postulates. Someone declares a postulate set and its terms. TPM works out what follows, records each finding with the assumptions built into the postulates and derivations, and audits the whole body for contradictions and gaps.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
=== The orders the instrument runs under ===&lt;br /&gt;
&lt;br /&gt;
A wind tunnel is only as good as the method of the person working it. The Wright brothers&#039; advance in 1901 was not only the six-foot tunnel; it was the decision to build balances that read lift against drag directly, so that an error in Smeaton&#039;s coefficient would cancel rather than propagate. The tunnel made the measurements possible. The method made them worth having.&lt;br /&gt;
&lt;br /&gt;
The instrument described above is worked by an AI agent, so the method is a document the agent is given before it touches anything, and keeps in front of it while it works. It is not code and it is not training. It is text, and changing the text changes the behaviour on the next turn.&lt;br /&gt;
&lt;br /&gt;
That layer is specified in its own right, and deliberately without reference to any particular assistant. [[The Principia Machina/GTP|GTP]] sets out what such a document has to do: how a procedure is called up and why that can never be triggered by a file; what happens to material the agent did not get from a person; how it stops and asks rather than guesses; how its own pieces are kept in step as they are revised. It says what each job requires and nothing about how any one assistant does it.&lt;br /&gt;
&lt;br /&gt;
The set this site&#039;s own agent actually runs is published beneath it as the worked case. It carries no authority of its own: [[The Principia Machina/GTP/Claude/Conformance|its conformance statement]] lists every job GTP names, what fills it, and the two it leaves undone.&lt;br /&gt;
&lt;br /&gt;
Publishing any of this is a deliberate choice. An agent allowed to touch a research record ought to have its instructions as readable as its output. A reader who doubts a finding can read the finding. A reader who doubts the process can read the process.&lt;br /&gt;
&lt;br /&gt;
Where this stands is the same place as everything else here. GTP is proposed and has not been declared. Exactly one implementation of it exists, which means the claim that it is generic has never actually been tested against a second one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Start here:&#039;&#039;&#039; [[The Principia Machina/GTP/Walk/1 What the orders are, and who writes them|a walk through the instruction layer]], in six pages, written for a general reader. The whole section is on [[The Principia Machina/GTP/Contents|its contents page]].&lt;br /&gt;
&lt;br /&gt;
== Where the analogy holds ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Throughput.&#039;&#039;&#039; The Wrights could test 200 shapes in the time one glider took to&lt;br /&gt;
build. Being wrong became cheap, so they could afford to be wrong often. AI supplies&lt;br /&gt;
derivation labour at a rate a person cannot match, and the point of that rate is the&lt;br /&gt;
same one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A sealed test section.&#039;&#039;&#039; A tunnel excludes weather, terrain and pilot skill so&lt;br /&gt;
that one variable can be read. A TPM container is isolated with its TFK and its full&lt;br /&gt;
register. Comparison against a more complete outside model is out of scope on&lt;br /&gt;
purpose.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Cancelling the suspect constant.&#039;&#039;&#039; The Wrights read a ratio so that a number they&lt;br /&gt;
distrusted dropped out. TPM ranks a finding by its distance to the TFK: how many&lt;br /&gt;
extra assumptions its derivation needs, and how many steps it took. Confidence,&lt;br /&gt;
authorship and expectation are not inputs. Where a finding is compared against an&lt;br /&gt;
outside value, the record reports the difference and never the agreement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Quarantining the published numbers.&#039;&#039;&#039; The Wrights stopped trusting Lilienthal&#039;s&lt;br /&gt;
tables, rebuilt from their own measurements, and compared afterwards. TPM does this&lt;br /&gt;
deliberately. Derivation runs with the benchmark out of view. The comparison lands&lt;br /&gt;
later as its own record, with its uncertainty stated and its components enumerated.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The instrument gets calibrated too.&#039;&#039;&#039; A tunnel with a bad balance produces&lt;br /&gt;
confident nonsense. TPM verifies a content digest of its own kernel before every&lt;br /&gt;
write, certifies each agent against planted probes before admitting it, and keeps&lt;br /&gt;
planting unannounced probes while it works. A certification pass is a filter, not a&lt;br /&gt;
guarantee, in the way a calibration certificate is.&lt;br /&gt;
&lt;br /&gt;
== Where the analogy breaks ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Internal consistency is not veracity.&#039;&#039;&#039; A perfectly repeatable tunnel result can&lt;br /&gt;
still be wrong about the sky, through scale effects, wall interference, or a&lt;br /&gt;
mismatched Reynolds number. TPM&#039;s version of that failure is a container that is&lt;br /&gt;
flawless and false. The only check for it sits outside the run: comparison against&lt;br /&gt;
measurement, after the fact, recorded as its own finding.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Completeness has a floor.&#039;&#039;&#039; The audit reports a declared degree of freedom that&lt;br /&gt;
nothing tied down. It cannot report one the TPK never named. A tunnel had the same&lt;br /&gt;
blind spot and said nothing about the phenomena it was not instrumented for.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There is no 1902 glider yet.&#039;&#039;&#039; The wind tunnel earned its status when data taken&lt;br /&gt;
from it flew. TPM&#039;s equivalent milestone is a container whose findings survive&lt;br /&gt;
comparison with measurements they were never shown. Until that happens, what this&lt;br /&gt;
page describes is design intent.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 22 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and awaits its declaration. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Its version is proposed; it becomes the published rule book when its fingerprint is landed as the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.12.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.8.1 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3164</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3164"/>
		<updated>2026-09-23T15:55:26Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing a set of physics postulates and evaluating the implications &lt;br /&gt;
using a strict AI protocol designed specifically to minimize hallucinations and completion theater. Certified AI agents do the derivations, but a closed-source gate keeper (TPX) continuously injects errors into their workload (canaries) to make certain their work maintains its reliability. Additionally, the wiki holds every step on the record so the work can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with a picture on every page and nothing assumed. It is the way in for everyone; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.&lt;br /&gt;
&lt;br /&gt;
Francis Wenham and John Browning built what is generally counted the first Wind tunnel in 1871. It&lt;br /&gt;
produced a real quantitative result. Horatio Phillips ran a steam-injector tunnel in 1884-85, patented&lt;br /&gt;
cambered sections, and showed that lift came largely from suction over the upper&lt;br /&gt;
surface. Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.&lt;br /&gt;
&lt;br /&gt;
None of it produced an aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly&lt;br /&gt;
27 mph.&lt;br /&gt;
&lt;br /&gt;
The duct was not the advance. The balances were. The Wrights designed their&lt;br /&gt;
measuring balances to read the ratio of lift to drag &#039;&#039;&#039;directly&#039;&#039;&#039;, so an error in&lt;br /&gt;
the absolute air-pressure constant cancelled out. They then tested&lt;br /&gt;
200 airfoil shapes, revised Smeaton&#039;s coefficient from 0.005 to about 0.0033,&lt;br /&gt;
and built the 1902 glider from their own data. It flew.&lt;br /&gt;
&lt;br /&gt;
The wind tunnel became an engineering instrument at the moment someone designed the&lt;br /&gt;
measurement so that a suspect constant could not corrupt the result.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
TPM is a test section for postulates. Someone declares a postulate set and its terms. TPM works out what follows, records each finding with the assumptions built into the postulates and derivations, and audits the whole body for contradictions and gaps.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
=== The orders the instrument runs under ===&lt;br /&gt;
&lt;br /&gt;
A wind tunnel is only as good as the method of the person working it. The Wright brothers&#039; advance in 1901 was not only the six-foot tunnel; it was the decision to build balances that read lift against drag directly, so that an error in Smeaton&#039;s coefficient would cancel rather than propagate. The tunnel made the measurements possible. The method made them worth having.&lt;br /&gt;
&lt;br /&gt;
The instrument described above is worked by an AI agent, so the method is a document the agent is given before it touches anything, and keeps in front of it while it works. It is not code and it is not training. It is text, and changing the text changes the behaviour on the next turn.&lt;br /&gt;
&lt;br /&gt;
That layer is specified in its own right, and deliberately without reference to any particular assistant. [[The Principia Machina/GTP|GTP]] sets out what such a document has to do: how a procedure is called up and why that can never be triggered by a file; what happens to material the agent did not get from a person; how it stops and asks rather than guesses; how its own pieces are kept in step as they are revised. It says what each job requires and nothing about how any one assistant does it.&lt;br /&gt;
&lt;br /&gt;
The set this site&#039;s own agent actually runs is published beneath it as the worked case. It carries no authority of its own: [[The Principia Machina/GTP/Claude/Conformance|its conformance statement]] lists every job GTP names, what fills it, and the two it leaves undone.&lt;br /&gt;
&lt;br /&gt;
Publishing any of this is a deliberate choice. An agent allowed to touch a research record ought to have its instructions as readable as its output. A reader who doubts a finding can read the finding. A reader who doubts the process can read the process.&lt;br /&gt;
&lt;br /&gt;
Where this stands is the same place as everything else here. GTP is proposed and has not been declared. Exactly one implementation of it exists, which means the claim that it is generic has never actually been tested against a second one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Start here:&#039;&#039;&#039; [[The Principia Machina/GTP/Walk/1 What the orders are, and who writes them|a walk through the instruction layer]], in six pages, written for a general reader. The whole section is on [[The Principia Machina/GTP/Contents|its contents page]].&lt;br /&gt;
&lt;br /&gt;
== Where the analogy holds ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Throughput.&#039;&#039;&#039; The Wrights could test 200 shapes in the time one glider took to&lt;br /&gt;
build. Being wrong became cheap, so they could afford to be wrong often. AI supplies&lt;br /&gt;
derivation labour at a rate a person cannot match, and the point of that rate is the&lt;br /&gt;
same one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A sealed test section.&#039;&#039;&#039; A tunnel excludes weather, terrain and pilot skill so&lt;br /&gt;
that one variable can be read. A TPM container is isolated with its TFK and its full&lt;br /&gt;
register. Comparison against a more complete outside model is out of scope on&lt;br /&gt;
purpose.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Cancelling the suspect constant.&#039;&#039;&#039; The Wrights read a ratio so that a number they&lt;br /&gt;
distrusted dropped out. TPM ranks a finding by its distance to the TFK: how many&lt;br /&gt;
extra assumptions its derivation needs, and how many steps it took. Confidence,&lt;br /&gt;
authorship and expectation are not inputs. Where a finding is compared against an&lt;br /&gt;
outside value, the record reports the difference and never the agreement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Quarantining the published numbers.&#039;&#039;&#039; The Wrights stopped trusting Lilienthal&#039;s&lt;br /&gt;
tables, rebuilt from their own measurements, and compared afterwards. TPM does this&lt;br /&gt;
deliberately. Derivation runs with the benchmark out of view. The comparison lands&lt;br /&gt;
later as its own record, with its uncertainty stated and its components enumerated.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The instrument gets calibrated too.&#039;&#039;&#039; A tunnel with a bad balance produces&lt;br /&gt;
confident nonsense. TPM verifies a content digest of its own kernel before every&lt;br /&gt;
write, certifies each agent against planted probes before admitting it, and keeps&lt;br /&gt;
planting unannounced probes while it works. A certification pass is a filter, not a&lt;br /&gt;
guarantee, in the way a calibration certificate is.&lt;br /&gt;
&lt;br /&gt;
== Where the analogy breaks ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Internal consistency is not veracity.&#039;&#039;&#039; A perfectly repeatable tunnel result can&lt;br /&gt;
still be wrong about the sky, through scale effects, wall interference, or a&lt;br /&gt;
mismatched Reynolds number. TPM&#039;s version of that failure is a container that is&lt;br /&gt;
flawless and false. The only check for it sits outside the run: comparison against&lt;br /&gt;
measurement, after the fact, recorded as its own finding.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Completeness has a floor.&#039;&#039;&#039; The audit reports a declared degree of freedom that&lt;br /&gt;
nothing tied down. It cannot report one the TPK never named. A tunnel had the same&lt;br /&gt;
blind spot and said nothing about the phenomena it was not instrumented for.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There is no 1902 glider yet.&#039;&#039;&#039; The wind tunnel earned its status when data taken&lt;br /&gt;
from it flew. TPM&#039;s equivalent milestone is a container whose findings survive&lt;br /&gt;
comparison with measurements they were never shown. Until that happens, what this&lt;br /&gt;
page describes is design intent.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 22 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and awaits its declaration. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Its version is proposed; it becomes the published rule book when its fingerprint is landed as the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.12.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.8.1 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
	<entry>
		<id>https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3163</id>
		<title>The Principia Machina</title>
		<link rel="alternate" type="text/html" href="https://invarians.org/index.php?title=The_Principia_Machina&amp;diff=3163"/>
		<updated>2026-09-23T15:32:56Z</updated>

		<summary type="html">&lt;p&gt;Alt BFP: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TPM map}}&lt;br /&gt;
&#039;&#039;&#039;The Principia Machina&#039;&#039;&#039; (TPM) is an instrument for testing the implications of a set of physics&lt;br /&gt;
postulates using AI. AI agents do the derivations and the wiki holds every&lt;br /&gt;
step on the record so they can be independently verified.&lt;br /&gt;
&lt;br /&gt;
== Start here ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New to The Principia Machina?&#039;&#039;&#039; [[The Principia Machina/Hub/General reader|walk through]]. It takes the subject from the beginning, one page at a time, with a picture on every page and nothing assumed. It is the way in for everyone; the pages below on this one are its first stop.&lt;br /&gt;
* &#039;&#039;&#039;Running the wiki or a container?&#039;&#039;&#039; [[The Principia Machina/Hub/Operator|The operator&#039;s guide]] is comprehensive and written for people who will be held to it. It assumes the walk; if you have not read the walk, it will read as rules without reasons.&lt;br /&gt;
* The panel at the right stays with you on every page: the two keys that explain the diagram shapes, and the definition of terms.&lt;br /&gt;
&lt;br /&gt;
== The instrument mattered as much as the aircraft ==&lt;br /&gt;
&lt;br /&gt;
Wind tunnels existed for thirty years before one changed aviation.&lt;br /&gt;
&lt;br /&gt;
Francis Wenham and John Browning built what is generally counted the first Wind tunnel in 1871. It&lt;br /&gt;
produced a real quantitative result. Horatio Phillips ran a steam-injector tunnel in 1884-85, patented&lt;br /&gt;
cambered sections, and showed that lift came largely from suction over the upper&lt;br /&gt;
surface. Konstantin Tsiolkovsky built an open-circuit tunnel in Moscow in the 1890s.&lt;br /&gt;
Nikolai Zhukovsky set one up at Moscow University in 1902. Hiram Maxim and Ludwig&lt;br /&gt;
Mach ran variants of their own.&lt;br /&gt;
&lt;br /&gt;
None of it produced an aircraft.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| [[File:Wright_Brothers_Wind_Tunnel.png|300px|thumb|none|&#039;&#039;The Wright Brothers and their Wind Tunnel&#039;&#039;]]&lt;br /&gt;
|&lt;br /&gt;
| [[File:Wright_flyer.png|300px|thumb|none|&#039;&#039;The Wright Flyer&#039;&#039;]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decisive use came in 1901. The Wright brothers&#039; 1900 and 1901 gliders&lt;br /&gt;
underperformed calculations based on the best existing wind tunnel experiments. They concluded that the published numbers were wrong: both Lilienthal&#039;s coefficients and Smeaton&#039;s coefficient of air pressure, were struck down. The brothers built a 6-foot tunnel with a 16-inch square test section, driven at roughly&lt;br /&gt;
27 mph.&lt;br /&gt;
&lt;br /&gt;
The duct was not the advance. The balances were. The Wrights designed their&lt;br /&gt;
measuring balances to read the ratio of lift to drag &#039;&#039;&#039;directly&#039;&#039;&#039;, so an error in&lt;br /&gt;
the absolute air-pressure constant cancelled out. They then tested&lt;br /&gt;
200 airfoil shapes, revised Smeaton&#039;s coefficient from 0.005 to about 0.0033,&lt;br /&gt;
and built the 1902 glider from their own data. It flew.&lt;br /&gt;
&lt;br /&gt;
The wind tunnel became an engineering instrument at the moment someone designed the&lt;br /&gt;
measurement so that a suspect constant could not corrupt the result.&lt;br /&gt;
&lt;br /&gt;
== The Principia Machina (TPM) as a hopeful tool ==&lt;br /&gt;
&lt;br /&gt;
TPM is a test section for postulates. Someone declares a postulate set and its terms. TPM works out what follows, records each finding with the assumptions built into the postulates and derivations, and audits the whole body for contradictions and gaps.&lt;br /&gt;
&lt;br /&gt;
The pieces, in the order the walk meets them:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.2 The Prime Kernel|The Prime Kernel]]&#039;&#039;&#039; (TPK) — the postulates, assumptions and hard boundaries under test. Nothing produced inside a run may contradict it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.3 The Translation Manifold|The Translation Manifold]]&#039;&#039;&#039; (TrM) — the mapping from the TPK&#039;s own terms into a physical setting. Each entry names a degree of freedom, the regime it holds in, and what would falsify it.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/2.4 The Measure Set|The Measure Set]]&#039;&#039;&#039; (TMS) — the yardsticks. How two findings are compared, when they count as contradicting, and what counts as an extraordinary case.&lt;br /&gt;
* Together these three form the &#039;&#039;&#039;[[The Principia Machina/TPS/2.1 The Full Kernel and immutability|Full Kernel]]&#039;&#039;&#039; (TFK). The TFK is immutable. Changing it does not edit the investigation; it starts a new one, with a new identity and a record of what it came from.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/3.1 Records, prefixes and volumes|The Research Register]]&#039;&#039;&#039; (RR) — every finding, in order, with its assumptions, its derivation, its regime and its standing.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/4.1 The audit and its authority|Congruence Protocol]]&#039;&#039;&#039; — the audit. It checks the register against the TFK, applies the strike rule to contradictions, and reports which declared degrees of freedom were never tied down.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/TPS/5.1 The three parts and the placement rule|Public Recorder]]&#039;&#039;&#039; — the wiki and the machinery that keeps the record: the platform, the TPX extension that enforces every check, and the PRB client beside each agent.&lt;br /&gt;
* &#039;&#039;&#039;[[The Principia Machina/GTP|GTP]]&#039;&#039;&#039; — the orders the agent works to: the instruction layer it is given before it touches anything and keeps in front of it while it works, specified on its own so any assistant could implement it. The section below takes it up.&lt;br /&gt;
&lt;br /&gt;
A single TFK together with the register built on it is a &#039;&#039;&#039;UUID Workspace Container&#039;&#039;&#039; (UWC), a container for short. Containers&lt;br /&gt;
are sealed by design. The [[The Principia Machina/Diagrams/C1 Kernel and register|kernel and register data structure]] and the [[The Principia Machina/Diagrams/C3 Lifecycle pipeline|container lifecycle]] show how the pieces fit and move; the walk explains both.&lt;br /&gt;
&lt;br /&gt;
=== The orders the instrument runs under ===&lt;br /&gt;
&lt;br /&gt;
A wind tunnel is only as good as the method of the person working it. The Wright brothers&#039; advance in 1901 was not only the six-foot tunnel; it was the decision to build balances that read lift against drag directly, so that an error in Smeaton&#039;s coefficient would cancel rather than propagate. The tunnel made the measurements possible. The method made them worth having.&lt;br /&gt;
&lt;br /&gt;
The instrument described above is worked by an AI agent, so the method is a document the agent is given before it touches anything, and keeps in front of it while it works. It is not code and it is not training. It is text, and changing the text changes the behaviour on the next turn.&lt;br /&gt;
&lt;br /&gt;
That layer is specified in its own right, and deliberately without reference to any particular assistant. [[The Principia Machina/GTP|GTP]] sets out what such a document has to do: how a procedure is called up and why that can never be triggered by a file; what happens to material the agent did not get from a person; how it stops and asks rather than guesses; how its own pieces are kept in step as they are revised. It says what each job requires and nothing about how any one assistant does it.&lt;br /&gt;
&lt;br /&gt;
The set this site&#039;s own agent actually runs is published beneath it as the worked case. It carries no authority of its own: [[The Principia Machina/GTP/Claude/Conformance|its conformance statement]] lists every job GTP names, what fills it, and the two it leaves undone.&lt;br /&gt;
&lt;br /&gt;
Publishing any of this is a deliberate choice. An agent allowed to touch a research record ought to have its instructions as readable as its output. A reader who doubts a finding can read the finding. A reader who doubts the process can read the process.&lt;br /&gt;
&lt;br /&gt;
Where this stands is the same place as everything else here. GTP is proposed and has not been declared. Exactly one implementation of it exists, which means the claim that it is generic has never actually been tested against a second one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Start here:&#039;&#039;&#039; [[The Principia Machina/GTP/Walk/1 What the orders are, and who writes them|a walk through the instruction layer]], in six pages, written for a general reader. The whole section is on [[The Principia Machina/GTP/Contents|its contents page]].&lt;br /&gt;
&lt;br /&gt;
== Where the analogy holds ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Throughput.&#039;&#039;&#039; The Wrights could test 200 shapes in the time one glider took to&lt;br /&gt;
build. Being wrong became cheap, so they could afford to be wrong often. AI supplies&lt;br /&gt;
derivation labour at a rate a person cannot match, and the point of that rate is the&lt;br /&gt;
same one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A sealed test section.&#039;&#039;&#039; A tunnel excludes weather, terrain and pilot skill so&lt;br /&gt;
that one variable can be read. A TPM container is isolated with its TFK and its full&lt;br /&gt;
register. Comparison against a more complete outside model is out of scope on&lt;br /&gt;
purpose.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Cancelling the suspect constant.&#039;&#039;&#039; The Wrights read a ratio so that a number they&lt;br /&gt;
distrusted dropped out. TPM ranks a finding by its distance to the TFK: how many&lt;br /&gt;
extra assumptions its derivation needs, and how many steps it took. Confidence,&lt;br /&gt;
authorship and expectation are not inputs. Where a finding is compared against an&lt;br /&gt;
outside value, the record reports the difference and never the agreement.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Quarantining the published numbers.&#039;&#039;&#039; The Wrights stopped trusting Lilienthal&#039;s&lt;br /&gt;
tables, rebuilt from their own measurements, and compared afterwards. TPM does this&lt;br /&gt;
deliberately. Derivation runs with the benchmark out of view. The comparison lands&lt;br /&gt;
later as its own record, with its uncertainty stated and its components enumerated.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The instrument gets calibrated too.&#039;&#039;&#039; A tunnel with a bad balance produces&lt;br /&gt;
confident nonsense. TPM verifies a content digest of its own kernel before every&lt;br /&gt;
write, certifies each agent against planted probes before admitting it, and keeps&lt;br /&gt;
planting unannounced probes while it works. A certification pass is a filter, not a&lt;br /&gt;
guarantee, in the way a calibration certificate is.&lt;br /&gt;
&lt;br /&gt;
== Where the analogy breaks ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Internal consistency is not veracity.&#039;&#039;&#039; A perfectly repeatable tunnel result can&lt;br /&gt;
still be wrong about the sky, through scale effects, wall interference, or a&lt;br /&gt;
mismatched Reynolds number. TPM&#039;s version of that failure is a container that is&lt;br /&gt;
flawless and false. The only check for it sits outside the run: comparison against&lt;br /&gt;
measurement, after the fact, recorded as its own finding.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Completeness has a floor.&#039;&#039;&#039; The audit reports a declared degree of freedom that&lt;br /&gt;
nothing tied down. It cannot report one the TPK never named. A tunnel had the same&lt;br /&gt;
blind spot and said nothing about the phenomena it was not instrumented for.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There is no 1902 glider yet.&#039;&#039;&#039; The wind tunnel earned its status when data taken&lt;br /&gt;
from it flew. TPM&#039;s equivalent milestone is a container whose findings survive&lt;br /&gt;
comparison with measurements they were never shown. Until that happens, what this&lt;br /&gt;
page describes is design intent.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
&lt;br /&gt;
By its own analogy, TPM is nearer 1871 than 1901. The duct exists and the balances&lt;br /&gt;
are being designed. The reader should treat the comparison on this page as a&lt;br /&gt;
statement of what the framework is trying to be, and should judge it later against&lt;br /&gt;
findings, not against its own description.&lt;br /&gt;
&lt;br /&gt;
As of 22 September 2026 the specification, TPS 0.1.0, is at revision 4, imported in full with its&lt;br /&gt;
diagrams, keys and terms, and awaits its declaration. The software it specifies,&lt;br /&gt;
TPX on the server and PRB beside each agent, is specified and not yet built; until it&lt;br /&gt;
is, the checks it will execute are performed by a human by inspection, and the&lt;br /&gt;
specification says so at each one.&lt;br /&gt;
&lt;br /&gt;
== The specification, and the machine-optimized pages ==&lt;br /&gt;
&lt;br /&gt;
These pages are the record itself. They are verbatim text, kept exact so that they can be fingerprinted and checked; they are not written to be read first.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The rule book.&#039;&#039;&#039; [[The Principia Machina/TPS|The Principia Machina Specification, TPS 0.1.0]] states every rule of the framework. It is normative and human-only-editable. Its version is proposed; it becomes the published rule book when its fingerprint is landed as the first line of the declarations chain, which the TPM extension (TPX) creates at its first landing. Its human-readable map is [[The Principia Machina/TPS/Contents|Contents]]: parts, pages, tables, diagrams, keys and terms.&lt;br /&gt;
* &#039;&#039;&#039;The reasons.&#039;&#039;&#039; The foundations record (0.12.0) keeps every decision behind the specification, with its sources. It is DATA: it describes, it does not instruct.&lt;br /&gt;
* &#039;&#039;&#039;Implementations.&#039;&#039;&#039; An implementation is the instruction set that makes one AI agent follow the specification&#039;s agent contract. PMP-TPM 0.8.1 is the first, for one vendor&#039;s agent, and is published as the worked case beneath [[The Principia Machina/GTP|GTP]] at [[The Principia Machina/GTP/Claude/Conformance|GTP/Claude]]. Implementations are not normative.&lt;br /&gt;
* &#039;&#039;&#039;For agents and scripts.&#039;&#039;&#039; [[The Principia Machina/Hub/AI agent|The agent entry]] lists the machine-optimized pages. Human readers have no reason to go there.&lt;br /&gt;
&lt;br /&gt;
[[Category:The Principia Machina]]&lt;/div&gt;</summary>
		<author><name>Alt BFP</name></author>
	</entry>
</feed>