Suite consumption
15,256 words18 subsections23 tables3 listingsPlan version 1.1
On this page18
This chapter fixes what FrankenRobotics takes from its sibling projects, in which form, behind which boundary, what happens when a sibling does not hold still, and how this program changes a sibling where the sibling is what has to change (§33.8). Every statement about sibling code below was read on 2026-11-21 at the heads listed in §33.13 and is a FACT with its path. Every statement about how this project behaves is a DESIGN. A sibling fact goes stale when the sibling moves, so a fact that a gate depends on is re-read by that gate's admission test and is never copied from this page into a record.
33.1 Postures
Five postures, the vocabulary FrankenMining established (FACT: Mining §27):
| Posture | Meaning |
|---|---|
| Consume | A Cargo dependency at an exact pin, default features off |
| Subprocess | A binary or CLI we invoke; no crate in our build graph |
| Lift | Copied source with a provenance header, a row in registries/lifts.toml and a golden test; re-owned here |
| Oracle | Development and test only; never in a production graph |
| Pattern | We copy the design, not the code |
Each foundation has an FD- row with its posture, its pin, the crates allowed to touch it, an admission gate and
a fallback, because no milestone may be blocked by a sibling that has not converged. A posture belongs to a use,
not to a repository: one sibling may be consumed for one purpose and be an oracle for another, and the ledger
(§33.4) says which. Two refinements follow from the facts in this chapter. A consumed FrankenSim crate may sit
behind a Cargo feature that is off by default, so that its closure is compiled only by the milestone that needs
it (§33.9). And the Subprocess posture is the first fallback for FrankenSim itself (§33.14).
33.2 The FrankenSim decision
ADR-SUITE-01: consume FrankenSim by path dependency, confined behind the airlock crate frob-fsim, pinned by
commit in franken-stack.lock.
The owner's brief is to use FrankenSim for the physics to the greatest extent possible. The referee tier needs
fs-mbd and fs-contact whole, together with geometry, integrators, optimizers and the ledger. Those two crates
are about 438 thousand lines between them with their tests (FACT: 291,848 and 146,603 lines of Rust under
frankensim/crates/fs-mbd and frankensim/crates/fs-contact). Copying that would be a fork.
What is consumed and what is owned must be stated plainly. FrankenSim is the referee and the source of geometry
kernels, structure-preserving integrators, optimizers, statistics and the design ledger. The batched engine is
FrankenRobotics code: the kernel library, the fixed-step convex compliant solve, the model-variant tables, the GPU
backends and the gym (§16, §17, §21, §23). FrankenSim's fs-control crate covers sampled motor current loops
only (FACT: frankensim/crates/fs-control/Cargo.toml, description). Four further limits are reported and are
re-read at INT-FSIM-03 before any gate cites them: FrankenSim has no batched environments, fs-mbd is plain
f64 and not generic over a differentiation scalar, it emits no articulated adjoints, and it steps over contact
sets the caller supplies.
The two sibling products chose otherwise, and their reasons are facts this plan must answer. FrankenMining
rejected a Cargo dependency on FrankenSim because it would link two asupersync versions, needs a different
nightly for one crate's const-generic feature, failed cargo check on fifteen targets at the time, and uses
out-of-repo relative paths. Its stack lock records the result as posture = "lift" (FACT:
franken_mining/franken-stack.lock, row FD-FSIM-00). FrankenTextiles lifts files one by one. Why the decision
differs here:
- The need is different in kind. Those products took numerics files. This one needs the multibody and contact engines.
- The mechanism has precedents, and their limit is known. Five crates sit outside FrankenSim's workspace with
their own
[workspace]table and consumefs-*crates by path:apps/instrument-lab/render-gpu,apps/instrument-lab/render-gpu-piano,apps/pocket-watch/engine-watch,crates/fs-cmaes-viz-wasmandcrates/fs-flyer-wasm(FACT: theirCargo.tomlfiles). All five live inside FrankenSim's directory tree, so they inherit its.cargo/config.toml.crates/fs-g1-trainis also excluded from the workspace, but it depends on nofs-*crate (FACT: its only dependency islibm), so it is not a precedent. One project outside the tree consumes four crates by path (FACT:jazz_chord_progression_editor_html/tools/piano-v2-soundboard-pack/Cargo.toml), and it carries no patch entry, no toolchain file and no build-identity setting, so it is not evidence that an out-of-tree build passes today. The precedents establish the mechanism. INT-FSIM-01 is the first measurement of the out-of-tree case. - Each objection has a mitigation that is a gate. The whole build graph, FrankenSim's crates included,
builds on one toolchain T (INT-TOOLCHAIN-01, §33.13). The workspace root repeats three things that Cargo does
not propagate from a path dependency: FrankenSim's
[patch.crates-io] asupersyncentry, its FrankenSQLite profile overrides, and the build-identity environment its linear-algebra crate requires (hazard 5 below). FrankenSim's own manifest states the rule for profiles (FACT:frankensim/Cargo.toml, comment above[profile.dev.package.fsqlite]); that the same holds for patches and for[env]in our graph is a HYPOTHESIS settled by INT-FSIM-01. A build may contain exactly one asupersync package (INT-ASUP-01), and the siblings are aligned on one published version in their own repositories (FD-ASUP-01). Volatile FrankenSim types are named in one crate only. - The fallbacks are written down, in order. First a pinned FrankenSim worker process, then a lift (§33.8, §33.14).
Known hazards on the day of writing (FACT, each with its path):
- Churn. 409 commits touched
crates/fs-mbdin the thirty days to 2026-11-21, on 17 distinct days (git log --since=2026-10-22 -- crates/fs-mbdinfrankensim). - An unfrozen composition contract.
COMPONENT_CONTRACT_VERSIONis 0 (frankensim/crates/fs-ports/src/component.rs:52). - A stale constellation lock.
frankensim/constellation.lockpins asupersync 0.5.0 at7a0f2f55047c, whilefrankensim/Cargo.lockresolves asupersync 0.6.2 by path and the local checkout is 0.6.2 atb32c5ba66315with 267 modified paths. The lock's pins for franken_numpy, frankenscipy, frankensqlite, frankentorch and franken_networkx also differ from the local heads. FrankenSim's verify-only preflight treats an off-pin or dirty sibling as a refusal (frankensim/AGENTS.md, "Cargo-Independent Constellation Preflight"), so by its own rule it would refuse today; the preflight was not run for this chapter. Whether each difference is a fast-forward or a divergence is classified at INT-FSIM-01, not assumed. - A nightly feature in the units crate.
fs-qtyenablesgeneric_const_exprs(frankensim/crates/fs-qty/src/lib.rs:20). §33.12 treats this as a named risk. - A build script that fails closed outside the tree.
frankensim/crates/fs-la/build.rspanics unlessFRANKENSIM_DEPGRAPH_RECEIPTorFRANKENSIM_DEPGRAPH_SALTis set; inside FrankenSim the salt comes from.cargo/config.toml, which a workspace outside the tree does not read.fs-lais in the closure offs-ad,fs-mbdandfs-contact. The core workspace therefore sets its own salt, naming its own development equivalence class, in its root.cargo/config.toml, and evidence-bearing performance builds export a receipt (§33.5). - A large closure. A path dependency on
fs-mbdcompiles 42 other FrankenSim crates and about 1.57 million lines of library source, becausefs-contactdepends onfs-material(633 thousand lines),fs-thermal,fs-thermochemandfs-feec(computed from theCargo.tomlfiles underfrankensim/crates). The crate set M1 needs compiles 65 crates and about 2.06 million lines. FrankenSim's lockfile holds 479 packages, of which 262 come from the registry (frankensim/Cargo.lock). INT-FSIM-01 records cold and warm build times and peak memory, and the lift fallback is priced against these numbers, not against the size of two crates. - A contact capacity. The sustained contact solver admits at most 21 contacts
(
frankensim/crates/fs-contact/src/sustained/solve.rs:26), and its articulated step keeps fixed material witnesses (§33.11, row 4). - Dirty trees. FrankenSim's own checkout has 32 modified paths at head
483d09c682f2. A pin names a commit; the resolution receipt (§33.5) hashes bytes when a tree is dirty.
A pinned commit, the airlock and the receipt are what make those survivable. Hazards 2, 3, 4, 5 and 7 are also upstream work items that this program does in FrankenSim's repository, under its rules (FD-FSIM-08; FD-FSIM-16 with FD-ASUP-01; FD-FSIM-15 and FD-FSIM-31; FD-FSIM-14; FD-FSIM-13; §33.8, Appendix F). Each keeps the interim posture stated in this chapter until its change lands. Hazard 1 is why the airlock stays whatever lands.
33.3 The airlock
frob-fsim is the only crate that may name types from FrankenSim's volatile crates. It exposes
FrankenRobotics-native traits and adapts them. A FrankenSim API change then costs one crate.
DESIGN (trait names fix intent, not signatures). The traits are grouped, and each group is a Cargo feature of
frob-fsim, so that a crate above the airlock compiles only the closure it uses:
| Feature group | Traits exposed | FrankenSim crates behind it | Default |
|---|---|---|---|
referee |
RefereeDynamics, RefereeContact, Integrator, PortSystem |
fs-mbd, fs-mbd-material, fs-contact, fs-tribo, fs-time, fs-motion, fs-ports, fs-system |
on |
geometry |
GeometryKernel, SceneQuery, MeshExchange |
fs-query, fs-geom, fs-rep-sdf, fs-rep-mesh, fs-rep-frep, fs-scene, fs-topo, fs-io |
on |
ledger |
Ledger, Session, Recompute |
fs-ledger, fs-session, fs-package, fs-recompute |
on |
optimize |
Optimizer, Archive, Racing |
fs-dfo, fs-bo, fs-ascent, fs-archive, fs-opt, fs-sos, fs-race, fs-eproc, fs-tropical, fs-symmetry |
off |
stats |
Uncertainty, ValueOfInformation, Surrogate, Assimilation |
fs-uq, fs-voi, fs-surrogate, fs-assimilate, fs-robust, fs-regime |
off |
spectral |
Spectral |
fs-spectral |
off |
actuation |
Magnetics, ThermalNetwork, CurrentLoop, PortHamiltonian |
fs-em, fs-thermal, fs-control, fs-phs, fs-matdb |
off |
structure |
StructuralOpt, ToleranceAllocation, AsBuilt, FabricationRules |
fs-solid, fs-topopt, fs-topols, fs-toleralloc, fs-asbuilt, fs-geocon, fs-fab, fs-adjoint |
off |
multiphysics |
FluidIsland, CoupledIsland |
fs-lbm, fs-couple |
off; gated bridge (§33.9) |
harness |
none (test support) | fs-roofline, fs-detaudit, fs-propcheck, fs-render |
dev only |
What a group costs to compile beyond the M1 set (referee, geometry, ledger, 65 crates and about 2.06
million lines of library source) is FACT, computed from the manifests on 2026-11-21: spectral adds nothing,
because fs-spectral is already in that closure; optimize adds 12 crates and about 84 thousand lines; stats
10 crates and about 113 thousand; actuation 2 crates and about 151 thousand; structure 13 crates and about
412 thousand; multiphysics 19 crates and about 2.31 million. The groups therefore serve two purposes of unequal
weight. They bound what a crate above the airlock may name, always. They save compile time only for the last
two.
A short bedrock-direct list may be used anywhere, because the types of those crates are the vocabulary of the
mathematics. Sizes are FACT, counted on 2026-11-21 as lines of Rust under each crate's src and under the whole
crate directory:
| Crate | Library lines | With tests | Depends on fs-qty |
Leaves FrankenSim | What it provides |
|---|---|---|---|---|---|
fs-ga |
4,078 | 4,883 | no | no | Motors, screws and meets in PGA; Lie façades in src/lie.rs |
fs-math |
5,063 | 7,633 | no | no | Deterministic elementary functions with error budgets in units in the last place |
fs-qty |
8,950 | 9,947 | it is fs-qty |
no | Compile-time dimensional analysis; runtime-checked quantities; SI parsing |
fs-rand |
7,356 | 12,053 | no | no | Counter-based Philox streams keyed by logical identity; Sobol and Owen sequences |
fs-blake3 |
7,304 | 13,757 | no | no | BLAKE3 in safe Rust; the 32-byte content hash |
fs-ivl |
5,956 | 11,295 | yes, through fs-evidence |
no | Outward-rounded intervals, affine forms, Taylor models, exact predicates |
fs-simd |
3,331 | 4,242 | no | no | SIMD tiers behind safe façades |
fs-exec |
33,870 | 38,543 | no | asupersync, by path | Two-lane executor and the Cx contract |
fs-evidence |
37,120 | 57,107 | yes, directly | no | Evidence<T> and Certified<T> with conservative composition |
fs-ad |
2,917 | 4,062 | no | asupersync through fs-la; FrankenTorch crates if a feature is on |
Forward-mode duals and the Real scalar contract |
Eight of the ten are under nine thousand lines. fs-exec and fs-evidence are larger and are admitted direct
because Cx and Evidence<T> appear in signatures throughout. The closure of the list is 16 crates and about
161 thousand lines of library source (FACT, same count). Everything else goes through the airlock.
Three rules bind the adapter. It converts, and never reinterprets: a FrankenSim refusal becomes a typed referee
refusal carrying the upstream reason, and is never retried with weakened inputs. It does not cache across pins:
every memoized referee result carries the stack-lock digest in its key. And it exposes capacities as data: the
21-contact limit of hazard 7 is a field of RefereeContact, checked when a model is compiled and again at run
time, so that an over-capacity contact set is a refusal by name and is never silently truncated (the contact set
of a tracked robot overflows where a point-foot robot's does not, and dropping contacts would bias exactly the
comparison the studio exists to make).
33.4 Foundation ledger
| FD | Foundation | Posture | Used for | Confined to | Admission | Fallback |
|---|---|---|---|---|---|---|
| FD-FSIM | frankensim | Consume by path | Bedrock-direct crates (§33.3). Through the airlock: the feature groups of §33.3, extended in §33.9 | frob-fsim, plus the bedrock-direct list |
INT-FSIM-01 to INT-FSIM-18 | KILL-FSIM: a worker process, then a lift |
| FD-ASUP | asupersync | Consume | Structured concurrency, cancellation, Cx; the lab runtime for deterministic simulation testing (§33.15) |
All async code; one package identity per build, on the one published version FD-ASUP-01 aligns the siblings on | INT-ASUP-01, INT-ASUP-02 | A surface that still brings a second package moves to its own workspace (for frob-mcp, KILL-MCP fallback 1) |
| FD-FSQL | frankensqlite | Consume; Pattern and Oracle for its pager policies | The Chronicle ledger; the qualification ledger; eviction policy for the memo store (§33.15) | frob-chronicle (through fs-ledger where it fits); frob-conformance for the oracle |
INT-FSQL-01, INT-FSQL-02 | Append-only JSON-lines ledger with the same schema; LRU eviction |
| FD-FT | frankentorch | Consume | ft-kernel-metal (Metal gateway) in the Metal annex; ft-api, ft-nn, ft-optim, ft-serialize as CPU trainer, gradient oracle and policy interchange |
spark/frob-spark-metal; frob-learn behind a feature |
INT-FT-01, INT-FT-02 | Annex binds objc2-metal directly; CPU trainer uses the in-house kernels on batch-cpu |
| FD-CUDA | cudarc (third party) |
Consume, annex only | CUDA driver and NVRTC bindings | spark/frob-spark-cuda |
INT-CUDA-01 | None needed for CPU and Metal; CUDA tier absent |
| FD-FNP | franken_numpy | Consume narrowly; Oracle | Array files at the export boundary (fnp-io); fnp-linalg batch routines as an f64 oracle for small-matrix kernels |
frob-chronicle, frob-conformance, bindings/frob-gymnasium |
INT-FNP-01, INT-FNP-02 | Plain binary columns; drop the oracle |
| FD-FSCI | frankenscipy | Oracle | Reference integrators (solve_ivp), rotation conversions (fsci-spatial), cross-check optimizers |
frob-conformance |
With INT-FSIM-01 (FrankenSim already pins it) | Drop the cross-checks |
| FD-FSYM | frankensympy | Build-time; Subprocess; second checker | Derivation of kernel arithmetic; polynomial, interval and rational certificates; the exact lane of linkage synthesis, reached as a subprocess; an independent re-check of bundles beside frob-verify |
derive/frob-derive; frob-conformance (re-check only) |
INT-FSYM-01, INT-FSYM-02 | KILL-KIR, KILL-LEMMA |
| FD-FLN | franken_lean | Subprocess | Independent re-check and sealing of Lean proofs; kernel reflection F (the tier §12.4 gives it) | lean/ tooling |
INT-FLN-01, INT-FLN-02 | Stock Lean alone, recorded as a single-kernel check |
| FD-FMCP | fastmcp_rust | Consume | The MCP server (§32), a member of the core graph on T once FD-FMCP-01 has brought fastmcp_rust onto T | surface/frob-mcp |
INT-FMCP-01 | KILL-MCP |
| FD-FTUI | frankentui | Consume F | The terminal dashboard | frob-tui |
INT-FTUI-01 | No dashboard; line-delimited JSON job events |
| FD-F3D | franken_threed | Pattern; Subprocess F | Its admission-record discipline; an optional renderer route for the viewer | viewer/ build scripts |
INT-F3D-01 | Plain Three.js bundle |
| FD-FDGR | franken_drone_geometry_reconstruction | Pattern; Subprocess F | A scan-import lane with coverage, uncertainty and scale authority | frob-scene (schema adapter only) |
INT-FDGR-01 | Mesh and point-cloud import through fs-io, scale declared by the operator |
| FD-FJAX | frankenjax | Pattern | Reference semantics for batching and differentiation transforms; the rule sets of its e-graph crate | — | INT-FJAX-01 F, only if the M2 profile asks | Common-subexpression elimination only |
| FD-FKER | franken-kernel, franken-evidence (in the asupersync repository) | Pattern; Oracle | The wire shape of trace, decision and policy identifiers (§34.12) | frob-core (shape); frob-conformance (round-trip oracle) |
With INT-ASUP-01 | Local identifier types with the same text form |
| FD-FTX | franken_textiles | Oracle; Subprocess M | ftx-drape as a reference for the cloth evaluation tier (§33.15), reached as a worker process in its own workspace because its exact serde_json pin conflicts with the core graph (§33.17, row 7) |
A worker driven from frob-conformance, behind a flag; never a Cargo dependency |
INT-FTX-01 | No cloth tier; rigid proxies |
| FD-FFW | franken_firmware | Pattern M | The hardware-abstraction boundary for firmware export | — | None until the M8 work package is funded | No firmware export |
| FD-FSS | franken_surveillance_system | Pattern | The twin package and the camera-model contract | — | None | — |
Honest notes on four of these:
- franken_numpy is an
f64array library on heap vectors with no single-precision storage and no fixed-size matrix types, and it lists GPU arrays and automatic differentiation as out of scope (FACT). It is the right tool at the interchange boundary and as an oracle. It is not put in a hot path where it does not fit. Its stride convention differs from FrankenTorch's (§33.11, row 3). - frankensympy's workspace refers to two sibling pin directories,
../franken_numpy-pinand../frankenscipy-pin, that do not exist on this machine, and it pins a different nightly from the rest of the suite (FACT:frankensympy/Cargo.toml:95–96,frankensympy/rust-toolchain.toml).derive/therefore depends on individualfsym-*crates by path. The different nightly is the starting state:derive/builds on T and has no toolchain file of its own, and frankensympy is moved to T by the toolchain train (§33.13). - frankentorch tensors live on the host.
Device::MetalandDevice::Cudaare tags, andft-nnandft-autogradrun on the CPU (FACT as reported from a source reading; re-read at INT-FT-02). A device tag earns no GPU operator coverage. On-device learning kernels are written here, in the shared dialect (§21, §23). - franken_threed does not yet package a single self-contained page (FACT:
franken_threed/README.md, "Honest status"). The viewer's self-contained HTML export is this project's own build step.
33.5 The stack lock
franken-stack.lock is TOML in FrankenMining's format (FACT: franken_mining/franken-stack.lock). One row per
foundation, checked by xtask check-stack:
toolchain = "<T, chosen at INT-TOOLCHAIN-01; moved only by a toolchain train (§33.13)>"
[[foundation]]
id = "FD-FSIM"
name = "frankensim"
posture = "consume-path"
path = "../frankensim"
git_rev = "<40-hex commit recorded at INT-FSIM-01>"
toolchain = "<the channel in the sibling's own toolchain file at git_rev; equal to T after the train>"
features = ["referee", "geometry", "ledger"] # airlock groups compiled by default
build_env = { FRANKENSIM_DEPGRAPH_SALT = "franken-robotics-dev-v1" }
confined_to = ["frob-fsim", "bedrock-direct"]
admission_gate = "INT-FSIM-01"
receipt = "<BLAKE3 of the resolution receipt this row was admitted under>"
fallback = "KILL-FSIM: (a) pinned worker process exchanging whole jobs; (b) lift the minimal referee set."
[[foundation]]
id = "FD-ASUP"
name = "asupersync"
posture = "consume"
version = "<the single version every workspace resolves>"
admission_gate = "INT-ASUP-01"
fallback = "FD-ASUP-01 aligns the siblings; a surface that still brings a second package: KILL-MCP fallback 1."
The resolution receipt. A pin is a statement of intent. What was built is a different fact, and the two have
already diverged inside the suite (hazards 3 and 8 of §33.2). xtask check-stack therefore writes one receipt
per admission and per pin move. DESIGN, schema frob.stack-receipt/1, canonical JSON:
{
"schema": "frob.stack-receipt/1",
"repo_rev": "<this repository's commit>",
"toolchain": "<T>",
"siblings": [
{"fd": "FD-FSIM", "rev": "<40 hex>", "dirty": false, "tree_hash": null,
"features": ["referee", "geometry", "ledger"],
"own_lock": {"file": "constellation.lock", "hash": "<BLAKE3>", "agrees": false,
"class": "stale-lock | drift | on-pin"}},
{"fd": "FD-ASUP", "rev": "<40 hex>", "dirty": true, "tree_hash": "<BLAKE3 of tracked bytes>"}
],
"lockfiles": [{"workspace": "core", "hash": "<BLAKE3 of Cargo.lock>", "packages": 0, "registry": 0}],
"patches": ["asupersync -> ../asupersync"],
"profile_overrides": ["fsqlite*: opt-level 1"],
"build_env": {"FRANKENSIM_DEPGRAPH_SALT": "franken-robotics-dev-v1"},
"duplicates": [],
"commands": [{"argv": ["cargo", "tree", "-d"], "exit": 0, "output_hash": "<BLAKE3>"}]
}
Rules for the receipt:
- It captures source trees, requested features, compiler channels, lockfiles and the constraints of direct and
transitive siblings in one file. A sibling's own lock (
constellation.lock,SUITE.lock) is hashed and compared, and a disagreement is classified the way FrankenSim classifies it: on-pin, stale-lock (the checkout is a fast-forward of the lock), or drift (dirty, retreated or diverged). - When a tree is dirty the receipt hashes the tracked bytes. A dirty sibling admits development builds only; no gate records a PASS on a dirty tree.
- Identities are independent of machine paths. The receipt stores repository-relative paths and revisions, never
/Users/.... - Every admission record (§33.6) cites a receipt hash. A result in the Chronicle ledger carries the receipt hash of the binary that produced it, which is what lets a later reader decide whether two results may be compared as results of the same stack.
xtask check-stackfails if the tracked lockfiles, the toolchain files or the sibling heads disagree with the newest receipt. It never moves a sibling checkout. Receipts are kept underreceipts/, named by their hash.
Known answer: a receipt computed twice on an unchanged tree is byte-identical. Negative control: touching one
tracked file in a sibling flips dirty and changes tree_hash, and check-stack fails.
33.6 Admission gates
An admission record is valid only if it cites a commit of this repo whose tracked Cargo.lock contains the
foundation, with the command, its output and the receipt hash (the rule FrankenMining adopted after finding
admission records for crates that were not in the build, FACT). Records live in DEPENDENCY_ADMISSION.md, a
convention taken from FrankenThreeD (FACT: franken_threed/DEPENDENCY_ADMISSION.md). Thresholds below are
TARGETs until the gate records measured values.
| Gate | Pass criterion |
|---|---|
| INT-TOOLCHAIN-01 | The one toolchain T is chosen and recorded in franken-stack.lock and rust-toolchain.toml, in the order of preference of §33.13: (a) the suite's common nightly, (b) FrankenSim's present pin. The whole build graph (the core, the GPU annexes, derive/frob-derive and surface/frob-mcp) builds and tests on T. The matrix of §33.12 is recorded: which of the four nightlies in play compile fs-qty, the bedrock-direct list, the M1 closure and each of the other build sets. After this gate T moves only by a toolchain train. |
| INT-FSIM-01 | From this repo, a crate depending by path on fs-ga, fs-mbd, fs-contact, fs-time and fs-query passes cargo check --all-targets with the root patch, profile and build-identity settings of §33.2, and reproduces the digest of a G1 forward-dynamics state computed inside FrankenSim at the pinned commit. Recorded: cold and warm check times, peak memory, package count, and the drift class of every sibling. The cold check must fit the machine envelope of §34.7 (at most one hour, 16 GiB and 8 cores). |
| INT-FSIM-02 to -11 | The first admission tests, file by file (§33.10). |
| INT-FSIM-13 to -17 | The group gates of the extended airlock list (§33.9). |
| INT-FSIM-18 | The worker-process fallback, exercised before it is needed (§33.14). |
| INT-ASUP-01 | cargo tree -d shows one asupersync package in each workspace, the same published version in all of them, and no binary links two. This is the gate that proves FD-ASUP-01. |
| INT-ASUP-02 | The job protocol runs under asupersync's lab runtime: 100 of 100 repeats of one seed give identical traces, and a planted lost-chunk bug is found within 10,000 explored schedules and replays from its minimized fixture (§33.15). |
| INT-FSQL-01 | The ledger opens, writes, and recovers after a forced kill mid-write. |
| INT-FSQL-02 | The memo store's eviction sequence equals the sibling policy's on 10 recorded traces of at least 10⁵ accesses (§33.15). |
| INT-FT-01 | ft-kernel-metal's gateway builds in the Metal annex, with FrankenTorch's block patch repeated at the annex root, and runs a kernel on this Mac. |
| INT-FT-02 | A buffer stays resident across two command buffers and the gateway returns a completion receipt from the device (§33.10). |
| INT-CUDA-01 | The pinned cudarc builds without a CUDA toolkit, loads the driver on trj, and runs a kernel on both GPUs. |
| INT-FSYM-01 | derive/ builds on T against the fsym-* crates by path, derives K-cay-step, and its certificate replays in the offline auditor. |
| INT-FSYM-02 | The planar two-link Jacobian compiles and agrees with closed forms at a regular and a singular configuration (§33.10). |
| INT-FLN-01 | fln builds on a Linux host, re-checks and seals one trivial theorem from lean/, and the capsule checks from an empty environment. |
| INT-FLN-02 | The checker admits a true port identity and rejects its sign-mutated twin (§33.10). |
| INT-FMCP-01 | frob-mcp builds in the core graph on T with exactly one asupersync package (cargo tree -d shows no duplicate), lists the tools generated from the verb registry, and passes the MCP protocol smoke test over stdio and HTTP (§33.13). |
| INT-FNP-01 | An array file written through fnp-io reads back identically. |
| INT-FNP-02 | The stride conversion at the interchange boundary reads element 3, not element 12, on the 2×2 case (§33.11, row 3). |
| INT-FTUI-01 | frankentui builds with one asupersync package or none, and the recorded job pane equals its snapshot (defined in §33.15). |
| INT-F3D-01 | The replay page built through franken_threed's route matches the plain bundle (defined in §33.15). |
| INT-FDGR-01 | The scan-import schema fixtures validate and a non-metric scale is refused (defined in §33.15). |
| INT-FJAX-01 | An extracted kernel matches its baseline bit for bit with at least 10% fewer operations (defined in §33.15). |
| INT-FTX-01 | The cloth drape matches ftx-drape, run as a worker process (defined in §33.15). |
An admission is never inherited. A crate first used at M4 is admitted at M4, by its own record, at the pin of that day.
33.7 The dependency firewall
Which milestone needs which foundation. A blank cell means the milestone does not depend on it. A cell in parentheses is used if the foundation is admitted and is not required for the milestone to exit. Milestone content is defined in §43; this table states dependency only.
| Foundation | M0 | M1 | M2 | M3 | M4 | M5 | M6 | M7 | M8 |
|---|---|---|---|---|---|---|---|---|---|
| frankensim | admit; file tests | referee, geometry, ledger, memo store; the statistics the two study types use (admitted when first used, §33.6) | parity oracle | optimizers, racing, statistics, spectral | optimizers, archive, surrogates | structural, variational, as-built, manufacture | multiphysics bridge | frozen pin | |
| asupersync | admit; one version (FD-ASUP-01) | jobs; lab runtime for the job protocol | device jobs | daemon, MCP | frozen pin | ||||
| frankensqlite | admit | ledger | qualification ledger | ||||||
| frankentorch | admit (Metal) | Metal backend, gradient oracle | policy interchange | ||||||
| cudarc | admit | CUDA backend | |||||||
| frankensympy | admit | (certificates for M0 kernels) | derived kernels | exact synthesis lane | coverage gate | ||||
| franken_lean | capsules; reflection F | ||||||||
| fastmcp_rust | bring onto T (FD-FMCP-01); admit | (MCP for M1 verbs) | full MCP | mission tools | rival access | ||||
| franken_numpy | admit | (array export) | small-matrix oracle | (Gymnasium adapter) | |||||
| frankenscipy | (reference integrators) | ||||||||
| frankentui | (dashboard) | ||||||||
| franken_threed | (renderer route) | ||||||||
| drone reconstruction | (schema fixtures) | (scan import) | |||||||
| franken_textiles | (cloth oracle M) | ||||||||
| franken_firmware | (pattern M) |
M1 depends only on FrankenSim, asupersync and FrankenSQLite. If the GPU, symbolic and proof foundations all
failed admission, M1 would still ship a referee-tier design studio and the first mission slice on the CPU. The
mission slice needs no symbolic or proof sibling, because its certificates are checked by frob-verify, which
uses the standard library alone (§34.11). Nothing in the last five rows is on a critical path. The M0 column
carries the two upstream work items at priority P0, FD-FMCP-01 and FD-ASUP-01 (§33.8). Neither is on M1's
critical path: if INT-FMCP-01 cannot pass within the M0 budget, KILL-MCP's fallbacks apply and M1's verbs are
reached through the CLI. M7 freezes every pin and T for the length of the tournament, because a ratio of times
measured across a pin move or a toolchain train is not one measurement (§39).
33.8 Upstream work and drift
Every sibling this plan consumes is the owner's project (FACT, stated by the owner on 2026-11-22). DESIGN: a
limitation, defect or mismatch in a sibling is therefore work this program does, in the sibling's repository,
under that repository's own AGENTS.md, gates and conventions. Each such change is an upstream work item
(Appendix F): a bead in this program's graph with the label upstream, mirrored as a bead in the sibling's
tracker, with a priority, an interim posture here, and a switch-over rule. The interim posture and the
switch-over rule exist so that no milestone waits on a sibling change landing. Upstream changes are additive: a
new mode, type or feature, never a change to existing behaviour, with any lossiness self-described (the rule the
Wright Flyer plan sets for its upstream extensions, FACT). Each upstream work item carries one reproducible
failing fixture and a description of the needed argument or result.
The sibling's rules bind the work. For FrankenSim they include its layer checks, its contracts, its
unsafe-capsule discipline, its ban on in-process foreign kernels in production paths, which is why the GPU
annexes stay in this repository, and its ban on branches and worktrees (FACT: frankensim/AGENTS.md,
frankensim/docs/ACCELERATOR_DOCTRINE.md; §21.2, §34.4, §34.7). Other agents work in the same sibling
repositories. Before an upstream change edits a file it reserves that file through Agent Mail and follows the
sibling's own coordination rules, and it lands on the sibling's main through the sibling's own gates.
Pins advance through a compatibility train: move the pin, write a new receipt, rerun the admission and parity
gates, relock. A sibling's newer clean head is never rolled back locally. The airlock crate frob-fsim stays,
because FrankenSim's API still moves daily (hazard 1 of §33.2). The fallbacks stay written down (KILL-FSIM,
KILL-MCP and the others); they are fallbacks, and no default wiring rests on one.
Upstream work items added by this chapter, continuing the series of Appendix F:
| Upstream work item | Repo | Change | Priority | Interim posture | Switch-over rule |
|---|---|---|---|---|---|
| FD-FSIM-10 | frankensim | Correct fs_g1_train::ppo_update: the clip branch for negative advantage, the critic gradient from the current forward output, and episode boundaries in the sequence forward (§33.11, row 1) |
P2 | Not a dependency and not an oracle; PPO is written here | Re-run INT-FSIM-06; only then may it serve as a comparison baseline |
| FD-FSIM-11 | frankensim | planar_drive: choose the straight branch on the heading increment relative to the heading's rounding unit, or use the half-angle chord form (§33.11, row 2) |
P2 | Known answers for wheeled bases use the independent formula | Re-run INT-FSIM-05; then admit as an oracle |
| FD-FSIM-12 | frankensim | A moving-surface owner for the sustained step: witness migration across an edge, with tangential memory transported or reset under the declared friction law (§33.11, row 4) | P1 | The referee's transactional step migrates witnesses above the airlock (§16) | Re-baseline the fidelity ledger once |
| FD-FSIM-13 | frankensim | A sustained solve above 21 contacts, or a documented patch model with a qualification fixture | P1 | Over-capacity sets refuse by name | Re-run the capacity fixtures of §18 |
| FD-FSIM-14 | frankensim | A documented build-identity setting for path consumers outside the tree (fs-la/build.rs) |
P2 | The core sets its own salt; performance builds export a receipt | Remove the local setting if a default class is published |
| FD-FSIM-15 | frankensim | Land the macro-generated dimension products that fs-qty documents as its fallback, behind a feature, so consumers are not tied to generic_const_exprs |
P1 | frob_core::qty re-export; frob-units if forced (§33.12) |
Re-run INT-TOOLCHAIN-01 |
| FD-FSIM-16 | frankensim | Refresh constellation.lock to the heads its Cargo.lock builds with |
P2 | The resolution receipt records the disagreement | check-stack reports on-pin |
| FD-FNP-01 | franken_numpy and frankentorch | A named conversion between signed byte strides and unsigned element strides, with the unrepresentable cases refused | P2 | A typed converter at our boundary | Replace the local converter; re-run INT-FNP-02 |
| FD-FSQL-01 | frankensqlite | Make the S3-FIFO state machine generic over its key type | P3 | Pattern with a differential oracle | Consume it; delete the local copy |
| FD-FMCP-01 | fastmcp_rust | Bring fastmcp_rust onto T: its toolchain file and, where T requires it, its declared rust-version are changed so that it builds on T, and its own test suite and its MCP conformance checks pass on T. Under candidate (a) of §33.13 the same toolchain train advances FrankenSim's pin and moves frankensympy |
P0, at M0 | Agents use the CLI, which is complete on its own; if the change cannot land within the M0 budget, KILL-MCP's fallbacks apply | INT-FMCP-01 passes with frob-mcp in the core graph on T |
| FD-FTUI-01 | frankentui | Relax the exact asupersync 0.5.0 pin on its optional executor | P3 | The executor feature is forbidden here | None needed unless the executor is wanted |
| FD-FKER-01 | asupersync (franken-kernel) | Add claim and evidence identifier types beside TraceId, DecisionId and PolicyId |
P3 | Local types in frob-core with the same text form |
Replace local types |
Two upstream work items are at priority P0 and are done at M0: FD-FMCP-01 above, and FD-ASUP-01 (Appendix F), which aligns FrankenSim's constellation, FrankenTorch and fastmcp_rust on one published asupersync version by changes in those repositories. INT-FMCP-01 and INT-ASUP-01 are the gates that prove them.
The priority of an upstream work item states its value to this project and orders it in this program's queue. No priority makes a milestone wait: the interim posture holds until the switch-over rule has been run. What the work costs, the order in which it is done and collisions with other agents in the same sibling are carried as risks in §41.
| ✖ KILL-FSIM | Trigger: INT-FSIM-01 cannot pass within two weeks of M0 effort, or its cold check exceeds the machine envelope, or BET-04's breakage threshold is crossed (upstream breakage above 20% of working days in any four-week window). Fallback (a): the volatile crates move behind a process boundary: one pinned FrankenSim worker process per device exchanges whole jobs with the core through the same airlock traits (§33.14). The bedrock-direct crates that still pass their own admission stay path dependencies; those that do not are lifted first, since they are small. Fallback (b), only if (a) fails INT-FSIM-18 or the pinned commit can no longer be built on any available toolchain: lift the minimal referee set with provenance headers and golden tests (fs-ga, fs-math deterministic functions, fs-rand, the fs-mbd articulated module, the fs-contact multicontact solve), record every lifted file in registries/lifts.toml, state "lift-only" in the README, and keep the upstream work items open. |
The order matters because of hazard 6. The lift set is small only on paper: the two modules it names sit on a
closure of about 1.5 million lines, and cutting them free of fs-material is engineering that fallback (a)
avoids entirely. A worker keeps FrankenSim's real code as the referee at an old pin for as long as needed.
33.9 FrankenSim crates reached through the airlock for the new subsystems
Each crate below exists at head 483d09c682f2. Sizes and closures are FACT, counted as in §33.3; the closure is
the number of other FrankenSim crates a non-optional path dependency compiles. The purpose column paraphrases the
crate's own manifest description and the modules named were found in its src.
| Crate | Library lines (with tests) | Closure | Needs fs-qty |
What it provides | Reached by | Group gate |
|---|---|---|---|---|---|---|
fs-spectral |
14,329 (24,566) | 13 | yes, directly | Spectral problem admission and health monitoring; floquet::analyze_monodromy analyses a supplied monodromy matrix |
frob-gait, frob-lifecycle |
INT-FSIM-13 |
fs-uq |
15,887 (23,672) | 37 | yes | Karhunen–Loève fields, polynomial chaos, quasi-Monte Carlo, multilevel Monte Carlo, control variates, importance sampling, Shapley effects | frob-nemesis, frob-arena, frob-ground |
INT-FSIM-14 |
fs-voi |
1,044 (1,715) | 5 | yes | Ranking-flip probability, an expected-value-of-information surrogate, expected opportunity loss | frob-opt, frob-arena, frob-mission |
INT-FSIM-14 |
fs-surrogate |
6,663 (8,841) | 0 by default | no | Reduced-order models (POD, DMD, polynomial EDMD) admitted only inside validity bands, with escalation | frob-opt, frob-mission |
INT-FSIM-14 |
fs-assimilate |
13,024 (20,534) | 9 | yes, directly | Checked linear-Gaussian belief updates from instrument observations | frob-ground |
INT-FSIM-14 |
fs-topopt |
40,042 (68,735) | 51 | yes | Density topology optimization (SIMP, Helmholtz filter, Heaviside projection, exact sensitivities) | frob-foundry |
INT-FSIM-15 |
fs-topols |
15,709 (16,807) | 40 | yes | Level-set topology optimization with CutFEM-coupled compliance descent | frob-foundry |
INT-FSIM-15 |
fs-toleralloc |
6,491 (9,555) | 5 | yes | Adjoint-driven tolerance allocation by first-order variance propagation (allocate) |
frob-foundry |
INT-FSIM-15 |
fs-asbuilt |
10,802 (16,392) | 14 | yes, directly | Registration of scan data to a design by a closed-form rigid fit, with the fit residual retained | frob-ground, frob-foundry |
INT-FSIM-15 |
fs-geocon |
1,341 (2,608) | 18 | yes | Minimum thickness, draft, envelopes, certified volume, each with derivatives or certificates | frob-foundry |
INT-FSIM-15 |
fs-fab |
355 (471) | 4 | yes | A vocabulary of fabrication constraints; thin today | frob-foundry |
INT-FSIM-15 |
fs-io |
22,276 (28,772) | 13 | yes | Hardened mesh interchange and bounded STEP exchange with quarantine receipts | frob-foundry, frob-scene |
INT-FSIM-15 |
fs-recompute |
3,034 (5,661) | 10, plus FrankenSQLite | yes | A content-addressed Merkle graph of results with slack, skip-soundness certificates and invalidation | The memo graph (§28): frob-verbs, frob-chronicle |
INT-FSIM-16 |
fs-lbm |
348,054 (517,241) | 39 | yes, directly | Lattice Boltzmann solvers; film, freesurface and d3q19 modules |
frob-scene living worlds, evaluation tier only |
INT-FSIM-17 |
fs-couple |
1,042,487 (1,839,169) | 65 | yes, directly | Multiphysics composition through typed port relations with measured energy audits | Coupled islands M | INT-FSIM-17 |
Other FrankenSim crates the design uses or was tempted to use:
| Crate | Library lines | Needs fs-qty |
Decision |
|---|---|---|---|
fs-phs |
66,221 | no | Airlock, group actuation: port-Hamiltonian composition and discrete-gradient stepping for actuator models (§15). Its constrained interconnections are deferred upstream, so closed-loop mechanisms do not rely on it. |
fs-topo |
1,976 | yes | Airlock, group geometry: manifoldness with defect localization and Betti numbers, used in scene acceptance (§19). |
fs-regime |
2,277 | yes | Airlock, group stats: dimensionless groups and solver-validity cards, used to refuse a model outside its regime. |
fs-adjoint |
10,125 | yes | Airlock, group structure: implicit-function adjoints and gradient checks for structural sensitivities. |
fs-robust |
570 | yes | Airlock, group stats: tail-risk objectives with the weakest-input rule. |
fs-scene |
807 | yes | Airlock, group geometry: role-tagged support and keep-out boxes for referee scenes. |
fs-solid |
211,738 | yes | Already in the ledger. Its rod module serves the rod evaluation tier. Fatigue estimates use the rainflow counter of fs-material (RainflowMiner), which fs-solid's fatigue module imports (§31.4). |
fs-la |
22,883 | no | Oracle only: batched small dense routines as an f64 reference for kernel tests. It is in the bedrock closure through fs-ad. |
fs-checker |
3,851 | yes | Pattern: a standalone evidence-package checker, the model for frob-verify. Not linked, because it depends on fs-qty and the auditor may depend on nothing. |
fs-tilelang, fs-soa |
327; 339 | no | Pattern: kernel metadata vocabulary and aligned structure-of-arrays buffers. |
fs-conform |
2,995 | no | Not admitted. It is a conformance kit for chart-to-chart converters, not conformal prediction, despite the name. Conformal bands come from fs-surrogate or are written here (§30). |
fs-truss |
10,152 | yes | Not admitted: it brings franken_networkx into the graph, and no chapter needs ground-structure trusses. |
fs-g1-train |
3,494 | no | Not admitted (§33.11, row 1). |
Group gates. Each is the form of INT-FSIM-01 applied to one group at the milestone that first uses it: the group compiles from this repo behind its feature, one known answer passes through the airlock trait, and one negative control fails. Thresholds are TARGETs.
| Gate | Group | Known answer through the airlock | Negative control |
|---|---|---|---|
| INT-FSIM-13 | spectral |
The Floquet multipliers of the monodromy of ẍ + x = 0 over one period are both 1, to 10⁻¹² | A monodromy with a multiplier of modulus 1.01 is reported unstable |
| INT-FSIM-14 | stats |
A two-design comparison with mean gap Δ and standard deviations s₁, s₂ returns the closed-form ranking-flip probability Φ(−Δ/√(s₁² + s₂²)) to 10⁻¹²; a multilevel estimate of E[x²] under a standard normal is 1 within its own stated interval | Importance weights on a proposal that misses the failure region trip the effective-sample-size floor and the estimate is refused |
| INT-FSIM-15 | structure |
A tolerance allocation on a two-term stack reproduces the hand-computed variance split; a mesh written through fs-io reads back with the same hash |
A STEP file above the stated bound is quarantined with a receipt, not parsed |
| INT-FSIM-16 | ledger (fs-recompute) |
Incremental recomputation equals full recomputation on 10⁴ random edit sequences | An input missing from a key is caught by the shadow recompute within 64 hits |
| INT-FSIM-17 | multiphysics |
Poiseuille flow between plates matches the parabola to the crate's own stated tolerance; total film mass is conserved to 10⁻¹² relative over 10⁴ steps | The bridge refuses when the feature is off, and refuses a throughput-tier request |
The gated bridge. fs-lbm and fs-couple are two of the largest crates in FrankenSim, and their closure is
66 crates and about 4.1 million lines of library source, of which 19 crates and about 2.3 million lines lie
outside what M1 compiles (FACT). They are reached only through the multiphysics feature of frob-fsim, which
is off in every default build, is compiled only by the M6 lanes, and exposes two traits that exchange whole
fields at declared instants. No kernel of the batched step calls across the bridge. A result that crossed it is
labelled as evaluation tier and cannot enter a throughput claim. If INT-FSIM-17 fails, the fluid film stays the
Solid film-friction law of §18 and coupled islands are dropped (the kill gate and its fallback are stated in §19
and §16 with the mechanisms themselves).
33.10 First admission tests, file by file
A crate that compiles is not yet admitted. For each source file this project leans on, the table names what is reused and the first test that must pass before any code above the airlock calls it. Line counts are FACT at the heads of §33.13. Tolerances are TARGETs.
| Gate | Source anchor (lines) | What is reused | First admission test |
|---|---|---|---|
| INT-FSIM-02 | fs-ga/src/lie.rs (1,735), lie_differential.rs (155), lie_opt.rs (311) |
Group façades over motors; twist and wrench conventions | Transform a moving link: power ⟨wrench, twist⟩ is frame-invariant to 10⁻¹² relative, and the analytic Jacobian agrees with central differences to 10⁻⁷ relative at 1,000 seeded configurations. A deliberately reversed adjoint must fail at least three fixtures. |
| INT-FSIM-03 | fs-mbd/src/articulated.rs (3,428), articulated/generalized.rs (377), articulated/point_motion.rs (200), point_motion.rs (204) |
Tree kinematics, recursive Newton–Euler, the articulated-body solve, floating-base maps, rigid-point motion | A two-joint arm's accelerations equal those from independently differentiated energy to 10⁻¹⁰; an offset inertial sensor's acceleration equals the rigid-point formula. Recorded: scalar genericity, adjoint support, contact inputs. |
| INT-FSIM-04 | fs-mbd/src/articulated_contacts.rs (799), articulated_contacts/step.rs (854), fs-contact/src/broad_phase.rs (792) |
Coupled impulses, admitted contact steps, the spacetime broad phase | A thin step lying between two clear endpoint poses is detected on 1,000 of 1,000 seeded sweeps. A set of 22 contacts returns a typed refusal. |
| INT-FSIM-05 | fs-mbd/src/planar_drive.rs (265), robot_models.rs (1,488) |
A prescribed-speed planar drive as a known-answer source; the G1 and iiwa7 catalog builders | §33.11, row 2. Until it passes, planar_drive is not an oracle. |
| INT-FSIM-06 | fs-g1-train/src/ppo.rs (515), standin_env.rs; fs-cmaes-viz-wasm/src/g1_walking.rs (2,630) |
Nothing is linked. A walking objective and an update rule to compare against | §33.11, row 1. Until it passes upstream, neither file is a baseline. |
| INT-FSIM-07 | fs-mbd/src/articulated_contacts/step/sustained.rs, fs-contact/src/sustained/solve.rs |
The sustained force–displacement complementarity step | §33.11, row 4. |
| INT-FSIM-08 | fs-scene/src/lib.rs (807), fs-query/src/convex.rs (616) |
Support and keep-out boxes, half-spaces, convex support queries | A box-on-plane support query equals the closed form. A mesh-backed interior is not admitted by this test; it needs scene cooking and swept cases (§19). |
| INT-FSIM-09 | fs-phs/src/interconnection.rs (454), fs-tribo/src/lib.rs (2,678), fs-matdb/src/lib.rs (1,485) |
Effort and flow ports, friction-law selection, material data with provenance | Power across an interconnection sums to zero to 10⁻¹² relative; every pair parameter returns with its provenance record; a missing material pair is a refusal. |
| INT-FSIM-10 | fs-symmetry/src/lib.rs (323), fs-ad/src/ift.rs (489), gradcheck.rs (394) |
Cyclic reference cases; implicit-function sensitivities; gradient checks | The implicit sensitivity of a 2×2 fixed point equals its closed form. Recorded scope: cyclic groups only, no contact-event derivatives. |
| INT-FSIM-11 | fs-tilelang/src/lib.rs (327); apps/instrument-lab/render-gpu-piano/src/cuda.rs (414), metal.rs (384) |
Pattern only: one kernel source with a prelude per backend | No dependency is added. The test is §21's: one dialect source compiles through both preludes and matches its CPU twin. |
| INT-FSYM-02 | frankensympy/crates/fsym-calculus/src/sparse_jacobian.rs (1,705), compile.rs (2,198); fsym-formal/src/checker.rs (248), envelope.rs (89) |
Sparse analytic Jacobians generated offline, with assumptions preserved | Compile the planar two-link Jacobian; evaluate at a regular and a singular configuration against closed forms. |
| INT-FLN-02 | franken_lean/crates/fln-checker/src/admit.rs (10,040), policy.rs (190); fln-kernel/src/lib.rs (638); SUITE.lock |
An isolated checker for a small formal profile | Admit a true port identity; reject its sign-mutated twin; list axioms and coverage. |
| INT-FNP-02 | franken_numpy/crates/fnp-ndarray/src/lib.rs (2,930); frankentorch/crates/ft-core/src/lib.rs (6,415) |
Host tensor layouts on both sides of the interchange boundary | §33.11, row 3. |
| INT-FT-02 | frankentorch/crates/ft-kernel-metal/src/compute.rs (1,680) |
A safe gateway to custom Metal shading-language kernels | A buffer stays resident across two command buffers; the gateway returns a completion receipt from the device; a device tag alone earns zero operator coverage. |
INT-FSIM-12 is reserved and unused.
33.11 Reported foundation defects
Five defects or limits were reported in components this plan stands on: the three errors in the suite's PPO update
(row 1), the joint law of its action sampler (row 6, in §33.17), the planar-drive integration defect (row 2), the
stride-convention trap (row 3) and the fixed-witness assumption of the sustained contact step (row 4). The
mixed-frame fs-mbd::Wrench (row 5, in §33.17) is a convention hazard beside them, not a defect. Each is recorded as
a fact to recheck: what was reported, what a reading of the source on 2026-11-21 does and does not confirm, the
admission
test that settles it, the upstream work item, and what this project does meanwhile. None was re-executed for this
chapter. A reported number stays a report until its admission test records it.
| # | Component | Reported | Read in source on 2026-11-21 | Admission test | Upstream work item | Interim posture |
|---|---|---|---|---|---|---|
| 1 | fs_g1_train::ppo_update (frankensim/crates/fs-g1-train/src/ppo.rs:253–345) |
Three errors: the clip branch is reversed for negative advantage; the critic gradient ignores the current output; two reset episodes concatenated are forwarded as one sequence | First two confirmed by reading (lines 322–326 and 340); the third is consistent with line 309 and its number was not re-run | INT-FSIM-06 | FD-FSIM-10 | Not linked, not an oracle, not a baseline |
| 2 | fs-mbd::planar_drive (frankensim/crates/fs-mbd/src/planar_drive.rs:117–133) |
Near-straight motion at a large heading returns zero translation | Mechanism confirmed by reading and by the rounding arithmetic below; the run was not repeated | INT-FSIM-05 | FD-FSIM-11 | Independent formula in frob-conformance |
| 3 | Strides in fnp-ndarray and ft-core |
Signed byte strides on one side, unsigned element strides on the other; a verbatim copy reads the wrong element in bounds | Both conventions confirmed (fnp-ndarray/src/lib.rs:258, :390; ft-core/src/lib.rs:397, :2460); the wrong read was not executed |
INT-FNP-02 | FD-FNP-01 | A typed converter; no bare stride tuple crosses the boundary |
| 4 | Sustained contact step (frankensim/crates/fs-mbd/src/articulated_contacts/step/sustained.rs) |
Fixed material witnesses and a fixed contact frame; a wheel rolling over a sharp lip changes both | Confirmed as a documented scope limit with typed refusals (module header, lines 1–10 and 333–339); capacity 21 at fs-contact/src/sustained/solve.rs:26 |
INT-FSIM-07 | FD-FSIM-12, FD-FSIM-13 | Witness migration in the referee's transactional step (§16); over-capacity refuses |
Row 1, the hand cases. The clipped surrogate is min(ρ·Â, clip(ρ, 1 − ε, 1 + ε)·Â), and the unclipped branch carries the gradient exactly when ρ·Â ≤ clip(ρ)·Â, for either sign of Â. The source tests the opposite inequality when  < 0. Take  = −1 and ε = 0.2. At ρ = 0.5 the two terms are −0.5 and −0.8, the minimum is the clipped term and the gradient is zero, but the code lets it flow. At ρ = 2 the terms are −2 and −1.2, the minimum is the unclipped term, but the code clips. The reported finite differences of the loss in the log standard deviation at ratios 0.5, 1 and 2 are 0, −0.5 and −1 against the code's −0.25, −0.5 and 0. For the critic, the gradient is formed from the value stored during the rollout, and the value returned by the training forward pass is discarded; the reported case is a critic output of 2 with stored value and return 0, where the code's gradient into the critic bias is 0 and the squared-error objective gives 2. For sequences, the reported case is two independently reset one-step episodes whose concatenation gives a frozen policy a second likelihood ratio of 1.582459 where 1 is correct. INT-FSIM-06 has three probes: the four combinations of advantage sign and clip side, each against a finite difference of the scalar loss to 10⁻³ relative in single precision; the critic gradient against the current forward output; and a packed sequence against separate episode replays, ratio 1 to 10⁻⁶. The same three probes are the first tests of this project's own PPO (§23), because a defect this easy to write is easy to write twice.
Row 2, the arithmetic. The step takes its straight branch only when |ω| ≤ 10⁻¹² rad/s. Otherwise it forms θ′ = θ + ω·Δt and returns R·(sin θ′ − sin θ) and −R·(cos θ′ − cos θ). Take θ = 32 rad, wheel speeds 1 and 1 + 6·10⁻¹³ m/s, track 0.5 m and Δt = 1/400 s. Then ω = 1.2·10⁻¹² rad/s, just above the threshold, and ω·Δt = 3·10⁻¹⁵ rad. Half the spacing of doubles at 32 is 2⁻⁴⁸ ≈ 3.55·10⁻¹⁵, so θ′ rounds to θ and both differences are exactly zero. Both wheels advance and the chassis does not move. Over 400 steps the true displacement is one metre along the heading, about (0.83422336, 0.55142668) m. The independent formula is Δp = v·Δt·sinc(δ/2)·(cos(θ + δ/2), sin(θ + δ/2)) with δ = ω·Δt, sinc(x) = sin(x)/x and sinc(0) = 1. Its hand-checkable case: unit speed through a half turn from θ = 0 gives the chord (0, 2/π) m. INT-FSIM-05 tests exact straight travel, the near-zero-curvature case above, wrapped against unwrapped headings, and incremental against one-shot integration to 10⁻¹².
Row 3, the hand case. A contiguous 2×2 single-precision view has strides (8, 4) in bytes and (2, 1) in elements. Copying (8, 4) into an element-stride view over a 16-element buffer addresses element 8 + 4 = 12 at index [1, 1], where element 3 belongs. Both reads are in bounds, so nothing faults. A view with byte origin 4 and strides (8, −4) addresses elements (1, 0, 3, 2), which unsigned strides cannot express. The converter at the export boundary carries the logical origin, the allocation extent, the stride unit and the signedness. A view that the target cannot represent is materialized and the copy is charged to the caller, or refused under a zero-copy contract. A writable view is also checked for independence, separately from bounds: a 2×2 view with element strides (1, 1) maps index [0, 1] and index [1, 0] to one element, so stores of 7 and 11 leave a result that depends on their order. Shared elements are admitted for reads; a write needs an injective index map, a declared reduction or separate storage, and is refused otherwise. Neither library is wrong by itself; the trap is at our boundary.
Row 4, the consequence. The limit is declared upstream and enforced by refusal, which is the behaviour this plan wants from a referee. It still decides what M1 can claim: referee rollouts over planes and primitive obstacles are admitted, and a wheel climbing a riser is admitted only through the event-located transactional step, which localizes new witness pairs at a consistent world contact point and transports or resets tangential memory. INT-FSIM-07 passes when the flat-to-edge-to-top transition returns the typed refusal through the airlock at the pin, and the same transition completes under witness migration with the energy ledger closed to its stated residual.
33.12 The fs-qty coupling and the frob-units escape hatch
The risk, named. Rule L-6 (§34.3) puts fs-qty types in every public signature above layer 1. fs-qty is
the one crate in FrankenSim that enables a nightly feature, generic_const_exprs, which the compiler marks
incomplete (FACT: frankensim/crates/fs-qty/src/lib.rs:20–21; a search of crates, apps and xtask finds no
other crate-level feature attribute). fs-evidence depends on fs-qty directly, and through fs-evidence so
do fs-ivl and nearly every physics crate (§33.3, §33.9). The whole build graph is therefore tied to nightlies
on which an incomplete feature still compiles one crate. The structure of the coupling matters for the upstream
change (FACT to recheck, a reported reading of the dependency graph that this chapter did not repeat;
INT-TOOLCHAIN-01 records it): of 22 crates coupled to fs-qty, 12 depend on it directly and 10 only through
another crate, and removing fs-qty from fs-evidence alone would free 8 of the 22. That is a smaller change
than FD-FSIM-15 and is listed beside it (Appendix F, FD-FSIM-31). The coupling can bite in three ways:
- A toolchain train moves T to a nightly where the feature has regressed. Candidate (a) of §33.13 is such a
move for FrankenSim, from
nightly-2026-07-06tonightly-2026-08-31. - A crate in the graph needs a newer compiler than a nightly on which
fs-qtycompiles. The starting state has this shape: fastmcp_rust declares a minimum of 1.100, and FrankenSim's pin is a 1.99.0 nightly (§33.13). The choice of T and FD-FMCP-01 remove it. - A stable-only target appears. Firmware export M would be one; franken_firmware is on stable 1.99.0.
The test. INT-TOOLCHAIN-01 records a matrix, not one result. The first and last columns are the two candidates for T (§33.13); the middle columns are the present pins of frankensympy and fastmcp_rust, recorded as the starting state:
| Build set | nightly-2026-07-06, candidate (b) |
nightly-2026-08-20 |
nightly-2026-08-25 |
nightly-2026-08-31, candidate (a) |
|---|---|---|---|---|
fs-qty alone |
recorded | recorded | recorded | recorded |
| Bedrock-direct list | recorded | recorded | recorded | recorded |
M1 closure (referee, geometry, ledger) |
recorded | — | recorded | recorded |
Core with the Metal annex (ft-kernel-metal) |
recorded | — | — | recorded |
surface/frob-mcp with fastmcp_rust |
recorded | — | recorded | recorded |
derive/frob-derive with the fsym-* crates |
recorded | recorded | — | recorded |
Every row must pass on the column chosen as T.
The decision rule. T is the first candidate, in the order (a) then (b), on which every row passes, with the
upstream changes that candidate needs (§33.13). If fs-qty compiles on it, nothing else changes. If fs-qty is
what fails on candidate (a), the preferred fix is an upstream change in FrankenSim (FD-FSIM-15 or FD-FSIM-31),
and T is candidate (b) until that change lands and the train to (a) runs. If fs-qty fails on T after a later
toolchain train and the upstream change cannot land within that train, frob-units is created.
The escape hatch, kept cheap from the first commit. DESIGN: the core never imports fs_qty by name outside
frob-core and frob-fsim. Quantity types reach every other crate through one re-export module,
frob_core::qty. While the hatch is closed that module re-exports fs-qty. If it opens, the module re-exports
frob-units instead, and the change is one module plus the conversions in the airlock.
frob-units S, if it exists: layer 0, standard library only, compiles on stable. A dimension is a vector of
six signed 8-bit exponents in the order metre, kilogram, second, kelvin, ampere, mole, which is fs-qty's order
(FACT: fs-qty/src/lib.rs, DIMENSION_COUNT = 6). Typed quantities are a closed set of aliases; products and
quotients among them are generated by a declarative macro, the fallback fs-qty documents for itself. Data
loaded at run time uses a checked quantity that carries its dimension as a value. Conversions to and from
fs-qty live in frob-fsim only, so rule L-2 still holds. Cap: 3 thousand lines.
- Known answers: every alias product agrees with
fs-qtyin a differential test while both exist; a pressure cannot be added to a time (a compile-fail test); a round trip through the airlock conversion preserves the value bits. - Counterexample to the shortcut "a dimension vector is all the typing a quantity needs": a torque and an energy have the same vector (1 in kilogram, 2 in metre, −2 in second), so dimension checking alone cannot separate them. Both crates therefore keep them as distinct aliases over the same dimension, and the test adds a torque to an energy and expects a compile error.
- Gate: the alias set stays at or below 64 (TARGET); above that the macro's product table is no longer reviewable and the question returns to the owner as OPEN-SUITE-4.
- Cost, stated:
frob-unitslosesfs-qty's open-ended dimension arithmetic. A quantity outside the alias set must be added to it or carried as a checked runtime value.
33.13 Toolchain facts across the suite
FACT, read on 2026-11-21 from each repository's rust-toolchain.toml and manifests:
| Repository | Head | Channel | asupersync requirement | Note |
|---|---|---|---|---|
| frankensim | 483d09c682f2 |
nightly-2026-07-06 (rustc 1.99.0-nightly) |
Path ../asupersync; lockfile resolves 0.6.2 |
Its own lock still says 0.5.0 |
| asupersync | b32c5ba66315 |
nightly-2026-08-31 |
It is 0.6.2 | 267 modified paths; franken-kernel and franken-evidence 0.6.0 live here |
| frankensqlite | 79b735cb265a |
nightly-2026-08-31 |
0.6.2 from the registry, default features off |
FrankenSim patches it to the path |
| frankentorch | 8165d6a18028 |
nightly-2026-08-31 |
0.6.2, default features off |
[patch.crates-io] block for metal 0.33.0 |
| franken_numpy | e8cb85f4e5ac |
nightly-2026-08-31 |
=0.6.2, optional |
|
| frankenscipy | edb7ae619c2d |
nightly-2026-08-31 |
0.6.2, default features off |
|
| frankensympy | 29f847c14428 |
nightly-2026-08-20 |
Path ../asupersync |
Two missing pin directories |
| franken_lean | 4426f8ea745a |
nightly-2026-08-31 |
none | SUITE.lock governs its pins |
| fastmcp_rust | 117388bcc169 |
nightly-2026-08-25 |
=0.6.2 |
rust-version = "1.100"; workspace version 0.13.0 |
| frankentui | 5979b92cc576 |
nightly-2026-08-31 |
=0.5.0, optional, behind asupersync-executor |
Version 0.10.0 |
| franken_threed | bf7abe16367e |
nightly-2026-08-31 |
=0.5.0, default features off |
|
| frankenjax | fa93fb775e1c |
nightly-2026-08-31 |
0.5.0, optional |
Uses the third-party egg crate |
| drone reconstruction | db45703afc5e |
nightly-2026-08-31 |
none | |
| franken_textiles | ecb13277aa02 |
nightly-2026-08-31 |
not read | |
| franken_firmware | 151f9ca991e7 |
stable 1.99.0 |
not read | The only stable pin |
Four nightlies and one stable release are in play. That table is the starting state, which the toolchain train, FD-FMCP-01 and FD-ASUP-01 change. Three consequences are DESIGN:
- One toolchain, T, for the whole build graph. T is recorded in
franken-stack.lockand inrust-toolchain.toml. Every crate that anyfrobbinary links builds on T: the core, the GPU annexes, the derivation tool and the MCP server. No annex carries a toolchain file of its own;lean/is not Rust and keeps its own toolchain, andfrob-certbuilds on T in the graph and also alone on a stable release (§34.11). T is chosen at INT-TOOLCHAIN-01 and after that is moved only by a toolchain train: one coordinated change that moves T in this repository and in every consumed sibling that needs it, followed by the admission and parity gates. The candidates, in order of preference:- (a) The suite's common nightly, the one most siblings already pin:
nightly-2026-08-31on the day of writing (asupersync, frankentorch, franken_numpy, franken_lean, franken_threed and others in the table above). It requires advancing FrankenSim's pin fromnightly-2026-07-06in FrankenSim's repository, and moving frankensympy fromnightly-2026-08-20and fastmcp_rust fromnightly-2026-08-25. - (b) FrankenSim's present pin, if FrankenSim cannot yet build on (a). fastmcp_rust's declared
rust-versionand toolchain file are then changed so that it builds on that pin, and the train to (a) is scheduled.
- (a) The suite's common nightly, the one most siblings already pin:
- fastmcp_rust is upgraded to match T, and
frob-mcpis in the core graph. As found, fastmcp_rust declares a minimum of 1.100 and FrankenSim's pin is a 1.99.0 nightly; Cargo refuses such a build unless told to ignore the declared minimum, and this plan does not build on an ignored constraint. The mismatch is fixed in fastmcp_rust. Under either candidate, upstream work item FD-FMCP-01 (P0, at M0) is done by this program in fastmcp_rust's repository, and it is complete when fastmcp_rust's own test suite and its MCP conformance checks pass on T.frob-mcpis then an ordinary member of the core workspace: it linksfrob-verbs, runs verb implementations in process, and shares the one toolchain and the one asupersync package with the rest of the graph (§32.12.2). INT-FMCP-01 is the gate. KILL-MCP names the fallbacks, and fires only if INT-FMCP-01 cannot pass within the M0 budget after FD-FMCP-01 and FD-ASUP-01 have been attempted. - One asupersync version, and 0.5.0 never enters a graph. FrankenSim's constellation, FrankenTorch and
fastmcp_rust are aligned on one published asupersync version by changes in those repositories (FD-ASUP-01,
P0, at M0); INT-ASUP-01 is the gate that proves it. frankentui's executor feature is forbidden, and
frankenjax and franken_threed are never Cargo dependencies.
xtask check-depsenforces all three.
33.14 The worker-process fallback
ADR-SUITE-02: before any FrankenSim source is lifted, the referee moves behind a process boundary. S
What it is. frob-fsim has two build modes behind the same traits. In mode inproc (the default) the adapters
call FrankenSim through path dependencies. In mode remote every volatile fs-* dependency is compiled out and
the adapters speak a job protocol to a worker. The worker is the binary target frob-fsim-worker of the same
crate, built in mode inproc from the small workspace worker/ on FrankenSim's toolchain at the pinned commit.
No new crate is created, and frob-fsim remains the only code that names volatile types. One worker runs per
device or per process slot; the daemon starts, supervises and stops it.
The protocol exchanges whole jobs and bounded chunks. It never carries a per-link, per-ray or per-tick call: the solver and its working set stay together on one side.
job = { job_hash, stack_receipt, model (compiled referee model, canonical bytes), scene, initial_states,
control (a schedule, or a controller program the worker evaluates), horizon, cadence, seeds,
outputs (state columns, events, digests, energy-ledger rows) }
chunk = { job_hash, index, first_step, last_step, columns, events, digest, final: bool }
refuse = { job_hash, code, upstream_reason }
- A job is identified by the BLAKE3 hash of its canonical bytes, and submission is idempotent on that hash.
- Chunks follow a fixed logical partition of the horizon, so a restarted worker regenerates the same chunk boundaries and the client resumes from the last contiguous chunk whose digest it holds.
- The worker reports the stack receipt it was built under. A mismatch with the job's receipt is a refusal
(
FROB-REF-791), not a warning. - Transport is a local socket or a pipe, framed by length, with integers above 2⁵³ as strings where JSON is used and binary columns elsewhere.
What the fallback preserves: the referee is FrankenSim's own code; teleport from a device tier to the referee (a job whose initial state is a snapshot); shadow sampling; promotion. What it costs: a fixed overhead per job, so the referee is called in rollouts and never inside a loop; and a second build to keep, though only at pin moves. What it does not solve: an API change still costs the adapter, but the worker can stay on an old pin while the core moves.
INT-FSIM-18 runs at M0 even though the fallback is not active, because a fallback that has never run is a hope. Pass criteria (TARGET): a 2,000-step G1 referee rollout submitted through the worker returns chunk digests equal, bit for bit, to the same job run in process; killing the worker mid-job and resubmitting returns the same digests; fixed overhead is at most 50 ms per job and at most 5% of wall time on jobs of one second or more. Negative control: a worker built at a different commit refuses the job.
The trigger for fallback (b) is numeric too (DESIGN). If shadowing through the worker falls below 0.1% of device world-seconds at the M2 batch size, which is the bottom of the range §36 gives for a CPU referee, the worker cannot do the referee's job and the lift is considered.
33.15 What the other siblings contribute
Each entry was checked in code, and each has a posture, an admission gate and a fallback. Gate thresholds are TARGETs.
asupersync's lab runtime: deterministic simulation testing of the daemon S. FACT: asupersync/src/lab/ is
about 127 thousand lines; its module header lists virtual time, deterministic scheduling by seed, trace capture
and replay, schedule exploration, test oracles, cancellation injection at await points and chaos injection
(src/lab/mod.rs). It is compiled under the full-runtime feature and re-exports LabConfig and LabRuntime
(src/lib.rs:237, :502). chaos.rs (918 lines), ldfi.rs (567), replay_minimization.rs (991),
dual_run.rs and snapshot_restore.rs exist. Use: every test of frobd's job protocol and of the Chronicle
writer runs under LabRuntime with a recorded seed. Faults are injected by schedule: a kill inside a chunk
write, a cancel at each await point, completions out of order, a storage error. A failing schedule is minimized
and stored as a replay fixture. Device work is represented by a stub whose timing the lab clock controls, and a
dual-run scenario compares the stub against a real device on a small job. Posture: Consume, as a
dev-dependency of frob-chronicle, frob-verbs and frob-conformance; it is the same single asupersync
package. Gate: INT-ASUP-02. Fallback: the chaos tests at kernel-batch boundaries of §38 with a hand-written
virtual clock, which keep fault injection and lose schedule exploration. One caution: lab/conformal.rs (906
lines) calibrates the lab's own oracle metrics and is not a general interval library, so the interval on a
runtime estimate (§32) takes its design from that file and none of its code.
FrankenSQLite's pager policies: eviction for the memo store S. FACT:
frankensqlite/crates/fsqlite-pager/src/s3_fifo.rs (3,058 lines) implements a three-queue policy: a small
admission queue, a main queue with bounded reinsertion, and a ghost queue of metadata, with an adaptive small
share between 5% and 30% and a rollout gate. Sibling files arc_cache.rs and evalue_eviction.rs hold two
further policies. The state machine is keyed on fsqlite_types::PageNumber, so it cannot be instantiated over
content hashes. Use: the memo graph of §28 stores results by content identity and must evict by something
better than recency, since a scan over many designs touches each key once. Posture: Pattern for the policy,
written with the memo graph in frob-verbs; Oracle for the sibling module in frob-conformance. Gate
INT-FSQL-02: under a bijection from keys to page numbers, our eviction sequence equals the sibling's on 10
recorded traces of at least 10⁵ accesses, and on the edit-loop trace the hit ratio is not below LRU's.
Fallback: LRU with admission weighted by recompute cost; never an unbounded store. Entries differ in recompute
cost by orders of magnitude, so the size accounting is in bytes and the admission rule may refuse a cheap
entry; that departure from the sibling's policy is tested separately, not hidden inside the differential test.
frankenjax's e-graph: a pattern, and only if a profile asks F. FACT: frankenjax/crates/fj-egraph exists
(9,408 lines in src/lib.rs), built on the third-party egg crate over frankenjax's own intermediate
representation; frankenjax pins asupersync 0.5.0. Use: none at run time. Extraction over an e-graph could shrink
derived kernel arithmetic beyond common-subexpression elimination. Ceiling, stated before any test: the gain is
at most the arithmetic share of step time multiplied by the reduction in operations, so if the M2 profile puts
arithmetic below 20% of step time, a 10% reduction is worth at most 2% and the item is dropped without a run.
Posture: Pattern. It is never a dependency, because it would add egg and a second asupersync. Pilot and gate
INT-FJAX-01, in the derive/ annex only: with rewrite rules restricted to identities exact over the reals that
also preserve floating-point results under the kernel's determinism class, the extracted kernel matches the
baseline bit for bit on the conformance vectors, and the operation count falls by at least 10% on at least three
kernels. Kill: either condition fails. Fallback: common-subexpression elimination only (fsym-simplify, 3,105
lines, already in the annex).
frankentui: the dashboard F. FACT: version 0.10.0, twenty crates under frankentui/crates, about 1.15
million lines; ftui-runtime carries an optional exact pin on asupersync 0.5.0 behind asupersync-executor
(crates/ftui-runtime/Cargo.toml:56, :81); ftui-harness supports headless tests. Use: frob-tui shows jobs,
races, budgets and gate status. Posture: Consume with default features off and runtime and native-backend
on; the executor feature is forbidden. frob-tui reads the daemon's event stream over the local socket and
links no physics crate. If frankentui does not build on T, the remedy is an upstream change in frankentui or the
toolchain train of §33.13, and until it lands the fallback below applies; the crate gets no toolchain of its
own. Gate INT-FTUI-01: one asupersync package or none in its graph; the job pane
rendered from a recorded event stream equals its stored snapshot in the headless harness; idle processor use at
most 2% of one core. The gate is also the pilot, run on a recorded stream before the crate is funded. Ceiling: a
convenience for a person watching a campaign; no claim and no agent workflow depends on it. Kill: the gate
fails, or frankentui cannot be built without its executor. Fallback: no dashboard; the same events as
line-delimited JSON.
franken_threed: a discipline, and an optional renderer route F. FACT: four crates (f3d-core 10,688
lines, f3d-math 19,100, f3d-graph 7,507, f3d-runtime 31,564). Its status table says: Three.js r186 is
pinned; an ingest command routes an ordinary application's WebGPU renderer to a new backend for an admitted
feature subset; pixel parity holds for ten scenes on a software rasterizer; no hardware run and no speedup have
been measured; single-file packaging is not built (franken_threed/README.md). It pins asupersync 0.5.0. Use:
its DEPENDENCY_ADMISSION.md discipline is already adopted (§33.6). The viewer is an ordinary Three.js r186
page, so it can later be passed through the ingest command. Posture: Pattern now; Subprocess when the viewer's
feature subset is admitted there; never a Cargo dependency. Gate INT-F3D-01: ten reference frames of the replay
page built through the route match the plain bundle within 1/255 per channel on at least 99.9% of pixels, and
an unadmitted feature fails explicitly. Fallback: the plain bundle. Ceiling: this route changes rendering cost
only, and rendering is outside every claim of §39.
franken_drone_geometry_reconstruction: a scan-import lane F. FACT: its status file (snapshot 2026-09-04)
describes an evidence path from recorded-media custody to an audited relative bundle problem, and says it does
not yet optimize cameras, emit metres or publish geometry (IMPLEMENTATION_STATUS.md); its crates hold about 27
thousand lines. The schemas for what it will publish exist: schemas/geometry_generation.schema.json requires
coordinate_frame, scale_status, representations, uncertainty_root, coverage_root and
publication_stage, and schemas/scale_model.schema.json records a scale authority with residuals in parts per
million. Use: a place scanned by a drone or a phone enters Habitat with its coverage and uncertainty attached.
Posture: Pattern today, as a schema adapter in frob-scene with no crate dependency; Subprocess once its
command-line tool publishes geometry. Gate INT-FDGR-01: the schema fixtures validate; a geometry generation
whose scale status is not metric is refused, because a relative scale cannot enter a physics scene; coverage
masks become the scene's unknown-space label, so a clearance certificate treats an unscanned region as unknown
and never as free; and the privacy inheritance of §37 applies to the result. Fallback: mesh and point-cloud
import through fs-io with scale declared by the operator and reality: no-claim. Counterexample to the
shortcut "import the mesh and trust it": a corridor whose far half was never observed appears as empty space in
a naive import, and a traversal certificate over it would be false; with the coverage mask the same query
returns unknown. Pilot: the schema fixtures and the refusal cases, which need no geometry. Ceiling: one import
lane among several; no milestone waits for the sibling to publish geometry. Kill: no published geometry by the
M5 entry review, after which the lane stays a schema adapter.
fastmcp_rust: the MCP server S. FACT: workspace version 0.13.0; the facade package is fastmcp-rust, with
fastmcp-core, -protocol, -transport, -server, -client, -macros, -console and -cli, about 1.23
million lines; ServerBuilder offers new(name, version), tool, resource, resource_template, prompt,
task_supervisor, final_tasks and build (crates/fastmcp-server/src/builder.rs); the task methods
tasks/get, tasks/update and tasks/cancel are served by default (README.md); it pins asupersync =0.6.2
and declares rust-version = "1.100". Use: frob-mcp registers tools generated from the verb registry and
serves catalogs, stills, reports and schemas as resources (§32). Posture: Consume, by surface/frob-mcp, a
member of the core workspace that links frob-verbs and runs verbs in process, once FD-FMCP-01 has brought
fastmcp_rust onto T (§33.13). Gate: INT-FMCP-01. Fallback: KILL-MCP.
Named by the design and not on any critical path.
| Sibling | Checked fact | Posture | Use |
|---|---|---|---|
| franken-kernel 0.6.0 | asupersync/franken_kernel (1,801 lines) defines TraceId, DecisionId, PolicyId, SchemaVersion, Budget and a capability-typed Cx. It has no claim or evidence identifier type. It depends on serde. |
Pattern; Oracle | The text form of artifact-graph identifiers (§34.12). Not linked into frob-core, which admits no serde. |
| franken_textiles | crates/ftx-drape exists, about 116 thousand lines with cloth.rs, contact.rs, integrator.rs; it takes its workspace's exact pin serde_json = "=1.0.151", which cannot share a Cargo graph with FrankenSim's (§33.17, row 7) |
Oracle; Subprocess M | Reference for the cloth evaluation tier, run as a worker process in its own workspace and never as a Cargo dependency. INT-FTX-01: a square cloth draped over a sphere matches ftx-drape's settled shape to its own stated tolerance. Fallback: rigid proxies. |
| franken_firmware | Eighteen crates including franken-hal, franken-control, franken-platform; stable 1.99.0 |
Pattern M | The hardware-abstraction boundary for firmware export. Exported firmware never touches a register, a bus or a stop relay (§37). |
| franken_networkx | fnx-algorithms, fnx-classes and ten more crates |
Not admitted | Tree and cycle algorithms on kinematic graphs are small and are written in frob-design. |
| franken_markdown, frankenmermaid | Present; nightly-2026-08-31 |
Subprocess, optional | Rendering a report is a view. Reports are generated as text by frob-chronicle. |
The five sibling admission gates, as rows. They are defined here, in the form of §33.6. Each is the pilot of its item as well as its gate, and none blocks a milestone.
| Gate | Foundation | Pass criterion | First needed |
|---|---|---|---|
| INT-FTUI-01 | frankentui F | One asupersync package or none in its graph; the job pane rendered from a recorded event stream equals its stored snapshot in the headless harness; idle processor use at most 2% of one core. | M3 |
| INT-F3D-01 | franken_threed F | Ten reference frames of the replay page built through the route match the plain bundle within 1/255 per channel on at least 99.9% of pixels, and an unadmitted feature fails explicitly. | M3 |
| INT-FDGR-01 | franken_drone_geometry_reconstruction F | The schema fixtures validate; a geometry generation whose scale status is not metric is refused; coverage masks become the scene's unknown-space label; the privacy inheritance of §37 applies to the result. | M3 for the schema fixtures; M5 for scan import |
| INT-FJAX-01 | frankenjax F | In the derive/ annex only, with rewrite rules that are exact over the reals and preserve floating-point results under the kernel's determinism class: the extracted kernel matches the baseline bit for bit on the conformance vectors, and the operation count falls by at least 10% on at least three kernels. |
M2 at the earliest, and only if the profile asks |
| INT-FTX-01 | franken_textiles M | A square cloth draped over a sphere matches ftx-drape's settled shape to its own stated tolerance, with ftx-drape run as a worker process in its own workspace (§33.17, row 7). |
M6 |
33.16 Invariants, refusals and open questions
Invariants this chapter maintains, each checked by one of the six checks of §34.6:
- INV-SUITE-01 No crate other than
frob-fsimand the bedrock-direct users names a FrankenSim type (check-deps). - INV-SUITE-02 Every binary links exactly one asupersync package (
check-deps). - INV-SUITE-03 Every recorded gate result cites a resolution receipt, and no PASS is recorded on a dirty
sibling tree (
check-stack). - INV-SUITE-04 No sibling checkout is ever modified or moved by this project's tooling (
check-stackwrites nothing outside this repository, and its test runs it against a copy it cannot write to). An upstream change is made by an agent working in the sibling's repository under that repository's rules (§33.8), never by a tool of this one. - INV-SUITE-05 A result that crossed the multiphysics bridge or came from a worker at a different receipt is never merged into a throughput-tier or same-stack claim (enforced by the evidence types of §12, tested in §38).
Refusals, in the families of §35:
| Code | Name | When |
|---|---|---|
FROB-REF-790 |
foundation-group-absent |
A verb needs an airlock feature group that this binary was not built with |
FROB-REF-791 |
referee-worker-mismatch |
The worker is absent, or was built under a different stack receipt than the job names |
FROB-REF-890 |
stack-mismatch |
Evidence recorded under another stack receipt is offered as same-stack evidence without revalidation |
Open questions (the rule of §42 applies: owner, blocked gate, fail-closed default):
| ID | Question | Default if undecided | Decided by |
|---|---|---|---|
| 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) | INT-ASUP-01 |
| OPEN-SUITE-2 | Decided; 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 (owner, 2026-11-22): 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 |
Decided by the owner; confirmed by INT-TOOLCHAIN-01 and INT-FMCP-01 |
| OPEN-SUITE-3 | Is a dirty asupersync checkout acceptable for development builds between receipts? | Yes for development, with the tree hash in the receipt; no gate records a PASS | INT-FSIM-01; owner |
| OPEN-SUITE-4 | The alias set of frob_core::qty, and whether it stays within 64 |
The quantities used by §13 to §18 only | INT-TOOLCHAIN-01; Marrow lead |
| OPEN-SUITE-5 | Budget for the cold build of the M1 closure on the build workers | The machine envelope: one hour, 16 GiB, 8 cores | INT-FSIM-01; owner |
| OPEN-SUITE-6 | Whether computational crates take asupersync's Cx or a capability-free token from frob-core |
asupersync's Cx wherever cancellation is observed; the token only if INT-ASUP-01 fails after FD-ASUP-01 and a fallback splits the graph |
INT-ASUP-01; Tether lead |
33.17 Further foundation facts and their admission tests
What it is. S Four additions to the table of §33.11 and to the sibling gates of §33.15, each with what was read, the admission test and the interim posture. None was executed for this chapter; the fraction in row 6 is arithmetic on the two constants in the source.
| # | Component | Fact | Read in source on 2026-11-21 | Admission test | Interim posture |
|---|---|---|---|---|---|
| 5 | fs-mbd::Wrench (frankensim/crates/fs-mbd/src/lib.rs:1695–1701) |
The step's external wrench is force_world with torque_body: two frames in one value, unlike fs_ga::Wrench and unlike §11.1 |
Confirmed by reading. The rigid-body type requires the body origin at the centre of mass (lib.rs:582–595) and applies the angular impulse as Δt·R̄·torque_body (:1913) |
A free body at R = R_z(90°) receives a pure world force and a pure body torque through the airlock; linear and angular momentum changes match to 10⁻¹² | A fourth frame type in frob-fsim only, with exactly two constructors |
| 6 | fs_g1_train::gaussian_action (fs-g1-train/src/ppo.rs:172–189) |
Adjacent channels agree in sign with probability 0.6655 where independence gives ½; the marginals are correct | Mechanism confirmed by reading | The joint-law battery of §23 (rule P-12) | Not linked; a planted copy is the negative control |
| 7 | serde_json pins across siblings |
franken_textiles and franken_threed pin =1.0.151; fastmcp_rust pins =1.0.154; frankenscipy requires 1.0.154 or later |
Confirmed in each Cargo.toml; ftx-drape takes its workspace pin |
cargo metadata resolves the graph that INT-FTX-01 needs, or reports the conflict |
ftx-drape is reached as a separate process in its own workspace; f3d-* crates are used with their serde feature off |
| 8 | The metal 0.33.0 binding under ft-kernel-metal 0.1.3 |
Its language-version enumeration ends at Metal Shading Language 3.1. It already exposes indirect thread-group dispatch and thread-group memory length, which the gateway does not wrap | Confirmed in the registry source (metal-0.33.0/src/library.rs:363, src/encoder.rs:1715, :1730) |
INT-FT-01 records the language version the gateway compiles under | Dialect sources use no construct newer than 3.1; the upstream work item (FD-FT-01) wraps the existing bindings |
Row 5, the hand case and the type. Let the body frame be rotated by 90° about z, so that body x is world y. A
caller holding a body-frame wrench with force (1, 0, 0) N means a push along world y. Copied unconverted into
force_world it pushes along world x: the same magnitude, the same energy, a direction wrong by 90°, and nothing
faults. DESIGN: frob-fsim defines MixedWrench { force_world, torque_body } beside the three maps of §11.3. Its
only constructors are from a body wrench at the centre of mass (f_world = R·f_body, torque unchanged) and from a
world wrench at the centre of mass (τ_body = Rᵀ·τ_world, force unchanged). A wrench at any other reference point is
first moved by the pushforward of §11.3. No other crate names the type.
Row 7, the consequence. A Cargo graph holds one version of serde_json 1.x. The cloth oracle of §33.15 cannot
be a dependency of a crate that also links FrankenSim, whose graph resolves 1.0.154. INT-FTX-01 therefore runs
ftx-drape as a worker process that exchanges whole jobs, the posture §33.14 already defines for FrankenSim, until
the pin is relaxed in franken_textiles. That change is upstream work item FD-FTX-01 (Appendix F).
Row 8, a reported fact to recheck. A compile probe on this M5 Ultra is reported to show that Metal Shading Language 3.2 and 4.0 provide no 64-bit integer atomic add and no 64-bit compare-and-swap (FACT to recheck; the fingerprint of §21.16 re-runs it). The consequence for kernels is in §21.
| GATE-WS-06 | Known answer. The mixed-wrench probe passes and its unconverted mutant fails; the planted sampler is rejected by rule P-12; xtask check-deps reports exactly one serde_json version per binary and fails a graph that adds ftx-drape to the core workspace; the Metal language version and the 64-bit atomic probe are recorded in the fingerprint. M0; the sampler row at M2. |
33.18 Six later foundation facts and their admission tests
What it is. S Six rows that continue the tables of §33.11 and §33.17, each with what was read, the admission test and the interim posture. They are counted separately from the five defects or limits and the one convention hazard of §33.11. Rows 9, 10, 12 and 13 are limits or defects; rows 11 and 14 are convention hazards. Nothing was executed for this section: each mechanism was read in source on 2026-11-21, the sum in row 9 was computed from the source table, and reported values are marked.
| # | Component | Fact | Read in source | Admission test | Interim posture |
|---|---|---|---|---|---|
| 9 | fs-mbd::robot_models, the G1 catalog (frankensim/crates/fs-mbd/src/robot_models.rs:398–403) |
The builder keeps 30 links and omits fixed attachments with nonzero mass. Reported: 1.377 kg over four welded links, against a 38-link source of 33.34014202 kg | The omission is stated in the builder's own list. The 30 masses sum to 31.96314202 kg. The upstream figures were not re-read | The mass roll-up through the airlock equals 31.96314202 kg, and the reduction lists its omissions | Used as the reduced profile of §14, never as the import-parity reference |
| 10 | fs_ga::Se3::left_jacobian, right_jacobian (fs-ga/src/lie.rs:46, :1044–1049) |
The series refuses when the infinity norm of ad exceeds 32, so a pure translation of 33 m returns IllConditioned, a pose that Se3::exp accepts and that is regular |
Confirmed: SE3_SERIES_MAX_AD_NORM = 32.0, and the refusal precedes the series. exp has no such limit (:766–776) |
The public paths at translations of 1 m and 33 m, against the closed form below | frob-lie owns the differentials in closed form (§13); a limit of an owner is reported as unsupported, never as a singular pose |
| 11 | fs_phs::transformer and interconnect_mapped (fs-phs/src/interconnection.rs:91) |
Opposite signs of the driven direction; both conserve power | Confirmed by the source comment. The rates (12, −8) and (−12, 8) are reported | The signed motion witness of §15 through the airlock, for both entry points | Only interconnect_mapped is reached, with the authored sign passed explicitly |
| 12 | fs_contact::broad_phase::swept_sphere_aabb (fs-contact/src/broad_phase.rs:146–156) |
Encloses straight centre motion only | Confirmed as a documented scope limit | The arc fixture of §18: the helper's bound misses the obstacle, and the arc-aware bound contains it | frob-contact builds its own bounds for rotating links |
| 13 | fs-sos (fs-sos/src/lib.rs:80–84, :289–308) |
Two cases in which a returned value is not a bound. Poly::new trims trailing coefficients below 10⁻¹⁵ in magnitude, so 1 − 2⁻⁵⁰·x becomes the constant 1 and is certified as 1 on abs(x) ≤ 2²⁸, where the minimum is 1 − 2⁻²². certified_bound_on forms its result by one subtraction rounded to nearest, and returns 1 for 1 − x/2 on abs(x) ≤ 2⁻⁵⁵, where the minimum is 1 − 2⁻⁵⁶ |
Both mechanisms confirmed by reading. The two returned values are reported and were not re-run | Both probes through the airlock, each compared with exact rational evaluation of the authored polynomial at the interval's ends | No fs-sos value enters a certificate. The sos-gram kind is checked in exact rationals (§12.4); a bound that is used as evidence is recomputed with the authored coefficients and an outward-rounded last step |
| 14 | f3d_math::Ray::apply_matrix4 (franken_threed/crates/f3d-math/src/ray.rs:487–490, vector3.rs:708–719) |
The transformed direction is renormalized, so hit parameters under a scaled instance are in local units | Confirmed by reading | The two-plane fixture of §19 through the adapter | The adapter converts by s_W = s_L/‖A⁻¹·d‖ |
Row 10, the closed form and the hand case. For a pure translation the twist has zero angular part, ad² = 0, and the left and right differentials of the exponential are exactly I + ad/2 and I − ad/2, both with determinant one. For a translation of 33 m along +x and a unit rotation rate about +z, the linear y component is −16.5 m in one and +16.5 m in the other. A warehouse aisle is longer than 32 m, so a refusal there would exclude ordinary poses. The anchored coordinates of §11 keep translations inside a cell small, but a relative pose between two bodies in one aisle is not anchored.
Row 13, why it matters although no certificate depends on it. §25.4.9 and C-32 name fs-sos as an owner worth
probing, and §22.12.4 cites its region-of-attraction routine. A value from it is a proposal to check. Two rules follow
for any bound this project accepts from a floating-point routine: the bound is evaluated on the authored coefficients,
or the error of translating them is bounded on the actual domain; and the last operation is rounded outward.
Upstream work items, added to Appendix F by description: fold or declare the omitted masses of the G1 catalog; a
closed-form differential for small rotation and large translation; a documented or removed legacy transformer; an
arc-aware swept bound; an authored-coefficient check and an outward-rounded result in fs-sos; a ray transform that
returns the scale of its parameter. Each is done in the sibling's repository under its rules (§33.8), and the interim
postures above hold until it lands.
| GATE-WS-09 | Known answer. Each of the six admission tests is recorded at the pin with its result: the roll-up of 31.96314202 kg; the refusal at 33 m and the agreement at 1 m to 10⁻¹², with the closed form returning ∓16.5 m; the signed motion witness for both transformer entry points; the arc fixture; the two fs-sos probes compared with exact evaluation; the two-plane ray fixture. A probe that now passes upstream is recorded as fixed and its interim posture is reviewed. M0, with rows 12 and 14 at M2. |