FrankenRobotics

Milestones M0–M8

6,817 words12 subsections3 tablesPlan version 1.1

On this page12
43.1 The shape of the program, and why M1 is a CPU studio43.2 Exit rules, and the dependency firewall in brief43.3 M0: spine and airlock43.4 M1: referee studio and first mission slice (CPU only)43.5 M2: batch, backends, families43.6 M3: places, tasks, adversaries, qualification43.7 M4: amortized control, co-design, mission queries at scale43.8 M5: proofs, reality, manufacture43.9 M6: frontier physics43.10 M7: the ten-fold tournament43.11 M8: frontier delivery43.12 No milestone is blocked by one failed bet

A milestone is a set of demonstrations with recorded values, not a date. This chapter gives the shape of the program, the rules for an exit, and one subsection per milestone with the same seven fields: purpose, artifact, what it demonstrates, acceptance, kill gates decided, owner input wanted, and the decision to stop or re-plan. Labels: thresholds repeated here are TARGETs and §40 governs them; week counts are DESIGN planning estimates; North-Star numbers follow §7.

43.1 The shape of the program, and why M1 is a CPU studio

The first wedge is chosen for the same reason FrankenMining chose its own: start where value is deliverable with the fewest unproven dependencies. M1 is a design studio on the CPU referee tier, with the first mission slice. It needs only FrankenSim, asupersync and FrankenSQLite (§33.7). It already demonstrates the thesis in small: a typed design, static analyses from Lie theory, a synthesized controller, a rollout on the transactional referee, structured telemetry, and a mission query answered over a family of designs with a certificate that an independent auditor re-checks, all through one verb registry. GPUs arrive at M2 on top of something that already works.

Three further reasons belong to this version of the plan.

  1. The result is not in the step. §2.3 shows that an infinitely fast environment step cannot deliver the ten-fold ratio. The parts of the thesis that no GPU can rescue (what an answer is, how it is checked, how an amendment withdraws it) are exercised at M1 on fixtures whose answers are known exactly (NS-13, NS-22).
  2. The rival is measured while M1 is built. M0 and M1 time the incumbent loop on trj (§2.7), so M2's engine work is funded against a measured denominator and not against a published one.
  3. A CPU studio survives every admission failure. If the GPU, symbolic and proof foundations all failed admission, M1 would still ship (§33.7).

The order of evidence follows §2.7: measure the rival (M0, M1), put the mission slice on the CPU (M1), run the rank-agreement experiment as soon as two rungs exist (a pilot on incumbent tools by M3, on our tiers at M4), hold a partial ten-fold gate (M3), and run the tournament (M7).

M Name Critical path Planning estimate, elapsed weeks for a swarm Exit is defined by
M0 Spine and airlock Yes 2 The admission records, one kernel on three backends, and the incumbent phase ledger on trj
M1 Referee studio and first mission slice, CPU only Yes 5 NS-01, NS-07 and the docking scenario demonstrated; the schedule gate (BET-12, §40.5) met
M2 Batch, backends, families Yes 6 Kill decisions for the kernel toolchain, contact, Metal and mixed batches recorded as ADRs
M3 Places, tasks, adversaries, qualification Yes 6 The partial ten-fold gate (GATE-TENFOLD-06) recorded, whatever the ratio
M4 Amortized control, co-design, mission queries at scale Yes 8 Rank agreement measured; the family-policy bets decided
M5 Proofs, reality, manufacture No; may overlap M4 6 The Reality lane has a record or a recorded no-claim
M6 Frontier physics No Per epic, 2 to 6 each Per-epic plans and kill gates
M7 The ten-fold tournament Yes; needs M4, not M5 or M6 6, including a two-week freeze and rehearsal The measured ratio published with its phase ledger (GATE-TENFOLD-07)
M8 Frontier delivery No Per epic Per-epic plans and stop rules

The estimates exist to make BET-12 testable. They are not acceptance evidence and no gate cites them. The critical path M0 to M4 and M7 sums to 33 weeks. M0 plus M1 is 7 weeks, so the schedule gate asks its question if they take more than 10.5 weeks for the cause BET-12 names. M5 does not gate M7: a sealed stratum that needs a mechanism of M5 or M6 which has not landed is declared not run in the tournament report, with the reason.

43.2 Exit rules, and the dependency firewall in brief

An exit is recorded by a fresh-context session that did not implement the milestone (§38). It requires all of the following.

  • Every gate of the milestone has a recorded value. A failing value is a record. A kill gate that fired is recorded as an ADR with the fallback now in force, and the capability is described by the fallback's name from then on (§0.2).
  • Every demonstration runs from a clean checkout, through frob --json and, where the registry exposes the verb to agents, through frob-mcp.
  • GATE-GAUNT-01 holds: every gate that passed has a registered negative control that it catches.
  • Every report prints its reality: line (GATE-GROUND-01, from M1 onward).
  • The risk register has been read (§41.4), and the open questions due have been answered or have taken their defaults (§42.1).

A gate may pass before its milestone. It may not move later without an ADR. §40 fixes each gate's milestone and threshold; the lists below name the key gates, and where a list and the register differ, the register governs. A milestone does not exit on a count of gates. Its exit line in §43.1 is the observable. An admission is never inherited: a foundation or an airlock group first used at a milestone is admitted at that milestone, by its own record, at the pin of that day (§33.6). At most four M items are active at once in any milestone (D-6).

The dependency firewall is detailed in §33.7. In brief:

