FrankenRobotics

Upstream work items

4,101 words3 subsections2 tablesPlan version 1.1

On this page3
F.1 The registerF.2 The reported foundation defects, as defect reportsF.3 What the upstream work items do not change

The rule. Every sibling repository this plan consumes is the owner's, and this program changes it where it needs changing (§33.8, §37.8). An upstream work item is a change this program makes in the sibling's repository, under that repository's own AGENTS.md, gates and conventions. It is a bead in this program's graph with the label upstream, mirrored as a bead in the sibling's own tracker (BD-037), and recorded in registries/upstream.toml with five things: the change, a priority, the interim posture here, the switch-over rule, and one reproducible failing fixture. No milestone waits on an upstream change landing, and no local patch or fork stands in for one. A defect found in a sibling becomes an admission test here and an upstream work item there, in that order: the admission test records what the pinned commit does, and the upstream work item describes the change.

Upstream changes are additive: a new mode, entry point, type or feature, never a change to existing behaviour, with any lossiness self-described (DESIGN, following the rule FrankenSim's own extension plans set for upstream work). They follow the sibling's rules. For FrankenSim those include its layer checks, its contracts, its unsafe-capsule discipline, its ban on in-process foreign kernels in production paths and its ban on branches and worktrees. Other agents work in the same repositories, so an upstream change reserves its files through Agent Mail and follows the sibling's own coordination rules before it edits. The priority states the value of the item to this project and orders it in this program's queue; the two P0 items are done at M0. The interim posture is what FrankenRobotics does until the change lands. The switch-over rule is what must be re-run when it does; a pin then advances through the compatibility train of §33.8 (move the pin, write a new receipt, rerun the admission and parity gates, relock).

Third-party gaps are not upstream work items. The cudarc bindings for graph capture and asynchronous pools (OPEN-SPARK-4) are confirmed or refuted at INT-CUDA-01, and the annex binds the driver directly where a binding is missing.

Identifiers FD-FSIM-01 to -09, FD-FT-01 to -03, FD-FSYM-01 to -05, FD-FLN-01, -02 and FD-ASUP-01 keep their earlier meaning. FD-FSIM-10 to -16, FD-FNP-01, FD-FSQL-01, FD-FMCP-01, FD-FTUI-01 and FD-FKER-01 are the upstream work items of §33.8. FD-FSIM-17 to -30, FD-FDGR-01 and FD-FSS-01 number the changes that subsystem chapters raised without a number. FD-FSIM-31 to -33, FD-FTX-01 and FD-F3D-01 are the upstream work items that follow from the coupling note of §33.12 and the foundation facts of §33.17.

F.1 The register

Upstream work item Repo Change Priority Interim posture here Switch-over rule
FD-FSIM-01 frankensim Spherical, universal, planar and cylindrical joints in fs-mbd or the proposed fs-kinematics P1 The referee lowers them to products of one-axis joints (§16.4) Re-run GATE-KIN-02, -03
FD-FSIM-02 frankensim A persistent contact time stepper (its open Moreau–Jean and barrier lanes) P1 frob-dyn owns the transaction, warm starts, friction memory and the commit fence (§16); barrier contact is not built here Re-baseline the fidelity ledger once
FD-FSIM-03 frankensim Support maps for capsules and convex hulls; heightfield and distance-field pair gaps; contact generation beyond endpoint gap checks P1 frob-contact generates contact sets and fs-contact::certified_ccd audits the path; parity only where both apply Re-run GATE-TRAC-02
FD-FSIM-04 frankensim Holonomic loop constraints and nonholonomic rolling in fs-mbd P2 Compliant equality rows on fast tiers; no exact loops on the referee Add exact-closure known answers
FD-FSIM-05 frankensim Adjoints through the articulated and contact steps P3 Derivative programs from frob-kir on smooth kernels; estimators through contact, each with a derivative label (§16) Compare gradients
FD-FSIM-06 frankensim One vector vocabulary across fs-mbd and fs-ga P2 The airlock converts Delete conversions
FD-FSIM-07 frankensim Deterministic elementary functions and cancellation checkpoints inside fs-mbd P2 The referee claims same-platform determinism only (§35) Add cross-ISA lanes to G5
FD-FSIM-08 frankensim Freeze the Component trait as contract v1 P1 The airlock adapts v0 Re-run functor laws
FD-FSIM-09 frankensim A home for device receipts (fields AE-01 to AE-12) in its evidence types P3 Local types with the doctrine's field names Replace local types
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 (F.2, row 1) P2 Not a dependency, not an oracle, not a baseline; PPO is written here and passes the same three probes first (§23) 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 (F.2, row 2) P2 Known answers for wheeled bases use the independent formula in frob-conformance 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 (F.2, row 4) P1 The referee's transactional step migrates witnesses above the airlock (§16.5, §18.4) Re-baseline the fidelity ledger once
FD-FSIM-13 frankensim A sustained solve above 21 contacts, an island-wise solve, or a documented patch model with a qualification fixture P1 Over-capacity sets refuse by name; patch reductions are declared (§18) 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 in .cargo/config.toml; 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 INT-TOOLCHAIN-01 forces it (§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-FSIM-17 frankensim fs-uq: a batched entry point for multilevel estimation (its driver takes a per-call closure) and importance sampling beyond Gaussian germs P2 The coupled estimators of §16.8 and §29.11 are ours; fs-uq supplies allocation and control-variate arithmetic only Re-run GATE-CHRON-09 with the sibling driver; keep ours if the intervals differ
FD-FSIM-18 frankensim Lift or parameterize the 10⁶ sample caps in fs-eproc's Bernoulli sequence and in fs-uq's importance execution P3 Our own exact binomial bound for larger counts; claims certified to 10⁻⁵ and reported as Estimated beyond (OPEN-NEMESIS-3, -4) Re-run GATE-NEMESIS-05 at the larger count
FD-FSIM-19 frankensim A splitting estimator (adaptive multilevel splitting) beside the existing importance sampler P3 Splitting is implemented in frob-nemesis with its unbiasedness fixture (§26.9) Differential test of the two estimators on the random-walk fixture, then choose one
FD-FSIM-20 frankensim Derivatives of the articulated dynamics with respect to state and design, and a hybrid multiple-shooting solver on articulated models (fs-orbit, fs-mbd) P3 The compliant-tier orbit route is ours and comes first; the referee orbit route waits (§22.9) Re-run GATE-GAIT-01, -02 on the referee route
FD-FSIM-21 frankensim A second polarization pair for the battery element of fs-phs P3 An in-house f64 reference until it lands (OPEN-SINEW-4) Re-run GATE-SINEW-07 against the sibling element
FD-FSIM-22 frankensim Dynamic rods (fs-solid has geometrically exact rods for statics) and a batched cloth P3 Rigid proxies S; chain cords and hinged plates F; rods and cloth stay M and off the critical path (§19.10) Re-run the proxy-adequacy pilot of §19.10.7 against the new owner
FD-FSIM-23 frankensim fs-assimilate: a windowed or streaming entry to the iterated update beyond 256 rows P3 Traces enter as windows of summary features, and the window definition is part of the calibration record (§30.9) Re-fit one recorded dataset both ways and compare posteriors
FD-FSIM-24 frankensim fs-assimilate: a cross-ISA statement for the ensemble lane P3 Ensemble results are recorded with the machine fingerprint and are not compared across machines Re-run the replay known answers of §30.21 on a second machine and record the comparison in the calibration record
FD-FSIM-25 frankensim fs-asbuilt: a correspondence-search lane (it registers by a closed-form rigid fit with supplied correspondences) P3 Datums and fiducials are placed at design time so correspondences are known (§31.12) Re-run the as-built known answers without fiducials
FD-FSIM-26 frankensim fs-io: a mesh entry point to the faceted STEP exporter P3 Faceted export under a stated triangle bound, with decimation and re-check or refusal (§31.12) Re-export the packet fixtures and compare hashes
FD-FSIM-27 frankensim fs-topols: a plane-stress option P3 Three-dimensional runs only; thin plates are checked by the independent solver Add the plane-stress known answer
FD-FSIM-28 frankensim fs-topopt::sdf3: a stable, ungated surface P3 Reached behind its feature through the airlock, pinned by commit Remove the feature gate from the airlock entry
FD-FSIM-29 frankensim fs-fab: geometric evaluators for overhang and tool access P3 frob-foundry owns the evaluators and reports review: no-claim Differential test, then delete the local evaluators
FD-FSIM-30 frankensim fs-mesh: a statement of boundary conformity P3 Conformity is measured per mesh and recorded with the structural evidence Replace the measurement with the stated bound where it applies
FD-FSIM-31 frankensim Remove the fs-qty dependency from fs-evidence, or put it behind a feature. Reported to free 8 of the 22 crates coupled to fs-qty, of which 12 depend on it directly and 10 through another crate (FACT to recheck, §33.12); a smaller change than FD-FSIM-15 P2 As FD-FSIM-15: the frob_core::qty re-export, and frob-units if INT-TOOLCHAIN-01 forces it Re-run INT-TOOLCHAIN-01 and re-read the list of coupled crates
FD-FSIM-32 frankensim Correct fs_g1_train::gaussian_action so that action channels are drawn independently: adjacent channels now agree in sign with probability 0.6655 where independence gives ½, with correct marginals (F.2, row 6) P2 Not linked; a planted copy is the negative control of the joint-law battery (§23.25, rule P-12) Re-run the joint-law battery against the corrected sampler; only then may it serve as a comparison baseline
FD-FSIM-33 frankensim Document the mixed frames of fs-mbd::Wrench (force_world with torque_body) at the type, or add named constructors from a body wrench and from a world wrench (F.2, row 5) P2 MixedWrench in frob-fsim with exactly two constructors; no other crate names the type (§33.17) Replace the local type; re-run the mixed-wrench probe of GATE-WS-06
FD-FT-01 frankentorch Metal gateway: asynchronous completion with several command buffers in flight; an interruptible wait; typed buffers beyond f32 and u32; binding at a byte offset; relief from the 31-argument limit; function constants; a binary archive and ahead-of-time compilation; private storage with blits; per-kernel timing in the receipt; Metal 4 command allocators; migration to objc2-metal. Part of this is wrapping and not new binding work: the metal 0.33.0 binding under the gateway already exposes indirect thread-group dispatch and thread-group memory length (§33.17, row 8), and is reported to expose blit encoders and binary archives (FACT to recheck) P1 Packed slabs indexed through an offset table; one synchronous batch per chunk of control intervals; one blocked host thread per device; source recompiled from a cached digest; a watchdog on the wait (§21.9) Re-run INT-FT-01, INT-FT-02, GATE-SPARK-02, -04
FD-FT-02 frankentorch Real device execution for tensors and autograd P2 On-device learning kernels in the shared dialect; FrankenTorch is the CPU trainer, the gradient oracle and the interchange format (§23.8) Gradient parity (GATE-CORTEX-02), then switch the trainer
FD-FT-03 frankentorch A CUDA gateway mirroring the Metal gateway P2 spark/frob-spark-cuda on cudarc Re-run GATE-SPARK-02, -03
FD-FNP-01 franken_numpy and frankentorch A named conversion between signed byte strides and unsigned element strides, with the unrepresentable cases refused (F.2, row 3) P2 A typed converter at our boundary; no bare stride tuple crosses it Replace the local converter; re-run INT-FNP-02
FD-FSYM-01 frankensympy Multi-output straight-line code generation with common-subexpression elimination; lift the 8,192-operation cap P2 frob-kir owns code generation Regenerate and compare digests
FD-FSYM-02 frankensympy A Lie-algebra module: structure constants from a matrix basis, ad matrices, BCH coefficients P3 Explicit matrices in derive/frob-derive —
FD-FSYM-03 frankensympy Permutation groups and character tables in Rust P3 Small-group code in frob-algebra Cross-check tables
FD-FSYM-04 frankensympy Certificate families for matrix identities and for sums of squares with rational Gram matrices P2 Entry-wise polynomial identities; the sos-gram proof kind stays F Re-issue certificates
FD-FSYM-05 frankensympy Faster Gröbner bases and multivariate resultants P3 Inverse kinematics and exact synthesis limited to leg-sized systems —
FD-FLN-01 franken_lean Unblock the Mathlib roots for matrix exponentials, Lie groups, analytic quaternions and representation theory P3 The algebraic route; only order-theory closures are used in Lean Promote selected cards from Certified to Proved
FD-FLN-02 franken_lean Certify its suite lock on macOS aarch64 P3 Lean work on a Linux host —
FD-ASUP-01 asupersync, frankensim, frankentorch and fastmcp_rust One published asupersync version that FrankenSim's constellation, FrankenTorch and fastmcp_rust all pin, obtained by changes in those repositories P0, at M0 One package identity per build stays enforced by check-deps; a surface that would bring a second package stays out of the core graph under KILL-MCP's first fallback INT-ASUP-01 passes on the whole graph: cargo tree -d shows no duplicate
FD-FMCP-01 fastmcp_rust Bring fastmcp_rust onto T, the one toolchain of the build graph (§33.13): 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) 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 surface/frob-mcp in the core graph on T
FD-FSQL-01 frankensqlite Make the S3-FIFO state machine generic over its key type P3 The pattern, with a differential oracle (INT-FSQL-02) Consume it; delete the local copy
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) Claim and evidence identifier types beside TraceId, DecisionId and PolicyId P3 Local ClaimId and EvidenceId in frob-core with the same text form Replace local types
FD-FDGR-01 franken_drone_geometry_reconstruction Publish geometry: optimized cameras, metres with a scale witness, coverage and uncertainty per region P3 scene.import consumes the twin package first; scale is declared by the operator (OPEN-HAB-5) Run INT-FDGR-01, then GATE-HAB-03 on one capture
FD-FSS-01 franken_surveillance_system In the twin package: four non-coplanar landmarks, a scale witness, and coverage or confidence per region. Conditional: opened only if the inspection pilot of §19.13 finds them missing P3 A tape-measure survey authored in the interior grammar, every dimension recorded as measured Re-run GATE-HAB-03 with a scale label of witnessed or better
FD-FTX-01 franken_textiles Relax the exact pin serde_json = "=1.0.151" to a range that admits the version FrankenSim's graph resolves (1.0.154, through FrankenSciPy) P3 ftx-drape runs as a worker process in its own workspace; it is never a Cargo dependency (§33.17, row 7) Re-run INT-FTX-01 with ftx-drape as a dev-dependency of frob-conformance; keep the worker if cargo metadata still reports a conflict
FD-F3D-01 franken_threed The same relaxation of its exact pin serde_json = "=1.0.151" P3 f3d-* crates are used with their serde feature off; the renderer route is a subprocess Re-run INT-F3D-01

