FrankenRobotics

Risks and the pre-mortem

6,128 words5 subsections5 tablesPlan version 1.1

On this page5
41.1 It is late 2029 and FrankenRobotics failed. Why?41.2 Every gate passed and the claim still failed41.3 Risk register41.4 How the register is used41.5 Four risks that follow from late foundation facts

This chapter asks how the program fails, names the earliest measurement that would show each failure coming, and points at the mechanism that answers it. It has three parts: a pre-mortem written from a failed future, a second pre-mortem for the case where every gate passed and the claim still failed, and the risk register. Labels: every threshold in a signal or mitigation column is a TARGET repeated from the gate named beside it, and §40 governs where the two differ; incumbent figures are FACTs registered in Appendix H; counts of crates, milestones and gates are FACTs about this document (§34.2, §40, §43). Nothing in this chapter is a result.

41.1 It is late 2029 and FrankenRobotics failed. Why?

DESIGN: each row is a story told from the failure backwards. The earliest signal is a quantity the program already records, chosen so that it moves while the failure is still cheap. The countermeasure names the section that owns it. The residual is what remains after the countermeasure works as designed. Stories 1 to 15 are carried from version 0.2 with their countermeasures corrected to this version's mechanisms. Stories 16 to 27 are new: five about the thesis, three about the evidence, four about the program.