M Needs Uses if admitted If a foundation is missing
M0 Nothing is relied on. The one toolchain T is chosen. FrankenSim, asupersync, FrankenSQLite, FrankenTorch's Metal gateway, cudarc, FrankenSymPy, fastmcp_rust and franken_numpy are admitted. The two P0 upstream work items are done in their repositories: FD-FMCP-01 (fastmcp_rust onto T) and FD-ASUP-01 (one asupersync version) — A failed admission is the result, and its fallback is decided here
M1 FrankenSim (referee, geometry, ledger, memo store), asupersync (jobs, lab runtime), FrankenSQLite (ledger) FrankenSymPy, fastmcp_rust, franken_numpy, frankenscipy CLI only; no kernel certificates. The mission slice is unaffected, because frob-verify uses the standard library alone
M2 FrankenSim (parity oracle), asupersync (device jobs), cudarc, FrankenTorch (Metal backend, gradient oracle), FrankenSymPy (derived kernels), franken_numpy (small-matrix oracle) — The no-GPU variant of §43.5; KILL-KIR; KILL-METAL
M3 FrankenSim (optimizers, racing, statistics, spectral), asupersync (daemon), FrankenSQLite (qualification ledger), fastmcp_rust (full MCP) franken_numpy (the Gymnasium adapter), frankentui, franken_threed, drone-reconstruction schemas Local implementations against the same known answers (OPEN-ATEL-3); KILL-MCP; KILL-TUI; plain Three.js
M4 FrankenSim (optimizers, archive, surrogates), FrankenTorch (policy interchange), FrankenSymPy (exact synthesis lane), fastmcp_rust (mission tools) — The numerical lane of KILL-SYNTH-LINKAGE; policies are exchanged in the native checkpoint format only
M5 FrankenSim (structural, variational, as-built, manufacture), FrankenSymPy (coverage), franken_lean (capsules) Drone reconstruction (scan import) KILL-LEMMA; KILL-REFLECT; KILL-INGEST; the Foundry kill gates
M6 FrankenSim's multiphysics bridge franken_textiles as a cloth oracle M The epic is not funded
M7 Every pin and T frozen for the length of the tournament fastmcp_rust for rival access A pin move or a toolchain train voids the runs it spans
M8 — franken_firmware as a pattern M The epic is not funded

43.3 M0: spine and airlock

  • Purpose. Retire the risks that could invalidate the architecture or the thesis, with the smallest possible amount of code. Two questions are answered by measurement: can the foundations be consumed from outside their trees, and is the rival's loop what §2.2 composes from published figures. No subsystem is built out.
  • Artifact.
    • frob doctor lists the admitted foundations with their records and the stack receipt. DEPENDENCY_ADMISSION.md holds every record, passing or failing, the toolchain matrix of §33.12 and the choice of T.
    • fastmcp_rust builds on T in its own repository, with its test suite and its MCP conformance checks passing (FD-FMCP-01). FrankenSim's constellation, FrankenTorch and fastmcp_rust pin one published asupersync version (FD-ASUP-01).
    • frob sim run g1 --tier referee --seconds 2 produces a state digest equal to the one FrankenSim computes for itself. The same job through frob-fsim-worker returns equal chunk digests.
    • frob spark probe and frob spark fingerprint run on both device families. K-cay-step runs from one source on batch-cpu, CUDA and Metal. The exact and guarded predicate kernels give identical bytes on all three.
    • T-01, T-03 and T-04 have certificates that replay offline. The claim-product type and the no-authorization flags exist in frob-core, with compile-fail tests.
    • The M0 verbs answer through frob --json and through frob-mcp, which is built in the core graph on T, links frob-verbs and runs the verbs in process.
    • The incumbent phase ledger on trj: cold start, a parameter edit and a topology edit to the first step, and time to the return threshold on one and two cards, at pinned revisions, each with a disclosure block.
    • The plan-time pilots re-run in this repository and recorded for Appendix K: the stance enumeration, the docking grid, the pusher battery, the reachable-verdict enumeration of the fixed-n rule, the boundary screen in guarded single precision, the ceiling of the solver comparison, and the power of the draft decision rule.
  • Demonstrates. No North-Star scenario is tagged M0. The milestone delivers the two measurements the program stands on: BET-04 (consumption by path) and the denominator of BET-13.
  • Acceptance. Admission: INT-TOOLCHAIN-01, INT-FSIM-01, INT-FSIM-02 to -11, INT-FSIM-18, INT-ASUP-01, INT-FSQL-01, INT-FT-01, -02, INT-CUDA-01, INT-FSYM-01, -02, INT-FNP-01, -02, and INT-FMCP-01: frob-mcp builds in the core graph on T with one asupersync package, lists the tools generated from the verb registry and passes the MCP protocol smoke test over stdio and HTTP. Upstream: FD-FMCP-01 and FD-ASUP-01 have landed in their repositories, or KILL-MCP is decided. Marrow: GATE-MARROW-01 for SO(3) and SE(3). Spark: GATE-SPARK-00, -01, -07, -08. Lemma: GATE-LEMMA-00, -06. Tether: GATE-TETHER-03. Workspace: GATE-WS-01, -04. Parity baseline: the trj rows of GATE-SPARK-21 that need no agent, which the parity-baseline gate GATE-TENFOLD-01 reads into the first phase ledger (§40.5); the whole of GATE-SPARK-21 closes at M1, and its rows on this Mac close no later than M1. GATE-GAUNT-01.
  • Kill gates decided here. KILL-FSIM, then rolling. Fallback (a): a pinned FrankenSim worker process per device that exchanges whole jobs, already exercised by INT-FSIM-18. Fallback (b), only if (a) fails: lift the minimal referee set with provenance. KILL-MCP, between M0 and M1: it fires only if INT-FMCP-01 cannot pass within the M0 budget after FD-FMCP-01 and FD-ASUP-01 have been attempted. Fallback 1: frob-mcp as its own workspace, talking to frobd over a local socket in newline-delimited JSON. Fallback 2: agents use the CLI, which is complete on its own. The choice of T and the frob-units decision follow the rules of §33.12 and §33.13 from the recorded matrix.
  • Owner input wanted. OPEN-SPARK-1 and OPEN-SPARK-2 (the envelope classes); OPEN-PROG-1 before the first push; OPEN-SUITE-3 and OPEN-SUITE-5; the comparator revisions of OPEN-PERF-2.
  • Stop decision. Re-plan before M1 if INT-FSIM-01 cannot pass within two weeks and the worker process also fails INT-FSIM-18, because the only route left is a lift from a closure of about 1.5 million lines (FACT, §33.2). Rewrite §2 before any work is funded against it if the measured ledger puts the ceilings of §2.3 under 3 for every mission class of §2.6. Drop a device family from M2 if the probe shows that it can hold no controlled determinism class. None of these stops the CPU studio except the first.
  • Work packages. WP-01 to WP-06, WP-34 to WP-37.

