Open questions
7,283 words4 subsections2 tablesPlan version 1.1
On this page4
An open question is a decision the plan has not taken, written so that not taking it is safe. This chapter states the rule every question obeys, lists the questions only the owner can answer, and then registers every open question of the plan by subsystem. Labels: every row is OPEN; a number in a default column is a DESIGN default or a TARGET, never a measurement.
42.1 The decision rule
Every OPEN has an owner, a deadline expressed as the gate or milestone it blocks, a fail-closed default, and the evidence that would decide it. Nothing is decided by silence: at its deadline an undecided question takes its default, and the default is recorded as an ADR. Five clauses make the rule operational.
- A default removes a claim or a capability. It never adds one. "GPU results are labelled exploratory", "no
pretraining", "
reality: no-claim" and "refuse" are defaults. "Assume the catalogue price" is not. - A question is asked one milestone before the gate it blocks. The owner-input line of each milestone in §43 lists the questions due. A question that reaches its deadline at its default is reported in the exit review with the capability it removed.
- Evidence decides where evidence exists. A question whose row names a gate, a profile or a pilot is decided by that measurement and not by preference. Only the questions of §42.2 are decided by the owner's judgement.
- A closed question is tombstoned, not reused. Its identifier stays in the register with the ADR that closed it.
- This register adopts the identifiers the chapters defined. A chapter's text governs the mechanism behind a question, and §40 governs any threshold a question touches. Where a chapter named no owner, the lead of its subsystem owns the question.
The register holds 147 questions: 141 raised in §12 to §37, of which four are closed, and six at program level. OPEN-PROG-1 and OPEN-GAUNT-1 are carried from version 0.2. OPEN-PROG-2 to OPEN-PROG-5 are new. The questions that §38 and §39 raise are adopted under the same rule with the owners and defaults those chapters state: OPEN-GAUNT-2 to -8 and OPEN-TENFOLD-3 to -9. OPEN-TENFOLD-1 and -2 are OPEN-PROG-2. With these fourteen the register holds 161.
42.2 Questions for the owner
These are the decisions that no measurement inside the program can take. Each row gives the default that holds until the owner answers, what that default costs, and the latest milestone at which an answer still changes the outcome.
| ID | Question | Default if undecided | What the default costs | Needed by |
|---|---|---|---|---|
| OPEN-SPARK-1 | Ratify ADR-SPARK-01: GPU backends live in annex workspaces with registered FFI capsules, outside the Franken-only core | GPU results are labelled exploratory | No Performance or Parity claim rests on a device result; M2 exits in its no-GPU variant (§43.5) | M0; blocks M2 exit |
| OPEN-SPARK-2 | The compute envelope: ratify or amend the classes E0 to E3 of §36.14 (E1 a named gate measurement, E2 a design campaign, E3 pretraining of one family policy) | E0: 16 GiB, 8 cores, one hour, one device | The throughput and scaling gates, the head-to-head and every campaign cannot run as specified | M0; blocks GATE-SPARK-03, -04, -20, -21 |
| OPEN-PROG-4 | Approval to run the rank-agreement experiment: about forty per-design trainings in one morphology class, about 5 device-hours where the specialists of §23 are reused and about 45 otherwise (§2.7, §28.10, §36.14) | Not run above E0; every cheap rung is uninformative, so it neither selects nor discards, and results are labelled as unranked |
The decisive early experiment of the program is late, and lever 2 of §2.4 stays a hypothesis | M1; the pilot on incumbent tools is due at M3 |
| OPEN-PHYLUM-3 | The compute envelope for the mixed-batch head-to-head and for pretraining populations | The one-device, one-hour rule, which admits the pilot and not the full experiment | KILL-PHYLUM is decided on the pilot alone | M2 |
| OPEN-CORTEX-1 | The compute envelope for pretraining family policies. The proposal is one class (quadruped), 200 designs, at most 60 GPU-hours of pretraining and 40 for specialists, on trj |
No pretraining | No family policy exists; M4 exits in its variant with specialists and inheritance (§43.7) | M3; blocks GATE-CORTEX-11 |
| OPEN-PROG-2 | The adjudicating simulator and the neutral party for the ten-fold test: which evaluator, independent of both arms, runs the acceptance batteries; and who seals the suite, holds the receipts and releases them after both arms close (§39) | An incumbent CPU engine at a pinned version that neither arm trains in, run by a fresh-context session with no write access to either arm; every ratio so measured is labelled self-adjudicated |
The words "independently accepted" are not used for the result, and the partial gate at M3 is a rehearsal | M2; before any sealed world family exists |
| OPEN-PROG-3 | Whether the Gymnasium-compatible adapter ships as a supported, published binding, or exists only as the rival's access path in the ten-fold test | Built and gated (GATE-CORTEX-16) for the test and for conformance; not a supported public surface; no interpreter in any frob binary |
External learning stacks have no supported route into the environment; if the adapter fails its gate the rival drives whole rollouts through the job interface (KILL-GYMADAPT) | M3 |
| OPEN-AUGUR-4 | Whether a quantifier-elimination or SMT engine is admitted as a production dependency, or only as a comparator outside the product | Comparator only; the product uses in-tree elimination for small linear systems | Some family cells stay unresolved that a general solver would close | M3; KILL-AUGUR-TIE depends on it |
| OPEN-GAUNT-1 | Admission of real datasets: which real-robot dataset, if any, enters the Reality lane first, with what licence and provenance. OPEN-GROUND-1 is the engineering half of this question | reality: no-claim everywhere; the second-simulator stand-in is labelled synthetic |
No Reality claim; GATE-GROUND-10 stays an import lane | M5 |
| OPEN-GROUND-2 | Whether any bench hardware of §30.17 is acquired | None | Bench packages A to F never run | Sourcing may start at M0 |
| OPEN-PROG-1 | Repository visibility and the licence file. The question now has a second half: who outside the program can replicate the ten-fold result | Private; the suite's licence file; the replication kit and the frob-verify binary are the only artifacts prepared for a third party |
A private repository cannot be independently confirmed (RISK-52) | First push; again before the pins are frozen for M7 |
| OPEN-PROG-5 | The order in which admitted Moonshot items become active under the cap of four (D-6) | None is active before its pilot passes; then the order of §43.9 and §43.11 | None on the critical path | M5 |
| OPEN-ARENA-3 | Who holds qual:admin, and the size and composition of the sealed world families |
The owner alone opens and closes campaigns; one sealed family per task family, sized for 20 requests at 256 clusters | Nothing is called qualified until a family exists | M2; blocks GATE-QUAL-01 |
| OPEN-SHIELD-2 | The calibration level α and the per-episode violation budget of runtime shields | α = 10⁻³ and a budget of 10⁻³ per episode | None beyond the default itself | M3; blocks GATE-SHIELD-03, -04 |
| OPEN-SPARK-5 | Whether a Metal binding of our own may be built before the gateway's upstream work item (FD-FT-01) lands | No; the gateway is changed upstream, and until then Spark stays inside its limits and accepts KILL-METAL's fallback | The Mac may be a development and replay tier only | M2 |
| OPEN-SUITE-2 | Decided by the owner on 2026-11-22; kept as a recorded decision. The question was whether the core moves to a nightly at or above 1.100 so that frob-mcp may join the core graph |
Decision: the whole build graph uses one toolchain T, chosen at INT-TOOLCHAIN-01 in the order of §33.13; fastmcp_rust is brought onto T by FD-FMCP-01; frob-mcp is a member of the core graph and runs verbs in process |
The upstream work of FD-FMCP-01 and FD-ASUP-01 at M0; KILL-MCP's fallbacks if INT-FMCP-01 cannot pass | Decided; confirmed at M0 by INT-TOOLCHAIN-01 and INT-FMCP-01 |
| OPEN-SUITE-3, OPEN-SUITE-5 | Whether a dirty sibling checkout is acceptable for development builds; the budget for the cold build of the M1 closure | Yes for development, with the tree hash in the receipt and no PASS recorded; the machine envelope | A gate run waits for a clean tree; KILL-FSIM fires if the cold check exceeds the envelope | M0 |
| OPEN-SINEW-1, OPEN-SENS-4, OPEN-TRAC-3 | Which real actuator parts, sensor cards and film or soil tables enter the catalogues, and under what data licences | Generic classes and ranges labelled assumed |
Every result that depends on them stays Estimated, and realism and Reality claims are refused |
M4 |
| OPEN-HAB-1, OPEN-HAB-4, OPEN-SKEL-2, OPEN-FOUNDRY-2 | One cited source each for dimensional norms, retrofit prices and legality, card prices and the parts catalogue | Generic ranges and prices labelled assumed; constraints marked unchecked |
No claim about realism or cost in a published report; --strict-data refuses a cost verdict |
M3 for norms; M5 for prices |
| OPEN-NEMESIS-3, OPEN-AUGUR-10 | Compute for a certified failure rate of 10⁻⁶, and for the Moonshot slices of §25.17 to §25.20 | Certify to 10⁻⁵ and report 10⁻⁶ as Estimated; no slice is funded before its pilot passes |
The lowest certified rate is 10⁻⁵ | M3; M6 |
| OPEN-SAFE-2, OPEN-SAFE-3, OPEN-SAFE-4, OPEN-CHRON-4 | Privacy inheritance for weights; sandboxed custom reward terms; retention periods and store budgets | Weights inherit mark and licence; custom terms are not admitted; logs and keys kept 30 days, failure captures 30 days in 64 GB, retired confirmation clusters sealed indefinitely | None beyond the defaults | M2 to M4 |
| OPEN-TETHER-5 | Whether the peer link between the two machines earns its upkeep | Standalone machines | The fleet scheduler assigns jobs by the role table only | M4 |
42.3 The register by subsystem
One row per question. The default is the fail-closed state that holds at the deadline. The last column gives the gate or milestone the question blocks, or the measurement that decides it.
| ID | Question | Default if undecided | Owner | Blocks, or decided by |
|---|---|---|---|---|
| Lemma (§12) | ||||
| OPEN-LEMMA-1 | Memory and time to re-check one theorem's closure with FrankenLean | Measure before any claim | Lemma lead | INT-FLN-01 |
| OPEN-LEMMA-2 | Whether the reflectors' soundness theorems have closures that avoid the blocked Mathlib modules | Specifications are stated in elementary form, without analysis modules | Lemma lead | GATE-LEMMA-05 |
| OPEN-LEMMA-3 | The cost of kernel evaluation on exact rationals at specimen size | Reflection is limited to specimens that fit the budget | Lemma lead | GATE-LEMMA-05 |
| OPEN-LEMMA-4 | Whether one auditor is enough, or a family certificate needs a second independent checker (fs-checker, or FrankenSymPy's capsule consumer for polynomial kinds) |
One auditor with the mutation suite of GATE-LEMMA-03 | Lemma lead | GATE-LEMMA-04 at M4 |
| OPEN-LEMMA-5 | Whether certificates change any design decision | Counted in the phase ledger of the ten-fold test; if the count is zero, Lemma is evidence quality only and stays off the critical path | Lemma lead | The M7 tournament |
| OPEN-LEMMA-6 | Whether the Mathlib module that holds the orbit-counting lemma of T-24 re-checks in FrankenLean at the pinned commit | Cited only after a recorded re-check; until then the count is Tested |
Lemma lead | GATE-LEMMA-02 |
| Marrow (§13) | ||||
| OPEN-MARROW-1 | Whether to canonicalize quaternion sign in stored state | No; state stays continuous and observations use sign-invariant features | Marrow lead | GATE-MARROW-01 |
| OPEN-MARROW-2 | Whether exact field arithmetic extends to radial designs with n above 12 | No; such designs are symmetric by construction, and imported ones use the tolerance route with a Tested label |
Marrow lead | Nothing |
| OPEN-MARROW-3 | Whether the exact fallback of §13.7 may use 64-bit integers where a backend offers them | 32-bit limbs everywhere, so the three backends run the same integer program | Marrow lead | GATE-MARROW-05 |
| Skeleton (§14) | ||||
| OPEN-SKEL-1 | A text syntax for designs | Closed by ADR-SKEL-02: JSON is canonical and the S-expression view is lossless and optional | — | Closed; tombstoned |
| OPEN-SKEL-2 | Where card prices come from, and under what licence | Prices are assumed, the cost budget is advisory, and --strict-data refuses a cost verdict |
Project lead | No gate before the build packet of §31 |
| OPEN-SKEL-3 | How a task with continuous world parameters declares the finite family that preflight stage 8 searches | The task's own randomization grid, recorded in the witness | Arena lead | Before stage 8 is funded |
| OPEN-SKEL-4 | Whether the lattice fill needs anisotropy |
Isotropic fraction only, with the assumption printed in the check report | Foundry lead | Nothing before §31 |
| Sinew (§15) | ||||
| OPEN-SINEW-1 | Which real actuator parts ship in the catalogue, and under what data licence | Generic classes only | Project lead | Nothing before M4 |
| OPEN-SINEW-2 | The default Stribeck shape and stiction velocity ε on batched tiers | The rational shape and ε = 10⁻³ rad/s, both overridable by a card | Sinew lead | GATE-SINEW-04 |
| OPEN-SINEW-3 | Whether iron loss is on by default at L2 | On when the card gives coefficients; otherwise zero, with the flag iron loss not modelled on every result |
Sinew lead | GATE-SINEW-05 |
| OPEN-SINEW-4 | Whether the second polarization pair on the referee is composed from existing FrankenSim circuit elements or needs an upstream change | Open the upstream work item (FD-FSIM-21); an in-house f64 reference until it lands |
Airlock lead | The admission test for fs-phs |
| Kinesis (§16) | ||||
| OPEN-KIN-1 | The default physics step and Newton iteration budget | 2 ms; 4 iterations with warm start | Kinesis lead | The fidelity–throughput frontier at M2 |
| OPEN-KIN-2 | Whether sleeping and islands are worth their complexity for single-robot worlds on lockstep tiers | No; islands are always formed under a transactional profile | Kinesis lead | The M2 profile |
| OPEN-KIN-3 | Final contact and row capacities per workload | The table of §16.6; overflow is flagged and the caller chooses | Kinesis lead | GATE-KIN-07 |
| OPEN-KIN-4 | Which law the strict profile runs by default once CL-H is admitted |
CL-1 with located events; CL-H as a named variant | Kinesis lead | Nothing; decided with GATE-TRAC-09 |
| OPEN-KIN-5 | L_max, E_max and the retry budget of the transactional step | 16, 64 and 3; exhaustion refuses | Kinesis lead | The refusal rate on the standard battery at M1 |
| OPEN-KIN-6 | The created-energy bound per law and step | 1% of actuator work per episode | Kinesis lead | Re-baselined once with GATE-FID-01 |
| Phylum (§17) | ||||
| OPEN-PHYLUM-1 | The registered default bucket set and the padding-waste limit | {12, 18, 24, 36, 48, 64} and 25%; beyond that the planner refuses (FROB-REF-741) |
Phylum lead | The M1 pilot of §17.14 |
| OPEN-PHYLUM-2 | Run length per model, 16 or 32 worlds | 32 on CUDA; the device's reported execution width on Metal | Phylum lead | The M2 profile |
| OPEN-PHYLUM-3 | The compute envelope for the head-to-head and for pretraining populations | The one-device, one-hour rule, which admits the pilot and not the full experiment | Owner | GATE-PHYLUM-03 |
| OPEN-PHYLUM-4 | Which incumbents and versions fill arms C and D of the head-to-head | None; the arms report not run |
Gauntlet lead | Frozen with the rival audit of §39 before any run |
| OPEN-PHYLUM-5 | Whether contact capacity needs its own bucket axis | No; one axis on degrees of freedom, with capacities from the largest member | Phylum lead | Overflow and padding statistics at M2 |
| Traction (§18) | ||||
| OPEN-TRAC-1 | Dense bricks or a sparse brick tree for interior scenes at 1 cm | Dense bricks with a coarse outer level | Traction lead | Measured memory at M3 |
| OPEN-TRAC-2 | The source of r_eff: sample geometry, a pressure assumption per material, or a card field | 2a/3 from sample geometry, overridden by a card | Traction lead | GATE-TRAC-04 |
| OPEN-TRAC-3 | Provenance for film and soil cards: which measured tables are admitted | Generic ranges labelled assumed, which keep every result Estimated |
Project lead | Claims of realism for wet floors and soft ground, not validity |
| OPEN-TRAC-4 | The admission bound on scaled κ·u for f32 tiers |
0.05 | Traction lead | GATE-TRAC-10 |
| OPEN-TRAC-5 | Witness-migration tolerances: δ_w and the largest normal rotation transported | The sample radius and 30°; beyond them, reset with an event | Traction lead | The sill fixture at M1 |
| Habitat (§19) | ||||
| OPEN-HAB-1 | Which published building and workplace norms supply the dimension distributions | Generic ranges labelled assumed; realism claims refused |
Project lead | GATE-HAB-02 for claims of realism, not for validity |
| OPEN-HAB-2 | Whether bricks carry a one-sample apron, which removes neighbour lookups and costs 42% more memory | No apron; up to eight directory lookups for a query in a boundary cell | Spark lead | The M2 profile; blocks nothing |
| OPEN-HAB-3 | Default spacings and truncation distance (2 cm and 16 cm, T = 8 cm) against 1 cm interiors | As stated | Habitat lead | Measured memory and the fidelity ledger at M3 |
| OPEN-HAB-4 | Sources for retrofit prices and legality constraints | Prices assumed; constraints marked unchecked in every report |
Project lead | Any claim about cost in a published report |
| OPEN-HAB-5 | Which reconstruction package and version is the import contract | The walkthrough twin package; the drone route when it publishes geometry | Habitat lead | GATE-HAB-03 |
| OPEN-HAB-6 | Whether contact with unknown space degrades the world or refuses the run | Degrade, exclude from metrics, count | Habitat lead | M5, with the first real place |
| OPEN-HAB-7 | Whether scene breadth in training improves held-out success | The bank serves evaluation | Habitat lead | The experiment of §19.15 |
| OPEN-HAB-8 | Sources for film roughness, carried thickness and transfer fraction | assumed; outputs Estimated; Reality no-claim |
Habitat lead | Any Reality claim about slip on films |
| Sensorium (§20) | ||||
| OPEN-SENS-1 | The default policy for clock events inside a step on throughput tiers | hold, with recorded lateness |
Kinesis and Sensorium leads | GATE-SENS-04, for the choice of default only; M2 |
| OPEN-SENS-2 | The limit on the clock lattice and the menu of declared rationals for common device rates | Q at most 2⁴⁰ | Sensorium lead | M2 |
| OPEN-SENS-3 | Whether observation age is a default policy input | Always in telemetry; given to a policy only when its schema declares it | Sensorium lead | M3, with the first tasks that randomize latency |
| OPEN-SENS-4 | Which sensor and optical cards ship with datasheet or measured fields | All assumed; Reality no-claim (FROB-REF-447) |
Project lead | Any Reality claim that depends on sensing |
| OPEN-SENS-5 | Whether glass reports the stronger return or draws between returns | The stronger return, deterministic | Sensorium lead | A measured card for one depth camera and one lidar |
| Spark (§21) | ||||
| OPEN-SPARK-1 | Owner ratification of ADR-SPARK-01 | An exploratory label on GPU results | Owner | M2 exit |
| OPEN-SPARK-2 | The compute envelope for gate measurements and training campaigns (classes E0 to E3, §36.14) | E0: FrankenSim's machine rule for CPU work, and one device for one hour per GPU job | Owner | GATE-SPARK-03, -04, -20, -21 as specified |
| OPEN-SPARK-3 | The bucket set and the capacities of each reference workload | Links {12, 18, 24, 36, 48, 64}, the set §17 states, and the capacities of §36.3; the M1 pilot of §17.14 may revise the set for both chapters at once | Spark lead | GATE-SPARK-10; the M2 profile |
| OPEN-SPARK-4 | Whether the pinned cudarc exposes graph capture and the asynchronous pool calls, and if not whether the capsule may declare them |
Preallocated transient buffers and per-launch submission, with the throughput cost disclosed | Spark lead | INT-CUDA-01 |
| OPEN-SPARK-5 | What Spark does if INT-FT-01 fails, or until the upstream work item FD-FT-01 lands | Stay inside the gateway's limits and accept KILL-METAL's fallback; no Metal binding of our own without an owner decision | Owner | KILL-METAL |
| OPEN-SPARK-6 | Whether the two RTX 4090 of trj allow device-to-device access |
Host-staged transfers of small statistics only | Spark lead | The fingerprint (GATE-SPARK-07) |
| Reflex, gaits and shields (§22) | ||||
| OPEN-REFLEX-1 | Whether the predictive controller runs on device | The single-step program on every tier; the predictive controller on CPU tiers only until measured | Reflex lead | M3 |
| OPEN-REFLEX-2 | The rank-agreement thresholds of GATE-REFLEX-04: the pair (0.7, 0.5) or the pair (0.6, 0.3) | The stricter pair, fixed before data; until the gate has run the baseline rung discards only | Reflex lead | GATE-REFLEX-04 |
| OPEN-REFLEX-3 | The residual's authority ρ per channel | 0.3 of range | Reflex lead | GATE-REFLEX-05 |
| OPEN-REFLEX-4 | Whether screening by the sampling controller needs a 4 ms planning step | 20 ms, labelled in the ControllerId, with results flagged model-privileged |
Reflex lead | GATE-REFLEX-06 |
| OPEN-GAIT-1 | When the referee route for orbits is built | Compliant tiers only | Kinesis lead, with upstream | Nothing on the critical path |
| OPEN-GAIT-2 | The norm and tolerance for order sensitivity | The mass norm and 1% of the pre-impact speed | Reflex lead | GATE-GAIT-02 |
| OPEN-SHIELD-1 | Where absorber envelopes come from before any bench data exist | assumed cards and Estimated claims |
Sinew lead, with Ground | Any energy claim above Estimated |
| OPEN-SHIELD-2 | The calibration level α and the per-episode violation budget | α = 10⁻³ and a budget of 10⁻³ per episode | Owner | GATE-SHIELD-03, -04 |
| Cortex (§23) | ||||
| OPEN-CORTEX-1 | The compute envelope for family-policy pretraining | No pretraining | Owner | GATE-CORTEX-11 and every use of a family policy |
| OPEN-CORTEX-2 | The default action law | latent-then-limit |
Cortex lead | GATE-CORTEX-07 |
| OPEN-CORTEX-3 | The reset schedule for lineages (depth k and audit rate m) | k = 5 and m = 8 | Cortex lead | GATE-CORTEX-13 |
| OPEN-CORTEX-4 | The adapter's transport: shared device views, or one copy per step across a process boundary | One charged copy per step | Tether lead | GATE-CORTEX-16 |
| OPEN-CORTEX-5 | Default β and κ per task family | β = 0.5025 /s and κ = 2.565 /s, which give γ = 0.99 and λ = 0.95 at 20 ms | Arena lead | Nothing |
| OPEN-CORTEX-6 | Whether the incumbent wall-clock of GATE-CORTEX-05 is re-measured on our card before M2 | The gate is recorded against the published figure, labelled published-context, until the re-measurement exists |
Spark lead | Citing GATE-CORTEX-05 as passed; closed by GATE-SPARK-21 |
| Arena (§24) | ||||
| OPEN-ARENA-1 | Which public task definitions to mirror for comparability | The reward terms of the public velocity-tracking tasks, with no claim of score parity | Arena lead | M2 |
| OPEN-ARENA-2 | A permissively licensed hexapod reference model | None; the template stands alone | Arena lead | M4 |
| OPEN-ARENA-3 | The size and composition of the sealed world families, and who holds qual:admin |
The owner alone opens and closes campaigns; one sealed family per task family, sized for 20 requests at 256 clusters; no result is called qualified until a family exists | Project lead | GATE-QUAL-01 |
| OPEN-ARENA-4 | Whether fixture 2's quadruped is the reference template or a dedicated minimal body | The reference template at a pinned DesignId |
Arena lead | GATE-ARENA-06 |
| OPEN-ARENA-5 | The guard band for boundary atoms on each backend | 2⁻²¹, with CPU re-evaluation of every flagged atom | Spark lead | The device half of GATE-ARENA-03 |
| Augur (§25) | ||||
| OPEN-AUGUR-1 | Whether .fmission predicates are written in the requirement language of .ftask or reference its terms by identifier |
Reference by identifier, so that there is one grammar | Arena lead | GATE-AUGUR-01 |
| OPEN-AUGUR-2 | Whether the linear programs are solved exactly over ℚ or in floating point with rational reconstruction | Floating point in the cone solver, basis reconstruction over ℚ, exact check; a failed reconstruction leaves the cell unresolved | Augur lead | GATE-AUGUR-02, from the reconstruction failure rate |
| OPEN-AUGUR-3 | The measured sparsity of the constraint-to-parameter graph for the plan's robot classes, and the coupled dimension that linkage closure adds | Region certificates are refused above six parameters | Augur lead | GATE-AUGUR-09 |
| OPEN-AUGUR-4 | Whether a quantifier-elimination or SMT engine is a production dependency or only a comparator outside the product | Comparator only; in-tree elimination for small linear systems | Owner | Before the M3 partial gate; KILL-AUGUR-TIE depends on it |
| OPEN-AUGUR-5 | Sound reachable tubes for contact-rich full-order cells, which no sibling provides | Constructive inclusion is limited to static, quasi-static, finite-game and low-dimensional smooth cells; contact-rich cells stay unresolved with Tested trajectories |
Augur lead | Revisited at M4 |
| OPEN-AUGUR-6 | Where the std-only checking code lives, and who writes bundles |
Settled by ADR-WS-02 (§34.11): frob-cert defines and reads the bundle, frob-lemma writes it, frob-verbs runs the check before an answer returns |
— | Settled; tombstoned |
| OPEN-AUGUR-7 | The exit code of a mission query that stops on budget with certified cells | Exit 2 with resolution-unmet; the certified cells and the unresolved remainder are returned, each cell complete in itself |
Tether lead | The registry entry of mission.synthesize at M1 |
| OPEN-AUGUR-8 | Who reviews the primitive equations in a bundle, and whether that review is recorded in the bundle | Unreviewed bundles say so in their flags and cannot be cited under the Proof claim outside the fixtures of §25.26 | Lemma lead | Citing a bundle under the Proof claim |
| OPEN-AUGUR-9 | Whether .fmission version 1 expresses several decision makers with separate histories |
The field accepts one decision maker; more than one is refused until slice 5 of §25.23 | Augur lead | M8 |
| OPEN-AUGUR-10 | The compute and calendar envelope for the Moonshot slices of §25.17 to §25.20 | None is funded before its pilot passes | Owner | M6 and M8 epics |
| OPEN-AUGUR-11 | Whether a measure on unresolved sets is standardized (volume in a named chart) | No measure; the caller supplies one in resolution, and probability mass is reported only under a supplied weighting |
Augur lead | Nothing |
| Nemesis (§26) | ||||
| OPEN-NEMESIS-1 | Sources for the legality bounds of interiors | Bounds are assumed, and counterexamples say so |
Project lead, with OPEN-HAB-1 | Claims that a counterexample is realistic, not its validity |
| OPEN-NEMESIS-2 | The distress score when the requirement margin is flat until shortly before failure | No splitting for that requirement; crude sampling | Nemesis lead | GATE-NEMESIS-05 |
| OPEN-NEMESIS-3 | The compute envelope for a 10⁻⁶ claim, which exceeds the one-hour job rule | Certify to 10⁻⁵ and report 10⁻⁶ as Estimated |
Project lead | Any certified rate below 10⁻⁵ |
| OPEN-NEMESIS-4 | The sample caps of 10⁶ in fs-eproc and fs-uq, and the absence of splitting upstream |
Our own exact binomial bound for larger counts; upstream work items FD-FSIM-18 and FD-FSIM-19 are open and no milestone waits on them | Airlock lead | Nothing |
| OPEN-NEMESIS-5 | How a hard-world set is carried across a change of robot class or task version | A set belongs to one class and one task version; worlds are re-promoted before they enter another | Arena lead | Nothing |
| Autopsy (§27) | ||||
| OPEN-AUTOPSY-1 | Default replicate count and perturbation sizes | 8 replicates at 10⁻¹², and 8 at 10⁻⁷ for interventions that change the outcome | Autopsy lead | The pilot of §27.17 |
| OPEN-AUTOPSY-2 | Whether one-at-a-time contrasts suffice, which would make pairs optional | Singles and pairs | Autopsy lead | GATE-AUTOPSY-03 |
| OPEN-AUTOPSY-3 | Lyapunov exponents of our own controllers and policies on our tiers, which set the usable fork horizon | Leads of at most 2 s, with the growth of placebo separation reported in every attribution | Cortex lead | Measured at M3; blocks nothing |
| OPEN-AUTOPSY-4 | The size of the snapshot reservoir on each device | Sized by the budget estimator; every other fork point is reconstructed by replay | Chronicle lead | Nothing |
| Atelier (§28) | ||||
| OPEN-ATEL-1 | The loss constants of DC-01 and the exchange rate between GPU-seconds and real experiment cost in DC-05 | The fixed 30-pair rule and the fixed experiment order | Atelier lead | GATE-ATEL-13 |
| OPEN-ATEL-2 | The definition of a stratum (the mode thresholds are settled at 0.7 and 0.5, §28.10) | One stratum per morphology class; an unmeasured stratum is uninformative |
Atelier lead | GATE-ATEL-07 |
| OPEN-ATEL-3 | Whether fs-recompute, fs-voi and fs-race pass admission through the airlock on T |
The node record, the closed-form value and the race are implemented locally against the same known answers | Suite lead | GATE-ATEL-12, -15 |
| OPEN-ATEL-4 | Whether result.revalidate and mission.revalidate stay two verbs over one engine or become one verb |
Two verbs, one engine | Tether lead | The verb registry freeze at M3 |
| OPEN-ATEL-5 | The planted winner for morphology classes that have no earlier specialist result | The control is reported not-run, and finalists are described as "k survivors" |
Arena lead | GATE-ATEL-09 for those classes |
| OPEN-ATEL-6 | Whether a fine-tune fraction of 5% is the right R2 rung, or two R2 rungs are needed | One R2 rung at 5% | Cortex lead | The calibration experiment of §23.11 |
| Chronicle (§29) | ||||
| OPEN-CHRON-1 | Column compression without a third-party codec | Uncompressed quantized columns | Chronicle lead | Nothing before M2 |
| OPEN-CHRON-2 | The chunk length L and the depth of the device ring | 256 control ticks per chunk and 2 s of ring | Chronicle lead | GATE-CHRON-04 |
| OPEN-CHRON-3 | Whether identifier types are imported from franken_kernel under the single-version rule for asupersync, or defined locally with the same layout |
Defined locally in frob-core |
Suite lead | GATE-CHRON-10 |
| OPEN-CHRON-4 | Retention windows for failure captures and the default store budget on each machine | 30 days and 64 GB | Owner | GATE-CHRON-12 |
| OPEN-CHRON-5 | Lease granularity: one generation per run, or one per shard with a versioned world-to-shard map | One per run | Tether lead | GATE-CHRON-04 on two devices |
| Ground (§30) | ||||
| OPEN-GROUND-1 | Which public paired simulation-and-reality dataset, if any, has enough robots per class to test exchangeability across units. None was identified | The second-simulator stand-in, labelled synthetic |
Ground lead | GATE-GROUND-10 only |
| OPEN-GROUND-2 | Whether any bench hardware of §30.17 is acquired | None; Reality stays no-claim |
Project lead | Nothing |
| OPEN-GROUND-3 | Calibration expiry by age and operating hours | 90 days or 200 operating hours, whichever comes first, and always on part replacement | Ground lead | GATE-GROUND-10 |
| OPEN-GROUND-4 | The exchange rate between operator time and GPU-seconds in the experiment table | Real episodes are recommended, never scheduled, and no rate is assumed | Project lead | Nothing |
| OPEN-GROUND-5 | Who is the authenticated authority that could promote a sibling's estimated candidate | Nobody; every Ground output stays Estimated |
Lemma lead | Any Ground output above Estimated |
| Foundry (§31) | ||||
| OPEN-FOUNDRY-1 | Whether fs-mesh produces a conforming mesh of an arbitrary optimized surface |
If it does not, the independent check is a second cut-cell solve at another resolution and offset, labelled check: same-family |
Foundry lead | GATE-FOUNDRY-04 |
| OPEN-FOUNDRY-2 | Which parts catalogue and price data, under what licence | Card references and no prices | Project lead | Nothing |
| OPEN-FOUNDRY-3 | Which current-capacity table governs conductor sizing | Current density against a limit declared on the cable card, with no capacity claim | Foundry lead | Any conductor capacity claim |
| OPEN-FOUNDRY-4 | Stress-life data for printed material by process and orientation | fatigue: no-claim for printed parts |
Foundry lead | The fatigue leg of GATE-FOUNDRY-05, for printed fixtures only |
| OPEN-FOUNDRY-5 | Wear, insulation and cell-fade coefficients with provenance | Generic cards marked assumed, which --strict-data refuses |
Sinew lead | GATE-FOUNDRY-12 |
| OPEN-FOUNDRY-6 | The time budget per bit-vector obligation | 2 s (TARGET); a timeout is undecided and is therefore refused | Lemma lead | GATE-FOUNDRY-11 |
| Tether (§32) | ||||
| OPEN-TETHER-1 | Decided with OPEN-SUITE-2; kept as a recorded decision. The question was whether frob-mcp can link handler crates in process |
Decision: frob-mcp is a member of the core graph and runs verbs in process, once FD-FMCP-01 has brought fastmcp_rust onto T; KILL-MCP's fallbacks if INT-FMCP-01 cannot pass |
Tether lead | Decided; confirmed by INT-FMCP-01 |
| OPEN-TETHER-2 | Whether the agent harnesses in use speak one of the two protocol eras the library serves, and act on catalog-changed notifications | Static clusters by launch flag, plus verb_invoke |
Tether lead | GATE-TETHER-12 |
| OPEN-TETHER-3 | The default and maximum of sync_wait_ms, against measured agent turn time and measured verb latency |
5,000 and 30,000 | Tether lead | GATE-TETHER-13 |
| OPEN-TETHER-4 | The slot reserve, per-environment job cap, quantum and ageing period, from the M2 queue trace | 5%, 64, 5 s, 600 s | Daemon lead | GATE-TETHER-10 |
| OPEN-TETHER-5 | Whether the peer link between the two machines earns its upkeep | Standalone machines | Owner | M4 |
| Suite consumption (§33) | ||||
| OPEN-SUITE-1 | Which asupersync version the whole graph resolves to | The one published version FD-ASUP-01 aligns the siblings on; until it lands, whatever FrankenSim's pinned commit builds with (0.6.2 by path today) | Build lead | INT-ASUP-01 |
| OPEN-SUITE-2 | Decided by the owner on 2026-11-22; kept as a recorded decision. The question was whether the core moves to a nightly at or above 1.100 so that frob-mcp may join the core graph |
Decision: one toolchain T for the whole build graph, chosen at INT-TOOLCHAIN-01 in the order of §33.13; fastmcp_rust is brought onto T by FD-FMCP-01; frob-mcp is a member of the core graph and runs verbs in process |
Owner | Decided; confirmed by INT-TOOLCHAIN-01 and INT-FMCP-01 |
| OPEN-SUITE-3 | Whether a dirty asupersync checkout is acceptable for development builds between receipts | Yes for development, with the tree hash in the receipt; no gate records a PASS | Owner | INT-FSIM-01 |
| OPEN-SUITE-4 | The alias set of frob_core::qty, and whether it stays within 64 |
The quantities used by §13 to §18 only | Marrow lead | INT-TOOLCHAIN-01 |
| OPEN-SUITE-5 | The budget for the cold build of the M1 closure on the build workers | The machine envelope: one hour, 16 GiB, 8 cores | Owner | INT-FSIM-01 |
| OPEN-SUITE-6 | Whether computational crates take asupersync's Cx or a capability-free token from frob-core |
Cx wherever cancellation is observed; the token only if INT-ASUP-01 fails after FD-ASUP-01 and a fallback splits the graph |
Tether lead | INT-ASUP-01 |
| Workspace (§34) | ||||
| OPEN-WS-1 | The rank order inside layers 4 and 5, where the chapters of Part IV may need edges the crate map did not foresee | The order of §34.2; a change is an ADR | Build lead | The first contract of each crate |
| OPEN-WS-2 | Whether frob-tui stays in the core workspace or becomes an annex |
Core. If INT-FTUI-01 shows that frankentui does not build on T, the remedy is an upstream change in frankentui or the toolchain train, with no dashboard until it lands | Tether lead | INT-FTUI-01 |
| OPEN-WS-3 | The stable release named in frob-cert's toolchain file |
The newest stable release on the day of its first commit, then moved only by ADR | Lemma lead | The first commit of frob-cert |
| OPEN-WS-4 | Whether .fmission is owned by frob-spec or by frob-mission |
frob-spec, for the reason in §34.9 |
Augur lead | The contract of frob-spec |
| OPEN-WS-5 | Whether the Gymnasium adapter binds in process or across a process boundary | Across a process boundary with shared array files, so that no interpreter is ever in a frob binary |
Cortex lead | The adapter's contract (§23.18) |
| Numerics and determinism (§35) | ||||
| OPEN-NUM-1 | Whether an explicit fused multiply-add is ever admitted in batched kernels | No | Spark lead | Nothing; the evidence is the probe's record of fused rounding on each family |
| OPEN-NUM-2 | The decision-equivalence thresholds (1% and 0.5%) and the ensemble size | As stated, frozen once at M2 with a written rationale | Spark lead | GATE-SPARK-16 |
| OPEN-NUM-3 | The cell side of anchored positions | 8 m, with the offset centred in [−4, 4) m | Spark lead | Nothing |
| OPEN-NUM-4 | The limit for Degraded: ill-conditioned and the refinement count of the stiff profile |
κ̂·u above 0.1; one refinement step | Spark lead | GATE-SPARK-18 |
| Performance (§36) | ||||
| OPEN-PERF-1 | The tolerance ratio of 0.67 and the band below it | As stated; below 0.33 KILL-PARITY fires | Performance lead | GATE-SPARK-03 |
| OPEN-PERF-2 | Which incumbent revisions and configurations are the comparators | The revisions in the source register, frozen by §39 before any paired run | Gauntlet lead | GATE-SPARK-21 |
| OPEN-PERF-3 | A credible energy source on each machine | A named gap in every disclosure block | Performance lead | Nothing |
| OPEN-PERF-4 | How the rows of §36.3 are restated if the default physics step moves from 2 ms (OPEN-KIN-1) | Every row is restated with its new decimation before any gate cites it | Performance lead | Every gate that cites §36.3 |
| Safety, security and privacy (§37) | ||||
| OPEN-SAFE-1 | Which weight layout and which policy architectures are on the allowlist at M2 | The single layout and family of §23's reference policy | Cortex lead | GATE-SAFE-07 |
| OPEN-SAFE-2 | Whether policy weights trained in a private or research-only scene inherit its mark and licence set | They inherit both | Owner | GATE-SAFE-04, -05 |
| OPEN-SAFE-3 | Whether sandboxed custom reward terms are admitted, and in what sandbox | Not admitted; the closed expression language only | Owner | M4 |
| OPEN-SAFE-4 | Retention periods for job logs, idempotency keys and retired confirmation clusters | Job logs and keys for 30 days; retired clusters sealed indefinitely | Owner | M3 |
| Program (this chapter) | ||||
| OPEN-PROG-1 | Public or private repository, the licence file, and who outside the program can replicate the ten-fold result | Private; the suite's licence file; the replication kit and frob-verify are the artifacts prepared for a third party |
Owner | First push; the pin freeze of M7 |
| OPEN-PROG-2 | The adjudicating simulator and the neutral party for the ten-fold test | A pinned incumbent CPU engine that neither arm trains in, run by a fresh-context session; ratios labelled self-adjudicated |
Owner | The M3 partial gate; the M7 tournament |
| OPEN-PROG-3 | Whether the Gymnasium-compatible adapter ships as a supported binding | Built and gated for the ten-fold test and for conformance only | Owner | M3 |
| OPEN-PROG-4 | Approval of compute for the rank-agreement experiment | Not run above E0; cheap rungs are uninformative |
Owner | GATE-CORTEX-12; GATE-ATEL-07 |
| OPEN-PROG-5 | The order in which admitted Moonshot items become active under the cap of four | None before its pilot passes; then the order of §43.9 and §43.11 | Owner | M6, M8 |
| OPEN-GAUNT-1 | Which real-robot dataset, if any, is admitted to the Reality lane first | reality: no-claim everywhere |
Owner | M5; GATE-GROUND-10 |
42.4 What the defaults add up to
If every question stayed at its default, the program would still exit M0 to M5 and M7. DESIGN: that is the test a
default must pass before it is written. The resulting product would be a CPU-first studio with exploratory GPU
results, no family policy, cheap rungs that only discard, generic cards and assumed norms, no Reality claim, a
ten-fold ratio labelled self-adjudicated, and a private repository. Every one of those limits would be printed on
the results it touches. The owner's answers in §42.2 are therefore the difference between that product and the one
this plan describes, and the six that matter most, in the order they fall due, are OPEN-SPARK-1 and OPEN-SPARK-2
at M0, OPEN-PROG-4 at M1, OPEN-PROG-2 at M2, OPEN-CORTEX-1 at M3 and OPEN-PROG-1 before the pins are frozen for M7.
Four questions are closed. OPEN-SKEL-1 was closed by ADR-SKEL-02 and OPEN-AUGUR-6 by ADR-WS-02; both identifiers
are retired. OPEN-SUITE-2 and OPEN-TETHER-1 were decided by the owner on 2026-11-22: one toolchain T for the whole
build graph, fastmcp_rust brought onto T by FD-FMCP-01, and frob-mcp a member of the core graph that runs verbs in
process (§33.13, §32.12.2). Both identifiers stay in the register with the decision. Four defaults are confirmed by
the gate register and are open only to new evidence: the anchored cell of OPEN-NUM-3, the parity tolerance of
OPEN-PERF-1, the stricter threshold pair of OPEN-REFLEX-2, and the single revalidation engine of OPEN-ATEL-4.