# Failure story Earliest signal Countermeasure in this plan Residual
1 The mathematics became the product. Elegant algebra crates grew and no robot walked. Layer-1 crates grow while the M1 exit slips; a construction with no verb or no failing test D-2 and D-6 (§9); milestone exits are robots moving and answers accepted (§43); a construction missing any of its four obligations moves to Appendix C The temptation is constant
2 FrankenSim moved weekly and adapter churn consumed the effort. BET-04's metric: upstream breakage above 20% of working days in a four-week window. Context (FACT, §33.2): 409 commits touched fs-mbd in thirty days Pinned commit, the airlock, the compatibility train; KILL-FSIM with the worker process first and the lift second (§33.8, §33.14) The lift is priced against a closure of about 1.5 million lines, not against two crates
3 GPU kernels passed tests and diverged in the field, so nobody trusted fast results. Divergence-ledger entries without explanations; a world whose digest depends on the batch it ran in spark.check on every driver or compiler change; the fingerprint gate; teleport; batch-composition invariance (GATE-SPARK-15); decision-level equivalence (GATE-SPARK-16); the promotion rule (§16, §21, §35) Class D3 comparisons are statistical
4 Throughput landed far under the parity band and agents stopped waiting. The M2 profile; a paired lower bound under 0.67 of the incumbent measured on trj Profile first (§36); KILL-PARITY; KILL-KIR; the ladder reduces how many steps a decision needs (§28) Every figure is a TARGET until M2
5 Policies exploited contact compliance and promotions kept failing. Promotion failure rate; energy-created flags; the share of finalists typed model-conditional The trust ladder, the energy audit and the model-form rank check (§16); the detectors of §23.16; KILL-CONTACT with CL-2 (§18) Convex compliant models have real artifacts
6 Baseline controllers failed on new morphologies, so every design needed training after all. GATE-REFLEX-02's trend on the corpus; the share of designs reported not-synthesizable Three-outcome reporting (§22.6); KILL-BASELINE; the sampling controller as fallback (BET-27); behaviour-cloning warm starts (§23.10) Novel bodies are hard
7 The agent surface was too large and agents got lost. GATE-TETHER-01 and GATE-TETHER-13 failures; serial turns per accepted answer Clusters of at most seven tools; session.focus; next_actions; robot-docs; the surface A/B of BET-10 (§32, §28) The registry is large even in clusters
8 The swarm closed beads that proved plumbing. Shared close reasons; a gate without a caught negative control; a PASS recorded by the session that implemented the capability The rules against false progress in §38; GATE-GAUNT-01 at every exit; typed close reasons (§0.7, §45) Needs discipline at every exit review
9 Interiors were toy boxes and results did not transfer to real places. Reviewer inspection of generated scenes; the share of dimensions labelled assumed OPEN-HAB-1 norms; hazard registries; scene acceptance; real-place ingestion (§19) Realism is unbounded work
10 Sim-to-real was never tested and claims overreached. Any report without a reality: line The seven claims (§8); GATE-GROUND-01 at every exit; reality: no-claim; card provenance; the no-authorization flags (§12) No hardware is in scope
11 "Certified" became a marketing word while the proof tools stayed immature. Certificates without replay hashes; the word "verified" in any output The wording rule of §12; frob-verify; KILL-LEMMA; the record of whether a certificate changed a decision Depends on the proof siblings maturing, which is upstream work of this program (Appendix F)
12 Single precision failed in large scenes and long runs. GATE-SPARK-05; the share of worlds marked Degraded: ill-conditioned; the guarded-predicate fallback rate Anchored positions, diagonal scaling, guarded predicates with an exact fallback (§35); half precision is not built Near-rigid cards stay outside f32
13 The GPU mandate and the suite's no-FFI doctrine were never reconciled, and work stalled on policy. OPEN-SPARK-1 still open at M2 The annex design (§21.2); the question is put to the owner at M0; M2 has a variant with no GPU (§43.5) Owner decision
14 The Metal gateway's limits throttled the Mac tier. Step-plan launch counts and blocked host time on Metal; GATE-SPARK-04 Packed slabs and one batch per chunk; upstream work item FD-FT-01; KILL-METAL, after which the Mac keeps the world bank, proof, replay and batch-cpu roles (§21) A Metal binding of our own needs an owner decision (OPEN-SPARK-5)
15 The plan itself became the delivery log and stopped being readable. This file growing after conversion to beads §0.7; docs/delivery/ See story 27
16 The ten-fold claim failed on quadruped missions because incumbents already train in minutes. The M0 phase ledger: time to threshold near the published 410 s on one RTX 4090 (FACT, Appendix H); a ceiling under ten for the class §2.3 states the ceilings before anything is built; §2.6 gives the class a range of 3 to 10; GATE-SPARK-21 measures the denominator first; BET-13 fixes the wording for a ratio under 3 and for a ratio between 3 and 10; the partial gate at M3 The quadruped ceiling cannot be engineered away, and the class may leave the claim
17 A composed incumbent layer tied. Ties already on record from the plan-time pilots (a lifted linear program, a dependency graph); the composed arm within a factor of 1.5 at the M3 partial gate BET-14; D-17; KILL-AUGUR-TIE; KILL-FAMILYCERT; the layer ships over that engine for the stratum, and engine work continues only for gaps internal to an engine (§2.6, §39) The engine's share of the product shrinks
18 Rank agreement between rungs was low, so most designs were trained anyway. Verdict flips after finalist training; top-weighted τ under 0.5 in the pilot on incumbent tools The rank-agreement experiment runs first (§2.7); GATE-REFLEX-04, GATE-CORTEX-12, GATE-ATEL-07; discard-only mode; the audit lane and the planted winner; KILL-RANK; training at parity (GATE-CORTEX-05) With most designs trained, the compute ratio is near 1
19 Family policies did not transfer. The pre-funding pilot; return with no adaptation under 70% of specialists; OPEN-CORTEX-1 at its default when M4 opens KILL-FAMILY; inheritance for parameter edits; the baseline and sampling rungs; the variant of M4 with no family policy (§43.7) The class is decided by specialists, and the humanoid range narrows
20 Mixed batches lost to per-family templates. The M1 pilot of padding overhead and bucket count; arm B expressing at least 95% of the mutation corpus The head-to-head with outcomes declared in advance (§17.14); KILL-PHYLUM and KILL-BUCKET; parameter variants within a topology are S and unaffected Two performance differentiators are withdrawn
21 The plan's breadth starved the spine. Forty-three crates, nine milestones and more than four hundred gates spread a swarm thin. Crates that hold only F or M content gain lines while an M1 or M2 exit slips; more than four M items active; a work package funded without its pilot A tier on every mechanism; features that select a tier are off by default (L-12); D-6 and the cap of four; pilots before funding (§0.7); M1 needs three foundations; the program gate; exits defined by demonstrations and not by gate counts (§43) Breadth is the brief, and the cap is enforced by people
22 Qualification was gamed. A campaign with many requests and no close; a receipt field outside the listed set; a denominator that shrank The blinded lane (§24): sealed clusters, pre-committed requests, α_i = α / [i·(i + 1)]; GATE-QUAL-01 under 500 adaptive retries; the firewall gates GATE-QUAL-02 and GATE-SAFE-03; scorecard accounting (GATE-ARENA-07) Whoever holds qual:admin is trusted
23 Certificates were issued for the wrong statement. A bundle whose embedded statement differs from the query; a changed quantifier accepted with consistent hashes D-12; the bundle embeds the canonical bytes of the statement (§34.9); MissionId changes with any quantifier (INV-AUGUR-03); the mutation suites of GATE-LEMMA-03 and GATE-AUGUR-01, -06; KILL-AUGUR-FALSECERT; one false certificate disqualifies an arm (§39) A true certificate of an uninteresting statement still reads as evidence (OPEN-AUGUR-8)
24 A foundation defect surfaced late. A known answer or a baseline that cites a module before its admission test has passed §33.11 records four reported defects as facts to recheck; INT-FSIM-05, -06, -07 and INT-FNP-02; an admission is never inherited; the file-by-file tests run at M0 Unreported defects exist
25 The toolchain train stalled: the siblings could not be brought onto one toolchain, and a merge was blocked. A failing cell in the matrix of INT-TOOLCHAIN-01; two asupersync packages in cargo tree -d One toolchain T chosen at INT-TOOLCHAIN-01, with candidate (b) in reserve; FD-FMCP-01 and FD-ASUP-01 done at M0; KILL-MCP's fallbacks (§33.13); the frob-units escape hatch (§33.12); check-deps Four nightlies and one stable release are the starting state (FACT, §33.13)
26 Calibration data never arrived. No dataset admitted when M5 opens; OPEN-GROUND-1 and OPEN-GROUND-2 at their defaults Reality is an import lane (§30): a synthetic rehearsal, frozen predictions, a published-anchor comparison at M3, bench packages that may be sourced from M0; the resting state is no-claim and blocks nothing The Reality claim stays empty
27 The document itself became unreadable. A threshold stated two ways; an identifier defined twice; a reader who cannot tell the spine from the frontier The reading paths of §0.4; tier tags; §40 as the only authority for a threshold; registries generated from the plan's tables; the plan stops growing at conversion to beads The plan is long by design