43.4 M1: referee studio and first mission slice (CPU only)

  • Purpose. Deliver the smallest product that is already useful and already honest: a design studio on the referee tier and exact answers to the first mission queries, with every result carrying its claim product and every family certificate re-checked by an independent binary.
  • Artifact.
    • The .fbot design language and the model compiler; .fmodule modules with port contracts; the first archetypes (quad-mammal, humanoid, diff-drive, mecanum) and the cart of fixture 1; preflight stages 1 to 6 as frob design check; URDF and MJCF import and export with loss reports.
    • Actuator levels L1 and L2. The transactional referee step with event location, retries that restore all state and witness migration, on planes, primitive obstacles and the door sill.
    • Static analyses inside design check and as separate verbs (§28); the invariant filter and baseline controllers for the first archetypes; the clock contract with its seven instants.
    • Telemetry levels T0 to T2, the energy ledger and frob explain run. The chunk store, the job protocol under seeded faults, and the artifact graph behind frob evidence trace.
    • The core of the requirement language with its three evaluators; fixture:cart-sill-dock; both study types on the CPU, with frob eval preanalyze listing the reachable verdicts of a fixed-n rule.
    • The first mission queries on static conditions: frob mission synthesize on the stance family, the docking family and the pusher battery; frob mission refute; bundles written as .frobcert and accepted by frob-verify built from an empty environment.
    • Lineage basics: content-addressed design versions, frob design diff, typed patches.
    • Every M1 verb on the CLI and over MCP; robot-docs generated from the registry.
  • Demonstrates. NS-01, NS-07, NS-22, and NS-13 on the CPU.
  • Acceptance. Marrow: GATE-MARROW-02. Skeleton: GATE-SKEL-01 to -08, with GATE-SKEL-03 for the first archetypes and GATE-SKEL-04 for stages 1 to 6. Sinew: GATE-SINEW-01, -02, -04 to -08 on the referee. Kinesis and Traction: GATE-KIN-01, -02; GATE-TRAC-02; and the referee rows of GATE-KIN-04, GATE-TRAC-01 and GATE-TRAC-06, whose strict rows close at M2 with batch-cpu. Sensorium: the CPU rows of GATE-SENS-04, -05 and -12 and the docking rows of GATE-SENS-08 and -09, because the mission slice needs them. Reflex: GATE-REFLEX-01 (referee rows), -03. Atelier: GATE-ATEL-02 for the analyses that exist, -06, the analysis parts of -05 and -12, and the dependency grades of -11 on mission cells, with INT-FSIM-16 and INT-FSQL-02 for the memo store. Chronicle: GATE-CHRON-03 (referee), -04 (CPU), -10, and the CPU part of -11. Arena: GATE-ARENA-03, -04 (referee rows), -05. Augur and Lemma: GATE-AUGUR-01 to -07; GATE-LEMMA-03, -04. Ground: GATE-GROUND-01. Tether and safety: GATE-TETHER-02, -07; GATE-SAFE-01, -08, -10; GATE-WS-03, and GATE-WS-02 for the formats that exist; INT-FMCP-01 for the M1 verbs. Parity baseline: GATE-SPARK-21 complete. Program gates: GATE-TENFOLD-02, GATE-TENFOLD-09 and the schedule gate (BET-12) of §40.5. GATE-GAUNT-01.
  • Kill gates decided here. The schedule gate (BET-12): if M0 plus M1 took more than 1.5 times their estimate because a sibling lacked a primitive, its upstream work item had not landed and no interim posture applied, the program pauses for a written re-plan before M2. KILL-SKEL-SEXPR (fallback: JSON is the only syntax). KILL-SKEL-SUBST (fallback: every substitution is global). KILL-AUGUR-FALSECERT stands from this milestone on: one certificate accepted by frob-verify and shown false removes its proof kind if the rule is at fault. The first reading of KILL-AUGUR-TIE is taken on the docking slice: if a conventional scenario-tree program gives the better answer per engineering hour, that program ships behind the same verbs (§25.23).
  • Owner input wanted. OPEN-PROG-4, the compute for the rank-agreement experiment; the owner's reading of the M0 ledger against §2.6.
  • Stop decision. The schedule gate. Beyond it, re-plan the mission chapter before adding physics if a fresh agent cannot complete the docking and stance amendments of GATE-AUGUR-07 after one repair cycle, because the mapping from sensors and actuators to the query is then the defect. Re-plan the referee if its refusal rate on the M1 fixtures (OPEN-KIN-5) leaves the sill fixture without a completed run.
  • Work packages. WP-07 to WP-14, WP-38 to WP-43.