Counts (FACT about this table): 53 upstream work items, of which 33 are in frankensim, 3 in frankentorch, 5 in frankensympy, 2 in franken_lean, and one each in ten other repositories or groups of repositories. Two are P0, eight P1, sixteen P2 and twenty-seven P3.

F.2 The reported foundation defects, as defect reports

Five defects or limits were reported in components this plan stands on (§1.7, §33.11, §33.17): rows 1 to 4 and row 6 below. Row 5, the mixed-frame wrench, is a convention hazard beside them. Each is FACT to recheck: the "read in source" column is what a reading on 2026-11-21 confirms, and a reported number stays a report until its admission test records it at the pinned commit. None was re-executed for this plan.

# Component Reported behaviour Read in source on 2026-11-21 Smallest reproducing case Admission test and pass condition Upstream work item Interim posture here
1 fs_g1_train::ppo_update (frankensim/crates/fs-g1-train/src/ppo.rs:253–345) Three errors in a PPO update: the clip branch is reversed for negative advantage; the critic gradient is formed from the value stored at collection and ignores the current output; two reset episodes concatenated are forwarded as one sequence The first two are confirmed by reading (lines 322–326 and 340). The third is consistent with line 309; its number was not re-run  = −1, ε = 0.2: at ρ = 0.5 the 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. Reported finite differences in the log standard deviation at ratios 0.5, 1 and 2: 0, −0.5, −1 against the code's −0.25, −0.5, 0. Critic output 2 with stored value and return 0: code gradient 0, objective gradient 2. Two reset one-step episodes: second likelihood ratio 1.582459 where 1 is correct INT-FSIM-06, three probes: the four combinations of advantage sign and clip side against a finite difference of the scalar loss to 10⁻³ relative in single precision; the critic gradient against the current forward output; a packed sequence against separate episode replays, ratio 1 to 10⁻⁶ FD-FSIM-10 Not linked, not an oracle, not a baseline. The same three probes are the first tests of this project's own PPO (GATE-CORTEX-07)
2 fs-mbd::planar_drive (frankensim/crates/fs-mbd/src/planar_drive.rs:117–133) A planar-drive integration defect: near-straight motion at a large heading returns zero translation The mechanism is confirmed by reading and by the rounding arithmetic; the run was not repeated θ = 32 rad, wheel speeds 1 and 1 + 6·10⁻¹³ m/s, track 0.5 m, Δt = 1/400 s: ω = 1.2·10⁻¹² rad/s exceeds the 10⁻¹² threshold, ω·Δt = 3·10⁻¹⁵ rad is below half the spacing of doubles at 32 (2⁻⁴⁸ ≈ 3.55·10⁻¹⁵), θ′ rounds to θ and both differences are exactly zero. Over 400 steps the true displacement is about (0.83422336, 0.55142668) m INT-FSIM-05: exact straight travel; the near-zero-curvature case; wrapped against unwrapped headings; incremental against one-shot integration to 10⁻¹², all against Δp = v·Δt·sinc(δ/2)·(cos(θ + δ/2), sin(θ + δ/2)) with δ = ω·Δt FD-FSIM-11 The independent formula lives in frob-conformance; planar_drive is not an oracle until the test passes
3 Strides in fnp-ndarray and ft-core A stride-convention trap: signed byte strides on one side, unsigned element strides on the other; a verbatim copy reads the wrong element in bounds Both conventions are confirmed (fnp-ndarray/src/lib.rs:258, :390; ft-core/src/lib.rs:397, :2460); the wrong read was not executed. Neither library is wrong alone; the trap is at the boundary A contiguous 2×2 single-precision view has strides (8, 4) in bytes and (2, 1) in elements. Copying (8, 4) as element strides over a 16-element buffer addresses element 12 at index [1, 1], where element 3 belongs. A view with byte origin 4 and strides (8, −4) addresses elements (1, 0, 3, 2), which unsigned strides cannot express INT-FNP-02: the conversion at the interchange boundary reads element 3, not element 12; the negative-stride view is materialized with the copy charged to the caller, or refused under a zero-copy contract (FROB-REF-617) FD-FNP-01 A typed converter that carries the logical origin, the allocation extent, the stride unit and the signedness
4 Sustained contact step (frankensim/crates/fs-mbd/src/articulated_contacts/step/sustained.rs; fs-contact/src/sustained/solve.rs:26) A fixed-witness assumption: fixed material witnesses and a fixed contact frame, where a wheel rolling over a sharp lip changes both; capacity 21 contacts Confirmed as a documented scope limit with typed refusals (module header, lines 1–10 and 333–339) A wheel rolling from a flat onto an edge and then onto the top of a riser INT-FSIM-07: 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. INT-FSIM-04: a set of 22 contacts returns a typed refusal FD-FSIM-12, FD-FSIM-13 Witness migration in the referee's transactional step; over-capacity sets refuse. Referee rollouts over planes and primitive obstacles are admitted at M1; a wheel climbing a riser is admitted only through the event-located step
5 fs-mbd::Wrench (frankensim/crates/fs-mbd/src/lib.rs:1695–1701) A convention hazard, not a defect: 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 body frame rotated by 90° about z: a body-frame force (1, 0, 0) N means a push along world y; copied unconverted into force_world it pushes along world x, with the same magnitude and energy, and nothing faults The mixed-wrench probe of GATE-WS-06: a free body at R = R_z(90°) receives a pure world force and a pure body torque through the airlock, and the linear and angular momentum changes match to 10⁻¹²; the unconverted mutant fails FD-FSIM-33 MixedWrench in frob-fsim only, with exactly two constructors
6 fs_g1_train::gaussian_action (fs-g1-train/src/ppo.rs:172–189) The action sampler's joint law: adjacent channels agree in sign with probability 0.6655 where independence gives ½; the marginals are correct The mechanism is confirmed by reading; the fraction is arithmetic on the two constants in the source and was not executed The sign-agreement fraction of two adjacent action channels over many draws The joint-law battery of §23.25 (rule P-12, GATE-CORTEX-18); the planted sampler is rejected (GATE-WS-06) FD-FSIM-32 Not linked; a planted copy is the negative control

F.3 What the upstream work items do not change

  • M1 depends only on FrankenSim, asupersync and FrankenSQLite (§33.7). No upstream work item is on the M1 critical path.
  • If no upstream work item has landed, the plan still ships: the referee lowers joints, owns its transaction and migrates witnesses; the Metal backend runs inside the gateway's present limits; and if the two P0 items cannot land within the M0 budget, KILL-MCP's fallbacks apply, frob-mcp as its own workspace over a local socket and then the CLI alone. The costs are named in the interim-posture column and in KILL-FSIM, KILL-METAL and KILL-MCP.
  • An upstream change that lands is adopted only through its switch-over rule. A sibling's newer clean head is never rolled back locally, and neither a pin nor T moves during the ten-fold tournament (§39).