Three clusters deserve a sentence each. Stories 16 to 20 are the thesis failing lever by lever, and §2 already says that no single lever delivers the result; what the plan adds is that each lever has its own early experiment and a fallback that ships under its own name. Stories 22 to 24 are the evidence failing, and they share a remedy: the party that proposes a result never checks it. Stories 21 and 25 to 27 are the program failing under its own weight, and their remedy is structural: M1 is small, the upper tiers are off by default, and the document delegates progress to beads and registries.

41.2 Every gate passed and the claim still failed

A gate measures a mechanism. The ten-fold claim is about an outcome. The reasons below could hold with every convergence gate green, so each is tied to a measurement that is not a mechanism gate. They are ranked by how early the signal is available.

Rank Reason Earliest signal Where the plan answers it
1 Nothing confirmable existed: no metric, no incumbent arm, no neutral check. No incumbent phase measurement on record at M0 exit §2.1 defines the metric; §39 the arms and the adjudicator; GATE-SPARK-21 is an M0 exit condition (§43.3)
2 Amdahl. Incumbent training takes minutes, and the agent's latency is common to both arms. Training under about 90% of a measured incumbent cycle in the M0 ledger The ceilings of §2.3; many designs per turn (§17); the phase ledger of §39
3 The cheap rung reorders designs, so most are trained after all, on a training rung that is only at parity. Worst on stairs, rubble and bipeds, where the multiplier would be largest. Verdict flips after finalist training; the trained fraction f above about 1% BET-17; the rank-agreement gates; discard-only; classes expected to be hard are sampled on purpose (§23, §28)
4 The referee could not run interior or tracked scenarios, so results stayed provisional. The share of standard-battery scenarios the referee completes at M2 (GATE-FID-03) The transactional step with witness migration (§16.5); the strict profile as adjudicator; BET-34
5 Common-mode error. Every tier shared generic and assumed cards, so tiers agreed with each other and accepted decisions failed neutral adjudication. The share of card fields that are assumed or generic in benchmark designs Card provenance on every report (§15); the published-anchor comparison at M3 (§30); an evaluator neither arm trained in (§39)
6 Structure helped agents only slightly. The ratio of restricted mean times in the surface A/B (GATE-ATEL-03), which needs an effect size and not merely a win BET-10's threshold of 1.5 on at least ten briefs; the verbs that showed no effect lose their speed claim