43.5 M2: batch, backends, families

  • Purpose. Put the batch under the studio: one model on batch-cpu, CUDA and Metal, with many designs in one batch, measured against the incumbent on the same cards. Decide by measurement the four things the engine rests on: the kernel toolchain, the contact law, the Metal tier and mixed batches.
  • Artifact.
    • The batched step in the lockstep and strict profiles on three backends; frob spark check, frob spark place with requested-versus-actual receipts, the arena lease and the binary kernel cache.
    • Scene packs and terrain generators (frob scene gen, frob scene compile). Contact law CL-1 with the four-dimensional cone and joint stiction and backlash rows, with diagonal scaling.
    • Proprioception, height scans, depth, lidar, and camera exposure and rolling-shutter timing; stills and the viewer page.
    • VecEnv with explicit reset, preserved final observations and the termination and truncation distinction; PPO on device (frob train start), with the two-device update rule.
    • Per-world parameter variants and model variants: frob phylum plan, frob phylum sweep; the head-to-head experiment of §17.14 run and published with all four arms.
    • The fidelity and divergence ledgers (frob fidelity ledger); replay and teleport (frob sim replay --world 1337 --tier batch-cpu); forks (frob run fork); the sampled referee (frob fidelity shadow).
    • The daemon's job engine with device ownership and idempotent submission; frob sim estimate.
    • Throughput and training-time figures against the incumbent measured on trj, each with its disclosure block.
  • Demonstrates. NS-02, NS-10, NS-14.
  • Acceptance. Kinesis and fidelity: GATE-KIN-03, -05, -06, -07; the strict rows of GATE-KIN-04; GATE-FID-01, -03, -06, -07. Traction and Sinew: GATE-TRAC-01 (strict and batched rows), -03, -04, -06, -10; GATE-SINEW-03, -09, and the batched rows of GATE-SINEW-02 and -04. Marrow: GATE-MARROW-05. Reflex: the batch-cpu rows of GATE-REFLEX-01. Habitat: GATE-HAB-01, -13. Sensorium: GATE-SENS-01 to -06, -12, -13. Spark, numerics and performance: GATE-SPARK-02 to -06, -09 to -12, -15, -16, -18, -19, -20, -22. Phylum: GATE-PHYLUM-02, -03, -04. Cortex: GATE-CORTEX-01, -02, -05 to -09. Chronicle and forks: GATE-CHRON-01, -02, -05 to -08, -12, -13, with the device rows of -03, -04 and -11; GATE-AUTOPSY-01, -02, -07; the episode part of GATE-ATEL-12. Arena: GATE-ARENA-01, -06, -08, and the batch-tier rows of -04. Tether and safety: GATE-TETHER-04, -05, -06, -08; GATE-SAFE-06, -07; INT-ASUP-02. KILL-TENFOLD-LEVER is re-read on our own profile. GATE-GAUNT-01.
  • Kill gates decided here, each recorded as an ADR.
    • KILL-KIR: hand-written arithmetic in Rust and the dialect, bound by differential tests.
    • KILL-CONTACT: CL-2 as the default at a published lower throughput; then locomotion claims on the referee only.
    • KILL-METAL: Metal becomes the development and replay tier, and the Mac trains on batch-cpu.
    • KILL-PHYLUM, with KILL-BUCKET: per-family templates become the engine; parameter variants are unaffected.
    • KILL-D1: the family is class D2 for itself and D3 against others, and a teleported world is a tolerance replay.
    • KILL-PARITY: feature work on the device tier stops until the row is inside tolerance.
    • Also decided: KILL-SHARD, KILL-LEARNKERN, KILL-MARROW-GUARD, KILL-SINEW-ROWS, KILL-POOL, KILL-EXPOSURE, KILL-SCHED, with the fallbacks their chapters name.
  • Owner input wanted. OPEN-SPARK-1 falls due at this exit. OPEN-PHYLUM-3 for the head-to-head. OPEN-PROG-2 and OPEN-ARENA-3, because sealed world families are built at M3. OPEN-CHRON-4.
  • Stop decision. Stop feature work on the device tier, and redo the arithmetic of §2 and §39 with measured rates, if a physics row is below 0.33 of the incumbent after one optimization pass (KILL-PARITY). Re-plan the legged strata of the partial gate if both fallbacks of KILL-CONTACT are exhausted. Name an adjudicator, or restrict claims to the classes the referee covers, if GATE-FID-03 reports coverage under 90% for a reference class. Fall back to the variant below if no device family holds batch-composition invariance.
  • The no-GPU variant. DESIGN: M2 can exit without a device. It applies if OPEN-SPARK-1 is not ratified, if INT-CUDA-01 and INT-FT-01 both fail, or if no device family holds a controlled class. Everything above lands on batch-cpu, on the 36 cores of the M5 Ultra and on the CPU of trj: the batched step in both profiles, VecEnv, PPO, variants and cohorts, the ledgers, replay, forks and the sampled referee. The Known answer, Parity and Fidelity gates run on batch-cpu; rows 13 to 15 of §36.3 are the Performance rows; device gates are recorded not run with the reason, and any device result that exists is labelled exploratory. NS-10 and the device halves of NS-02 and NS-14 are not demonstrated. The partial gate at M3 then charges the CPU engine's measured rate in full, and the strata that need no device (family queries, amendments, failure discovery on small worlds) are run first.
  • Work packages. WP-15 to WP-22, WP-44 to WP-52.

