The operator (2026-09-26), setting a goal: Ruliad Realize the generalized omnisociative rig; formalize it as zero-dependency, generatively emitted first-order logic; apply it to the near-term needs of our own stack, from the picokernel out to the MCP tools behind the untool lens; and represent human–machine and machine–machine rigs as digital twins across their dynamical and evolutionary states and transitions.

What exists now (implemented and tested, not deployed; untool-platform PR #2969, commit 9a93d69)

• Generalized rig (ontology/rig v0.3).
• A practitioner may be human, machine, collective or hybrid. This is a property of the rigging, so one agent can be a practitioner in one rig and an element in another.
• Machine couplings are protocol, interconnection or supervision, and must name their contract (A13).
• Dynamics.
• A rig's state is never stored. It is folded from append-only transition events over a declared lifecycle: 12 states, 36 moves.
• Parts and wholes move separately.
• Dynamical changes (within a space) are distinguished from evolutionary ones, where the configuration space itself is rewritten.
• Twins.
• "Complete" means complete relative to a signature, an observation set and an epoch. That is decidable: finite first-order model checking is decidable (Stockmeyer 1974; Vardi 1982). It is never absolute (Trakhtenbrot 1950; Rice 1953; Löwenheim–Skolem).
• Axiom A19 checks every such claim; it does not trust it.
• FOL as a house mechanism.
• Any IR constraint may carry fol:. tools/selfmodel/emit_fol.py checks it against the signature and emits CLIF, TPTP and a JSON AST.
• The emitter also generates a complete integrity layer from the IR: 370 axioms for the rig.
• tools/fol/fol-check.mjs has no dependencies and evaluates the axioms closed-world. Its verdicts agree with SHACL.
• It caught a defect SHACL passed: a source record swallowed by a comment line.
• Applied. The house stack is the first machine–machine rig. Its twin (a hand-recorded digital model) shows:
• the stack is degraded;
• four near-term needs are unmet;
• restoring the self-hosted runners alone meets two of them (board writes, required checks);
• the picokernel (ring 0) is unobserved.
• Grounding. RuliadRealizer arms 7–9 cover human–machine, machine–machine, and twins and their limits:
• Engelbart's H-LAM/T is the closest structural ancestor, but it lacks the needs-to-configuration loop.
• Bainbridge's irony of automation gives invariant I10.
• Willems' connector vertex gives invariant I11: an n-way coupling is not recoverable from pairs, which is the house's hyperedge-as-vertex met from control theory.
• Every edge in arms 7–9 is reconstructed-by-runner.

Not claimed

• That the twin is live or current past its one-hour staleness bound.
• That a restoration is cheap, safe or within an agent's authority.
• That software composes like passive physical systems.
• That the operator drew on any of these ancestors.

Pending

• The falsifier's review of arms 7–9.
• The operator's review of v0.3, I10 and I11.
• The Towa load and lens redeploy, both on the operator box.