41.3 Risk register

Severity is High when the risk can invalidate the thesis, the architecture or a milestone exit; Medium when it costs a capability or a claim; Low when it costs convenience. RISK-01 to RISK-20 keep their version 0.2 meaning, except RISK-02 and RISK-20, which are restated because sibling work is this program's work (§33.8). Their mitigations are corrected where this version changed the mechanism, and each now has an earliest signal. RISK-21 onward are new. The owner column names a role, not a person.

ID Risk Severity Earliest signal Mitigation Owner
RISK-01 FrankenSim API churn in fs-mbd and the Component trait High Adapter changes per pin move; BET-04's breakage share Airlock, pin, compatibility train; upstream work item FD-FSIM-08; KILL-FSIM with the worker process first (§33) Airlock lead
RISK-02 The toolchain train costs more than M0 allows, or breaks a sibling. One toolchain T serves the whole build graph, and the siblings start apart: four nightlies and one stable release are in play, and fastmcp_rust declares a minimum of 1.100 where FrankenSim pins a 1.99 nightly (FACT, §33.13) High A failing cell in the matrix of INT-TOOLCHAIN-01; FD-FMCP-01 still open at the M0 exit review T is chosen in the order of §33.13, with candidate (b) if FrankenSim cannot yet build on (a); FD-FMCP-01 at P0 brings fastmcp_rust onto T; T then moves only by a toolchain train followed by the admission and parity gates; KILL-MCP's fallbacks Build lead
RISK-03 Two asupersync versions in one build. Three siblings still pin 0.5.0 (FACT, §33.13) High cargo tree -d at INT-ASUP-01 FD-ASUP-01 at P0 aligns the consumed siblings on one published version; check-deps forbids 0.5.0 and the frankentui executor feature; those siblings never enter a graph; KILL-MCP's first fallback if a surface still brings a second package Build lead
RISK-04 Bit equality across backends is unattainable on a device family Medium GATE-SPARK-01's record of each family's best attainable class KILL-D1; class D3 with the decision-level test of §35.4; paired statistics refused under an uncontrolled class; the property claimed is batch-composition invariance (GATE-SPARK-15), with bit equality only where class D1 is attained Spark lead
RISK-05 The convex contact model's creep misleads wheel and stair results High Creep and slip quantities in the fidelity ledger; model-conditional finalists The four-dimensional cone and joint rows; CL-2; the model-form rank check; the hard-contact law as an arm F; KILL-CONTACT (§18) Traction lead
RISK-06 Derived kernels are slower than hand-written ones Medium The M2 profile against BET-01's bound of 1.3 KILL-KIR; specialization only for survivors, since its ceiling on an incumbent trace is about 1.2 (§21.18) Spark lead
RISK-07 FrankenSymPy budgets block derivations or certificates, by expression swell on a 29-joint humanoid Medium Derivation time and peak memory per kernel body at INT-FSYM-01 Derive per kernel body and per limb, never per robot; BET-11; KILL-LEMMA Lemma lead
RISK-08 The Metal gateway is synchronous, takes at most 31 buffer arguments, binds at offset zero and compiles from source only (FACT, §21.9) Medium Launch counts and blocked host time per chunk on Metal Packed slabs and offset tables; one batch per chunk; upstream work item FD-FT-01; KILL-METAL. The earlier fallback of a direct binding is withdrawn: a Metal binding of our own needs an owner decision (OPEN-SPARK-5) Spark lead
RISK-09 trj is heavily loaded, so measurements are noisy and compiles slow Medium The spread of A/A campaigns; the recorded host load in disclosure blocks The binary kernel cache; interleaved runs; admission by paired lower bound; the A/A known answer of GATE-SPARK-19 Performance lead
RISK-10 No compute envelope is approved, so the performance gates, the rank-agreement experiment and pretraining cannot run as specified High OPEN-SPARK-2 at class E0 when M1 opens The classes E0 to E3 are proposed at M0 (§36.14); every package above E0 names its budget (§44.2); variants of M2 and M4 that fit E0 Owner
RISK-11 Asset licences restrict what can ship Medium A pack whose licence join is not redistributable Procedural first; licence manifests enforced at pack time; GATE-SAFE-05 Habitat lead
RISK-12 A scan of a private place leaks through a still, a fixture or policy weights High A derived artifact without the private mark Inheritance of the private mark (§37); the export flag; scene.purge; GATE-SAFE-04; weights inherit by default (OPEN-SAFE-2) Chronicle lead
RISK-13 Reference robot imports hide lossy contact mappings Medium Fields missing from a loss report in the field-coverage diff Loss reports (GATE-SKEL-01); CL-M labelled parity-only Skeleton lead
RISK-14 The design corpus is tuned to the analyses Medium Corpus labels edited after an analysis changed Labels frozen before tuning; a held-out third; potency controls in GATE-ATEL-01 Arena lead
RISK-15 Agents optimize the scorecard instead of the robot, including by moving failures out of the denominator Medium Scorecard columns that do not sum to the battery size; a battery whose identity changed Promotion, detectors, held-out scenes, tail metrics; GATE-ARENA-07; numerical faults kept apart from physical failures (GATE-CHRON-08) Atelier lead
RISK-16 Lean work needs a large-memory Linux host Low The closure size measured at INT-FLN-01 Measure first (OPEN-LEMMA-1); specifications in elementary form (OPEN-LEMMA-2) Lemma lead
RISK-17 Baseline controllers mask design flaws or create false ones Medium Disagreement between estimated-state and privileged-state runs; controller-sensitive flags Three-outcome reporting; the comparator of GATE-REFLEX-03; rank agreement before a rung may eliminate Reflex lead
RISK-18 Crate scope caps are exceeded early Medium A crate at 115% of its cap in check-contracts The scope conversation at 115%; an ADR raises the cap or moves a mechanism; no silent growth Project lead
RISK-19 The viewer drifts outside FrankenThreeD's admitted subset. FrankenThreeD has no single-file packaging, so the HTML export is ours (FACT, §33.15) Low INT-F3D-01 Plain Three.js is the fallback and is always built Viewer lead
RISK-20 Upstream work costs more than planned, or is done in the wrong order: an upstream work item that a switch-over needs is still open when its milestone exits Medium An upstream work item older than two milestones with no change of state; a P0 item still open at the M0 exit review Every upstream work item has an interim posture that ships and a switch-over rule; no milestone waits on one landing; P0 items are done at M0 and the rest are ordered by priority in this program's queue Project lead
RISK-21 The fs-qty coupling ties the whole build graph to nightlies on which an incomplete compiler feature still builds one crate High The fs-qty row of the INT-TOOLCHAIN-01 matrix after a pin move or a toolchain train Quantities reach every crate through frob_core::qty; the preferred fix is an upstream change in FrankenSim (FD-FSIM-15, FD-FSIM-31); the frob-units escape hatch as the fallback (§33.12) Build lead
RISK-22 The FrankenSim closure makes builds slow and makes the lift expensive: the M1 set compiles 65 crates and about 2.06 million lines (FACT, §33.2) High Cold check time and peak memory at INT-FSIM-01 against the machine envelope Feature groups in the airlock; the worker process before any lift (INT-FSIM-18); OPEN-SUITE-5 Airlock lead
RISK-23 Dirty or off-pin sibling trees make a receipt unrepeatable Medium A drift class other than on-pin in check-stack at a gate run The resolution receipt hashes bytes; no gate records a PASS on a dirty tree (OPEN-SUITE-3); the compatibility train Build lead
RISK-24 A reported foundation defect is relied on before it is rechecked (the PPO update, the planar drive, the stride convention, fixed contact witnesses) High A known answer, an oracle or a baseline that cites one of those modules INT-FSIM-05, -06, -07, INT-FNP-02; the independent formula; our own PPO passes the same three probes first; witness migration above the airlock (§33.11) Airlock lead
RISK-25 The denominator of the ten-fold ratio is wrong: incumbents are faster, or their loop is shorter, than the composite of §2.2 High The M0 phase ledger GATE-SPARK-21 before any mechanism is funded against the rival; the ceiling-first rule (§0.7); pinned comparator revisions (OPEN-PERF-2) Gauntlet lead
RISK-26 A short robust program over an incumbent engine reaches the same accepted answers in comparable time High The composed arm within a factor of 1.5 on a stratum at the M3 partial gate BET-14; KILL-AUGUR-TIE; the layer ships for that stratum; research budget moves to the first mission the rival cannot resolve Project lead
RISK-27 Rank agreement between rungs is too low for cheap rungs to eliminate designs High τ under 0.5 at the lower bound in the pilot; verdict flips after training GATE-REFLEX-04, GATE-CORTEX-12, GATE-ATEL-07; the modes of §28.10 (discard-only from 0.5, uninformative below it or with no record); the audit lane; KILL-RANK, with the lost factor recorded in §39 Atelier lead
RISK-28 Family policies do not transfer, lose plasticity along lineages, or their pretraining is never approved High OPEN-CORTEX-1 at its default; the pre-funding pilot; the ten-edit chain of GATE-CORTEX-13 KILL-FAMILY; KILL-INHERIT; scheduled resets; the variant of M4 with no family policy Cortex lead
RISK-29 Mixed batches lose to per-family templates or to an incumbent's mixed batch Medium The M1 padding and bucket pilot; the share of the mutation corpus arm B expresses The head-to-head (§17.14); KILL-PHYLUM; KILL-BUCKET Phylum lead
RISK-30 Engine throughput or training time lands below the parity band High A paired lower bound under 0.67 of the incumbent; GATE-CORTEX-05 above 1.25 times the incumbent KILL-PARITY; KILL-LEARNKERN; the profile decides where effort goes Performance lead
RISK-31 The referee cannot complete the scenes where decisions are made: the upstream sustained solve admits at most 21 contacts and keeps fixed witnesses (FACT, §33.2) High Referee coverage per robot class under 80% at GATE-FID-03 The transactional step with witness migration; the strict profile as named adjudicator; upstream work items FD-FSIM-12 and -13; BET-34 Kinesis lead
RISK-32 Common-mode model error: tiers agree with each other and disagree with reality, because they share cards High The share of assumed and generic card fields in benchmark designs Provenance on every card field; the report line with that share; the published-anchor comparison; Ground; a neutral evaluator in §39 Sinew lead
RISK-33 Breadth starves the spine High Lines added to Frontier-only and Moonshot-only crates while a critical-path exit slips D-6 and the cap of four; L-12; pilots before funding; the critical path of §43.1; the schedule gate (BET-12, §40.5) Project lead
RISK-34 Qualification is gamed by adaptive retries or by a leak from sealed worlds High A receipt field outside the listed set; requests without a close GATE-QUAL-01, -02; GATE-SAFE-03; the level schedule α_i; replay of a campaign by frob-verify (GATE-QUAL-03) Arena lead
RISK-35 A certificate is issued for a statement other than the one asked High A mutated quantifier, authority or comparator accepted by the checker D-12; canonical statement bytes in the bundle; GATE-LEMMA-03; GATE-AUGUR-01; KILL-AUGUR-FALSECERT; unreviewed bundles say so (OPEN-AUGUR-8) Lemma lead
RISK-36 The proposer and the checker share a defect High A source file shared between frob-cert and a proposer; a checker dependency beyond the standard library ADR-WS-02; L-9; GATE-WS-03; GATE-AUGUR-06; a second checker if one is not enough (OPEN-LEMMA-4) Lemma lead
RISK-37 A screen discards the winner High The audit lane finds a discarded design in the true top band; a planted winner is missing from the finalists The screening audit of §26.10 (GATE-NEMESIS-07), and GATE-ATEL-09: no rung is trusted without a passed audit; a rung is uninformative where rank agreement is unmeasured; KILL-STATIC Atelier lead
RISK-38 An incomplete memo key serves a stale verdict High A shadow-recompute mismatch The shadow recompute and its gate (GATE-ATEL-11, -12); INT-FSIM-16; polarity rules in revalidation; KILL-REUSE Atelier lead
RISK-39 Retention deletes the interval that explains a decision Medium A citation of a collected object is refused; an evidence.trace closure that does not resolve Decision-relevant chunks are pinned; tombstones; GATE-CHRON-12; OPEN-CHRON-4 Chronicle lead
RISK-40 Contact capacity biases a comparison against the morphology with more contacts Medium Degraded shares that differ by class; capacity-biased labels The rule of §18.11; GATE-KIN-07; refusal instead of silent truncation; capacities in every disclosure block Traction lead
RISK-41 A scene looks plausible and cannot support a robot Medium The shares of unresolved and unintended impossible scenes (GATE-HAB-02) Scene acceptance (GATE-HAB-04); feasibility tags; clearance complexes (§19) Habitat lead
RISK-42 A model fits nominal motion for the wrong physical reason Medium Speed matches while current draw and contact work disagree in the energy ledger The identifiability analysis A-25 and GATE-GROUND-03; the wrong-reason label; the energy ledger evaluated on real logs (§30) Ground lead
RISK-43 Calibration data never arrives Medium No admitted dataset when M5 opens Import lanes with a recorded no-claim; the synthetic rehearsal; bench packages sourced from M0 (§30.17) Owner
RISK-44 Adaptation or tuning leaks into the final evaluation High A policy or controller identity that changed between discovery and confirmation; a training scene in an evaluation The scene-split and design-split checks (GATE-ARENA-02, GATE-HAB-14); identities frozen in the qualification request Arena lead
RISK-45 An optimization changes unrelated semantics: the kernel is faster while contact counts or sensor rates fall Medium Throughput rises while a count in the disclosure block moves Digest identity for rewrites that claim bit equality; the decision-level test for the rest; the harness of GATE-SPARK-19 Performance lead
RISK-46 Scaling across two cards or two machines vanishes under transfer cost, or under vision workloads Medium Strong scaling under 1.25 at GATE-SPARK-20; the fleet pilot KILL-SHARD; KILL-FLEET; the two cards run as independent lanes; only seeds, weights and receipts cross (§21.17) Spark lead
RISK-47 Search or gradients exploit a contact-order or model-form artifact Medium A ranking that flips under another admissible law; a derivative used outside its validity label Derivative validity labels (D-15); the model-form checks (GATE-FID-05, GATE-ATEL-10); KILL-FDGRAD Kinesis lead
RISK-48 A driver, system or binding update changes kernel results Medium A fingerprint change; a failed spark.check The fingerprint gate; --require-current-check; the kernel cache keyed by fingerprint; pinned bindings Spark lead
RISK-49 Imported text carries instructions to an agent Medium A hostile string outside an untrusted-marked field The untrusted annotation; GATE-SAFE-02; the poisoned-import arm of GATE-TETHER-13 Tether lead
RISK-50 Attribution names a cause where none is stable Medium The placebo flip rate on reference failures Abstention (GATE-AUTOPSY-05); double precision; KILL-AUTOPSY Autopsy lead
RISK-51 The tournament cannot confirm a true ratio of ten, for lack of power or because unfinished missions cap the ratio at 1/q High The power analysis before the suite is opened; the share of missions unresolved at the deadline in the M3 partial gate A pooled ratio whose pre-analysis is recorded before the suite is opened (§39.7); a finite-suite result at 24 families and a population claim only at 32 or more (§39.20); completion treated as a first-order goal Gauntlet lead
RISK-52 No neutral party or independent evaluator is named, or the repository stays private, so nobody outside can confirm the result Medium OPEN-PROG-1 and OPEN-PROG-2 at their defaults when the pins are frozen for M7 The replication kit; frob-verify as a standalone binary; the label self-adjudicated on any ratio measured without a neutral party (§42.2) Owner
RISK-53 Owner decisions arrive after the gates they block High An OPEN row at its default past its deadline Fail-closed defaults; each question is asked one milestone early (§42.1); variants that need no decision (§43.12) Owner
RISK-54 The plan and the registries drift apart Medium An identifier defined twice; a chapter threshold that differs from §40 §40 governs; registries and status tables are generated; the delivery log is not in this file Project lead
RISK-55 An upstream change collides with other agents working in the same sibling repository: overlapping edits to one file, a head that moves under a half-made change, or a reservation conflict that stalls the item Medium A file-reservation conflict in Agent Mail on a sibling path; an upstream work item whose sibling bead changes state without its bead here File reservations through Agent Mail before any edit in a sibling; the sibling's own AGENTS.md and coordination rules; small additive changes that land on the sibling's main through its own gates; the interim posture ships meanwhile (§33.8) Project lead