43.6 M3: places, tasks, adversaries, qualification

  • Purpose. Make results trustworthy enough to be compared with a rival, and then make the first comparison. Places, tasks, adversarial worlds, autopsy and blinded qualification land together because the partial ten-fold gate needs all of them: a mission to answer, a way to accept the answer, and a way to break it.
  • Artifact.
    • Seven interior archetypes with hazard lists: frob scene gen, frob scene accept, frob scene hazards, frob scene split; film-friction patches and rigid proxies; the world bank (frob scene bank).
    • Clearance complexes (.fclear) that return a route witness or an impossibility cut; the mesh path with enclosures and thin-feature detection.
    • Arena task families through tight-space maneuvering; requirement verdicts (frob task verdict); fixture 2; scorecards with full denominators.
    • The blinded qualification lane: frob eval qualify on sealed world clusters with pre-committed requests.
    • Nemesis: frob nemesis search, frob nemesis shrink to a .fmcw file, frob nemesis bound.
    • Autopsy: frob autopsy fork, frob autopsy attribute, frob autopsy repair, with the placebo fork.
    • Promotion with tier correction (frob eval promote), the exploitation detectors (frob eval detect) and the model-form rank check (frob fidelity modelform).
    • The daemon with slot dispatch, capabilities and budgets; the full MCP surface in task clusters of at most seven tools; the dashboard frob-tui.
    • The design corpus with frozen labels and the design benchmark; baseline controllers for all eighteen archetypes; the sampling controller as fallback (frob control mpc); the Gymnasium-compatible adapter.
    • Mission queries under amendment: frob mission revalidate, frob mission separate, and the expert grid behind frob experiment suggest.
    • The rank-agreement pilot on incumbent tools, and the partial ten-fold gate on legged and wheeled briefs, with a phase ledger for each arm.
  • Demonstrates. NS-03, NS-04, NS-09, NS-15, NS-16, NS-17.
  • Acceptance. Habitat and Traction: GATE-HAB-02, -04, -05, -06, -10, -12, -14; GATE-TRAC-05, -07. Sensorium: GATE-SENS-07 to -11, -14. Arena and qualification: GATE-ARENA-02, -07, -09; GATE-QUAL-01, -02. Nemesis: GATE-NEMESIS-01 to -06, -08. Autopsy: GATE-AUTOPSY-03 to -06. Fidelity and evidence: GATE-FID-02, -04, -05, -08 (GATE-FID-07, the sampled referee, is at M2); GATE-CHRON-09; GATE-SPARK-17. Reflex and Cortex: GATE-REFLEX-02, -05; GATE-REFLEX-01 for every archetype except tracked and hybrid; GATE-REFLEX-04 for the legged and wheeled classes; GATE-CORTEX-04, -10, -15, -16; GATE-CORTEX-12 as a pilot. Atelier: GATE-ATEL-01, the comparison row of -04, and the M3 parts of -07, -08, -11 and -13. Augur: GATE-AUGUR-06 (repeated), -08 to -10 and -12 to -14, with GATE-AUGUR-09 as a pilot. Skeleton, Marrow and Phylum: GATE-SKEL-03 and GATE-SKEL-07 for all eighteen archetypes; GATE-SKEL-04 for stages 7 and 8; GATE-MARROW-03; GATE-PHYLUM-01, -05, -07. Tether and safety: GATE-TETHER-01, -09 to -12, -14; GATE-SAFE-02 to -05, -09. Admission: INT-FSIM-13, -14 for the spectral and statistics groups; INT-FMCP-01 for the full surface; INT-FTUI-01 for the dashboard; INT-F3D-01; and INT-FDGR-01 for the schema fixtures. Program gates (§40.5): GATE-TENFOLD-03, -04, -05, -10 and -11 before the sealed suite is opened; the partial ten-fold gate, GATE-TENFOLD-06; and GATE-TENFOLD-13. GATE-GAUNT-01.
  • Kill gates decided here.
    • KILL-STATIC: design check verdicts become advisory lints and the pruning claim is withdrawn.
    • KILL-BASELINE: synthesis is limited to the classes that pass; others route to the sampling fallback or to training.
    • KILL-NEMESIS, KILL-RARE, KILL-MCW: card randomization with the legality profile, the oracle and the guard; crude sampling with a binomial bound; full failing worlds with replay.
    • KILL-AUTOPSY: single-factor paired re-runs from the episode start.
    • KILL-DR and KILL-SHADOW: promotion from referee episodes alone; the referee at promotion time only.
    • KILL-FAMILYCERT and KILL-AUGUR-TIE, read at the partial gate: mission answers come from generic solvers behind the same verbs, schema and checker.
    • Also decided: KILL-SLOT, KILL-PREEMPT, KILL-MCPTASKS, KILL-TUI, KILL-GYMADAPT, KILL-SPEC-REWARD, KILL-FCLEAR, KILL-FILM, KILL-MESHGPU, KILL-BANK-BREADTH, KILL-QUOTIENT, KILL-ALIAS, KILL-SKEL-ALIAS, KILL-AUGUR-REGION, KILL-AUGUR-REUSE, KILL-AUGUR-SEPARATE, KILL-AUGUR-PROBE, KILL-AUGUR-ALIAS.
    • KILL-AUGUR-FALSECERT applies to both arms of the partial gate.
    • The rule of BET-13 is applied per mission class at the partial gate (see the stop decision).
  • Owner input wanted. OPEN-CORTEX-1, the envelope for family-policy pretraining, which M4 needs on its first day. OPEN-PROG-3. OPEN-AUGUR-4. OPEN-HAB-1 and OPEN-HAB-4. OPEN-SHIELD-2. OPEN-SAFE-4.
  • Stop decision. The partial gate decides, by the rule written before it runs. A measured ratio under 3 on a mission class withdraws the speed claim for that class. Under 3 on every class, speed work is no longer funded, the product is positioned on replay, qualification, certificates and the evidence ledger, and the family-policy spend of M4 is decided again. Where the composed-incumbent arm is within a factor of 1.5, the layer ships over that engine for the stratum (BET-14). Separately: if GATE-QUAL-01 fails, nothing is called qualified, and confirmation falls back to fixed-n exact studies with a hard cap on submissions before any tournament is scheduled.
  • Work packages. WP-23 to WP-27, WP-53 to WP-60.

43.7 M4: amortized control, co-design, mission queries at scale

  • Purpose. Build the two levers that carry the thesis, deciding many designs per turn and training few of them, and extend mission queries from CPU fixtures to families on the GPU.
  • Artifact.
    • Family policies per morphology class (frob train family, frob policy apply), inheritance along design edits (frob train inherit) and distillation (frob train distill).
    • The rank-agreement record per class and task family (frob eval rank-agreement) and the ladder that allocates by it (frob opt cascade), with the audit lane and the planted winner.
    • Equivariant policies under the observation-preserving subgroup; gait orbits with continuation (frob gait orbit, frob gait continue).
    • Optimization, racing and the quality-diversity archive (frob opt start, frob opt archive); frob design bisect; registered predictions; the co-design cascade and the decision cores DC-01 to DC-11.
    • Mission queries over design families on the GPU, with region certificates on small sub-boxes, monotone transport and product-system dominance; frob result revalidate.
    • Synthesis: frob mission synthesize --strategy codesign, refine and linkage.
    • Tyre laws, tracks, wheel-leg hybrids, moving surfaces and soil cards; the priced retrofit catalogue and its search (frob scene retrofit).
    • The energy-budget tier and runtime shields (frob shield budget, frob shield fit, frob shield check).
    • frob experiment suggest ranked by value of information; the agent-surface A/B; frob solve run; the fleet scheduler (frob fleet plan).
  • Demonstrates. NS-05, NS-06, NS-08, NS-18, NS-19, NS-23, and NS-13 at scale.
  • Acceptance. Cortex: GATE-CORTEX-03, -11, -12, -13, -14. Reflex, gaits and shields: GATE-REFLEX-04 for tracked and hybrid classes; GATE-REFLEX-06, -07, -08; GATE-GAIT-01, -02, -03; GATE-SHIELD-01 to -04. Atelier: GATE-ATEL-03, -07 to -10, -14, -15, -16, the bisect row of -04, and the rest of -02, -05, -11 and -13. Augur and Lemma: GATE-AUGUR-09, -11, -14 to -19; GATE-LEMMA-04 (repeated). Phylum, Nemesis and Autopsy: GATE-PHYLUM-06, -08; GATE-NEMESIS-07; GATE-AUTOPSY-08. Habitat, Traction, Spark and Marrow: GATE-HAB-11; GATE-TRAC-08; GATE-SPARK-13, -14; GATE-MARROW-04. Tether: GATE-TETHER-13. GATE-REFLEX-01 closes here for the tracked and hybrid archetypes. GATE-GAUNT-01. The register places GATE-HAB-11, GATE-SHIELD-01 and GATE-AUGUR-11 here, with their mechanisms (§40.7).
  • Kill gates decided here.
    • KILL-FAMILY: no family policy; specialists with inheritance from the nearest parent, and the baseline screens.
    • KILL-INHERIT and KILL-DISTILL: children train from the class prior or from scratch; distillation only from a privileged teacher.
    • KILL-RANK and KILL-LADDER: R1 is uninformative and every candidate that survives static analysis is scored on the higher rung; the fixed halving table allocates among trained candidates.
    • KILL-EQUIV: symmetry is used for augmentation and metamorphic testing only.
    • KILL-GAIT, KILL-MPC, KILL-RESIDUAL: orbits as diagnostics; the sampling controller as a debugging aid; no residual rung.
    • KILL-SHIELD and KILL-ENERGY: barrier rows become penalties and alarms, and nothing is called a shield; an energy claim that shows an exceedance is withdrawn and its monitor stays as an alarm.
    • KILL-RETROFIT: the catalogue stays as Nemesis's edit vocabulary and the search verb is withdrawn.
    • Also decided: KILL-VOI, KILL-REUSE, KILL-FDGRAD, KILL-ATLAS, KILL-ALTALGO, KILL-SOLVE, KILL-FLEET, KILL-SPECIALIZE, KILL-FAMILYLANE, KILL-RESPONSE, KILL-SOIL, KILL-MARROW-BLOCKS, KILL-SYNTH-CODESIGN, KILL-SYNTH-TRAJOPT, KILL-SYNTH-LINKAGE, KILL-AUGUR-CUTS, KILL-AUGUR-DOMINANCE, KILL-AUGUR-LABELS.
  • Owner input wanted. OPEN-CORTEX-1 if still open. OPEN-SINEW-1 and the other catalogue questions. OPEN-SAFE-3. OPEN-TETHER-5. OPEN-NEMESIS-3. OPEN-PROG-5 before M5 closes.
  • Stop decision. If KILL-RANK fires for every class and KILL-FAMILY fires as well, the lever "train few" is gone. The ceilings of §2.3 are then recomputed with the measured trained fraction, every class whose ceiling is under 3 leaves the speed claim, and the sealed suite of M7 is re-stratified before it is sealed. M7 still runs, because its result is published whatever it is. Specialized GPU work stops in any cell where the timing of slice 4 of §25.23 shows that transfers, authoring, training, checking or the rival's reuse rule out the target.
  • The variant with no family policy. DESIGN: M4 can exit without one. It applies if OPEN-CORTEX-1 stays at its default, if the pre-funding pilot meets its falsifier, or if KILL-FAMILY fires. The rungs are then the static check, the baseline controller, the sampling controller, gait orbits, and per-design specialists that inherit from the nearest parent. The ladder runs per class in the mode its measured rank agreement permits (GATE-REFLEX-04), which is uninformative until a record exists (§28.10). GATE-CORTEX-11 is recorded as failed or not run, BET-15 as falsified or untested, NS-19 is not demonstrated, and §39 records the factor that was lost. Every other artifact of the milestone lands unchanged.
  • Work packages. WP-28 to WP-30, WP-61 to WP-67.