41.4 How the register is used

  • Review. The register is read at every milestone exit by the fresh-context session that records the exit (§43.2). For each row the session records whether the earliest signal has fired.
  • Escalation. A fired signal ends in one of three recorded outcomes: a kill gate decided, an ADR that changes a mechanism or a scope, or a written reason why neither applies. A fired signal with no record is a defect of the exit review.
  • Growth. A new risk continues the series. A risk that can no longer occur is tombstoned with the gate that retired it and is not renumbered.
  • No risk is mitigated by a hope. A mitigation column names a mechanism with a gate, a fallback named in advance, or an owner decision with a fail-closed default. An upstream work item is never a mitigation by itself; its interim posture is (RISK-20).

41.5 Four risks that follow from late foundation facts

What it is. S Four rows for the register of §41.3, in its columns. Each arises from a fact recorded in §23, §33, §34 or §39, each has an earliest signal that an existing check already produces, and none is covered by a row that is already in the register. Identifiers are assigned with the rest of the series.

Risk Severity Earliest signal Mitigation Owner
A dependency feature changes canonical bytes: a sibling that enters the build graph switches the JSON library to insertion-ordered maps or to another number representation, and digests of unchanged artifacts move High xtask check-deps reports a unified feature set of the JSON library that differs from the stack lock; a golden digest changes with no change to its artifact Canonical bytes come only from this project's writer; the four-way feature build of §34; the stack lock records the feature set Workspace lead
An exact version pin in a sibling blocks an oracle: two siblings require different exact versions of one package, so they cannot share a build graph Medium Dependency resolution reports two exact requirements on one package; the admission gate of the oracle cannot build The oracle runs as a worker process in its own workspace (§33.14); the pin move is an upstream work item (FD-FTX-01, FD-F3D-01) Suite lead
A sampler has correct marginals and a wrong joint law, so the likelihood ratio is computed for a variable that was not sampled and exploration is correlated across channels High A pairwise sign-agreement frequency outside ½ ± 0.005 in the sampler battery; a learning curve that changes when channels are reordered Rule P-12 and its gate (§23); counter-based draws keyed per channel; no sibling sampler is linked Cortex lead
A rare slow mission is absent from the sealed sample, and a resampling interval certifies a ratio the population does not have High The pre-analysis of §39 reports a family count below the count its registered bound needs; every sealed mission of an arm finishes near its fastest time The bounded paired contrast; the two result types of §39; a stratum below the necessary count reports a finite-suite result Gauntlet lead

DESIGN: the detector of each row is exercised by a planted instance in the negative-control registry (§38), so the signal is known to fire: a dummy dependency that enables the two library features; a second exact pin on one package; the planted linear-phase sampler; the rare-tail arm of the ten-fold pre-analysis.

Counterexample to the shortcut "a passing build means the pins are compatible": a build that never enables the oracle's feature flag resolves, and the conflict appears only when the flag is first turned on at the oracle's milestone. The resolution check therefore runs with every optional feature group enabled.

GATE-WS-07 Known answer. Each of the four planted instances raises its named signal in 100 of 100 runs; xtask check-deps resolves the graph with every feature group enabled and fails on the planted second pin; no row of the register lacks a planted instance. M0 for the two build rows, M2 for the sampler row, M3 for the suite row.