43.8 M5: proofs, reality, manufacture

  • Purpose. Strengthen what can be trusted and what can be built. None of it shortens the time to a decision (§2.5), so none of it gates M7.
  • Artifact.
    • Certificate coverage across derived kernels (frob prove kernel, frob prove bundle); Lean theorem capsules re-checked by FrankenLean; the reflection pilot (frob prove reflect); replay of a qualification campaign by frob-verify.
    • The articulated variational integrator on the referee and the strict profile; the hard-contact batch law on batch-cpu.
    • Ground: frob ground ingest, excite, identify, predict, score, band and kit, exercised first on the synthetic rehearsal; the first real cell if data is admitted.
    • Real-place ingestion: frob scene import, frob scene fit, frob scene probe-request; asset-populated interiors, if their pilot funds them; the tree-operator route as a pilot.
    • Foundry: frob foundry loads, size, optimize, check, tolerance and export, ending in a .fbuild packet whose four flags are false.
  • Demonstrates. NS-11, NS-12, NS-20, NS-21.
  • Acceptance. Lemma: INT-FLN-01, -02; GATE-LEMMA-01, -02, -05; GATE-QUAL-03. Kinesis and Traction: GATE-TRAC-09 on batch-cpu (§18.17 admits those rows from M3; the GPU rows are M6). Habitat: GATE-HAB-03. Ground: GATE-GROUND-02 to -09; GATE-GROUND-10 is tied to no milestone and is recorded when data is admitted (§40.6). Foundry: GATE-FOUNDRY-01 to -10, with INT-FSIM-15 for the structure group. Admission: INT-FDGR-01 for scan import. Formats: GATE-WS-02 complete for all thirteen. GATE-GAUNT-01. Four of these are tagged M4 by their chapters and may pass there: GATE-FOUNDRY-01 to -03 and GATE-GROUND-03.
  • Kill gates decided here. KILL-LEMMA: certificates become exact-rational randomized tests recorded as Tested. KILL-REFLECT: instance certificates stay Certified and reflection is parked. KILL-VARIATIONAL: the free-body step as oracle and the default integrator everywhere. KILL-HARDCONTACT: fixed-iteration island solvers with a residual flag, and the law kept as a specification and a model-form arm. KILL-GROUND, KILL-BAND, KILL-CLOCK, KILL-ASBUILT, KILL-KIT: Ground keeps admission, frozen predictions, direct measurements and time-free metrics, withdraws bands, and reports reality: no-claim. KILL-INGEST: a surveyed proxy authored in the interior grammar. KILL-DRESSING: structural proxies and static clutter only. KILL-LOADS, KILL-TOPOPT, KILL-FAB, KILL-TOLERANCE, KILL-PACKET: load cases declared by hand, beam sizing, advisory lints, worst-case boxes, and a packet reduced to a parts list, mass properties and STL. KILL-TREEOP and KILL-SKEL-PORT: the dense factorization and a cap of 64 degrees of freedom.
  • Owner input wanted. OPEN-GAUNT-1 and OPEN-GROUND-2. OPEN-HAB-5. OPEN-FOUNDRY-2 and OPEN-SKEL-2.
  • Stop decision. Nothing here stops the program: every lane has a fallback that ships under its own name, and the exit is a record or a recorded no-claim. Lanes stop singly. Work on Lemma beyond the coverage gate is not funded further before M7 if no consumed certificate has changed a decision by this exit (OPEN-LEMMA-5). Ground work beyond the rehearsal waits if no dataset has been admitted.
  • Work packages. WP-31, WP-32, WP-68 to WP-72.

43.9 M6: frontier physics

  • Purpose. Admit the physics that makes more failures visible, behind feature flags and off the critical path. Each epic needs its own short plan, its paper-scale pilot and its kill gate before work starts.
  • Artifact. Epics, in the default order of funding: robot-advected films, payload slosh, and cable and rug proxies F; then Cosserat rods, cloth and coupled islands on the CPU referee for finalists M; soft soil at scale; the hard-contact law on devices; the tree-operator route and the mesh path on devices, where their pilots at M5 and M3 kept them F; tactile sensing M; the rotor port M; RGB and splat scenes; moving people; gradients through contact with their validity labels; the holonomy and symmetry-at-contact queries of §25; lifecycle compression M.
  • Demonstrates. No North-Star scenario is tagged M6. Each epic's plan names its own acceptance story, and the Frontier half of BET-36 is tested here.
  • Acceptance. GATE-HAB-07, -08, -09; GATE-AUGUR-20, -21; the device rows of GATE-TRAC-09; GATE-FOUNDRY-12, which §31.19 tags M8 and which closes with its epic; INT-FSIM-17; INT-FTX-01, with the cloth oracle run as a worker process (§33.17); the known answers each epic's chapter lists.
  • Kill gates decided here. KILL-LIVING: Solid and Frontier proxies only, and no islands. KILL-ADVECT: static film-friction patches, and advection is not built. KILL-SLOSH: rigid ballast with a spill metric. KILL-PROXY: Solid proxies in training. KILL-SINEW-ROTOR and KILL-SINEW-AGE: the rotor port is withdrawn; ageing factors are constants. KILL-LIFECYCLE: aged model variants at hand-specified wear states. KILL-AUGUR-PHASE and KILL-AUGUR-SYMEVENT: the forward diagnostic and per-event finite differences.
  • Owner input wanted. OPEN-PROG-5 and OPEN-AUGUR-10: which epics are funded, in which order, under the cap of four active M items.
  • Stop decision. An epic stops when its pilot's falsifier holds or its kill gate fires. The whole milestone pauses whenever M4 or M7 is slipping, since nothing here is on their path.
  • Work packages. WP-33, WP-73 to WP-75.

43.10 M7: the ten-fold tournament

  • Purpose. Measure the thesis against the strongest composed rival, and publish the measured result whatever it is.
  • Artifact. The sealed suite in named strata. Every pin frozen. The rival arms: the strongest composed incumbent workflow, tuned on development fixtures and then frozen, and our own layer over the incumbent engine where the verbs allow it. Neutral adjudication with receipts released after both arms close. The report: per stratum, the ratio of restricted mean times with its interval, cold and warm runs separately, the crossover reuse count, a phase ledger for each arm that sums to wall-clock, the audit of every submitted certificate by frob-verify, the tie statement, and the count of certificates that changed a decision.
  • Demonstrates. NS-24.
  • Acceptance. The program gates of §40.5: GATE-TENFOLD-03, -04, -05 and -11 repeated before the sealed suite is opened; the tournament, GATE-TENFOLD-07; the replication kit, GATE-TENFOLD-08; suite hygiene, GATE-TENFOLD-12; and the recovery ratios of GATE-TENFOLD-13 on the sealed suite. Exit is the publication of the measured ratio with its phase ledger. GATE-GAUNT-01.
  • Kill gates decided here. No mechanism is killed at M7. Three written rules are applied: the decision rule of BET-13 and its wording for each range of the ratio; the tie rule of BET-14; and disqualification of an arm from the scoped claim by one false certificate.
  • Owner input wanted. OPEN-PROG-2, the neutral party and the adjudicating simulator, confirmed before the suite is sealed. OPEN-PROG-1. The envelope for the tournament itself (§44.2).
  • Stop decision. A tournament is not stopped by an interim number. It is voided and re-run only for a breach of protocol: a pin moved during the freeze, sealed material read by an arm, or a rival arm changed after its freeze. After publication the positioning follows BET-13: the product is described by its measured ratio per stratum, and by auditability where the ratio is under 3.
  • Work packages. WP-76, WP-77.

43.11 M8: frontier delivery

  • Purpose. Deliver the Moonshot items that would make the product unlike anything else, each behind a flag and each with a stop rule. The plan works without every one of them.
  • Artifact. Epics: facility co-design and multi-robot handoff (slice 5 of §25.23); skill transport with learned residuals; continuation-based synthesis on the CPU; firmware export; geometric-algebra tree policies at scale; reachable-set tables for shields; the fused per-world step kernel.
  • Demonstrates. No North-Star scenario is tagged M8.
  • Acceptance. GATE-AUGUR-22, -23, -24; GATE-REFLEX-09; GATE-CORTEX-17; GATE-SHIELD-05; GATE-FOUNDRY-11.
  • Kill gates decided here. KILL-AUGUR-FACILITY: single-robot missions with priced world edits. KILL-AUGUR-TRANSPORT and KILL-SKILL: family policies and inheritance; the exact skill layer and its witnesses. KILL-SYNTH-CONT: the exact lane with multi-start recovery, labelled Partial. KILL-GATREE: the plain morphology transformer. KILL-TUBE: reduced-order barriers. KILL-FIRMWARE: controller parameters and test vectors, and no code. KILL-MEGA: the staged step plan, which is the design of record.
  • Owner input wanted. Funding per epic, and an envelope of class E3 for any pretraining.
  • Stop decision. Per epic, by its stop rule. An epic that has not passed its pilot within its planned weeks returns to the register of Appendix C and frees its slot under the cap.
  • Work packages. WP-78 to WP-80.

43.12 No milestone is blocked by one failed bet

DESIGN: for every bet that a milestone tests, the milestone has an exit that does not need the bet to hold. The fallback ships under its own name, and the lost capability is recorded.

M Bet or decision that could fail The milestone still exits with
M0 BET-04: FrankenSim is consumable by path The worker process; the lift only if that fails
M0 INT-FMCP-01 cannot pass within the M0 budget after FD-FMCP-01 and FD-ASUP-01 have been attempted KILL-MCP: frob-mcp as its own workspace over a local socket to frobd; then the CLI, which is complete on its own
M1 A symbolic, proof or GPU foundation fails admission The same M1: it needs FrankenSim, asupersync and FrankenSQLite only
M1 BET-19 on the first slice: a conventional program answers the docking query as well That program behind the same verbs, schema and checker
M2 OPEN-SPARK-1 unratified, or both device families fail The no-GPU variant (§43.5)
M2 BET-18: mixed batches lose Per-family templates with per-world parameter variants
M2 BET-09: Metal is not a rollout tier CUDA trains; the Mac keeps the world bank, proof, replay and batch-cpu
M2 BET-34: the referee covers too little The strict profile as named adjudicator, with results that say so
M3 BET-06: baselines fail on many morphologies The sampling fallback and training for the classes that fail
M3 BET-21: the blinded lane does not hold its error rate Fixed-n exact confirmation with a cap on submissions
M3 BET-22, BET-23: adversarial search or attribution underperforms Randomization with shrinking and the guard; single-factor re-runs
M3 No neutral party is named (OPEN-PROG-2) A partial gate labelled self-adjudicated
M4 BET-15, or no compute envelope (OPEN-CORTEX-1) The variant with no family policy (§43.7)
M4 BET-17: rank agreement is low Cheap rungs that discard only; the fixed halving table
M4 BET-20: region certificates decide too little Dual witnesses, monotone bounds and sampled coverage labelled Estimated
M5 BET-11: certificate coverage is unaffordable Exact-rational randomized tests recorded as Tested
M5 BET-28, or no data arrives reality: no-claim, recorded as the state
M5 BET-29: generative structure saves too little Beam sizing and the structural margin analysis
M7 BET-13: the ratio is under ten The measured ratio, published per stratum with the wording BET-13 fixes
M7 BET-14: the composed incumbent ties The layer over that engine for the stratum, and a report that says so