Introduction and contents
968 words1 subsection1 tablePlan version 1.1
On this page1
COMPREHENSIVE PLAN FOR FRANKEN_ROBOTICS
FrankenRobotics is a robot proving ground, a robot design studio for AI agents, and a mission-query engine, built as one mathematical instrument. It simulates legged, wheeled, tracked and hybrid robots in terrain and interior scenes with physics supplied by FrankenSim, runs thousands of worlds and hundreds of different robots at once on CUDA and Metal GPUs, and exposes a command line and an MCP server through which agents design a robot, test it, read what happened and improve it. It answers questions about families of designs and not only about single designs: which bodies can do this mission, which cannot and why, and which experiment would settle the rest. It searches for the worlds that break a design, shrinks each failure to a minimal counterexample world, and explains a failure by intervening on a replay of it. It carries a path from simulation to calibration against measured reality and to manufacturable output. Every layer is formulated in Lie theory and abstract algebra: configurations are group elements, joints are subgroups, contact is a cone program in the dual Lie algebra, symmetry is a finite group acting on the design, and the hot kernels are derived from that algebra instead of being typed in by hand. Repo
franken_robotics; crate prefixfrob-; binariesfrob(CLI),frobd(job daemon),frob-mcp(MCP server),frob-verify(offline certificate auditor) andfrob-tui(terminal dashboard).
| Document | COMPREHENSIVE_PLAN_FOR_FRANKEN_ROBOTICS.md |
| Version | 1.1. Version 1.0 replaced version 0.2 and absorbed the review, audit and pilot evidence recorded in §0.6, §0.8 and Appendix K; 1.1 applies the owner's ruling that siblings are changed and not worked around (Appendix K, round 13) |
| Date | 2026-11-22 (drafted 2026-11-21 and 2026-11-22; the evidence it cites was gathered on 2026-11-21) |
| Status | Plan stage. Nothing in this document is implemented in the §0.2 sense. The repo holds plans and no code. The paper-scale checks behind this version ran no FrankenRobotics code, because none exists |
| Language | Rust 2024 on one pinned dated nightly, the toolchain T chosen at INT-TOOLCHAIN-01 (§33.13), for every crate a frob binary links; one shared C-dialect kernel source for CUDA and Metal; frob-verify uses the standard library only |
| Foundations | frankensim, frankentorch, franken_numpy, frankensympy, franken_lean, frankenscipy, asupersync, frankensqlite, fastmcp_rust, franken_threed |
| Hardware targets | Linux x86-64 with two RTX 4090, 24 GB each, with no link between them (host trj); Apple silicon with Metal (this Mac Studio: M5 Ultra, 36 CPU cores, 80-core GPU, 256 GB of unified memory) |
| Acceptance | The ten-fold test of §39: a ratio of restricted mean times to an independently accepted answer, against the strongest composed rival, on a sealed suite. A partial gate at M3 and the tournament at M7 |
| Next step | External review rounds on this version; the incumbent audit and phase ledger of M0 (§39); the paper-scale pilots that fund Frontier and Moonshot work (§0.7); then conversion to beads (§45) |
Contents
- Part 0. Document control: §0.1 labels and tiers · §0.2 what "implemented" means · §0.3 identifier prefixes · §0.4 reading guide · §0.5 subsystem names · §0.6 how this plan was produced · §0.7 plan hygiene rules · §0.8 how evidence binds the plan
- Part I. Thesis: §1 What exists, what is missing, what this is · §2 The ten-fold thesis · §3 Twelve principles · §4 Bets, each with its falsifier · §5 Readers · §6 Goals, non-goals, anti-goals · §7 North-Star scenarios · §8 The seven claims and the claim product
- Part II. The mathematical spine: §9 Doctrine · §10 The constructions (C-01 onward) · §11 Conventions · §12 Lemma: proofs, certificates, the offline auditor
- Part III. The body: §13 Marrow: the algebraic core · §14 Skeleton: design language, modules, archetypes, preflight · §15 Sinew: actuators, transmissions, power · §16 Kinesis: dynamics on three tiers · §17 Phylum: families of bodies in one batch · §18 Traction: collision, contact, wheels, tracks, terrain · §19 Habitat: scenes, living worlds, clearance, retrofits · §20 Sensorium: sensors, clocks, observability · §21 Spark: GPU backends and the kernel toolchain
- Part IV. The mind: §22 Reflex: estimation, control, gaits, skills, shields · §23 Cortex: the gym, learning, family policies, inheritance · §24 Arena: tasks, requirements, fixtures, metrics, qualification · §25 Augur: mission queries and inverse design · §26 Nemesis: adversarial worlds and rare failures · §27 Autopsy: counterfactual debugging · §28 Atelier: the studio loop, analyses, comparison, lineage, cascade, decision cores
- Part V. The record and the world: §29 Chronicle: telemetry, replay, evidence · §30 Ground: calibration against reality · §31 Foundry: structure, manufacture, lifecycle · §32 Tether: CLI, daemon, MCP, dashboard, viewer
- Part VI. Substrate and engineering: §33 Suite consumption · §34 Workspace, crates, formats · §35 Numerics and determinism · §36 The performance program · §37 Safety, security, privacy
- Part VII. Verification, the ten-fold test, gates and risks: §38 Gauntlet: the verification program · §39 The ten-fold test · §40 The gate register · §41 Risks and the pre-mortem · §42 Open questions
- Part VIII. Delivery: §43 Milestones M0–M8 · §44 Work packages · §45 The beads · §46 The first implementation session · §47 Definition of done and the release rubric
- Appendices: A glossary · B idea passes · C EV matrix and killed-idea register · D mathematics compendium · E worked cards · F upstream work items · G robots, scenes, licences, hazard lists · H source register · I type sketches · J verb registry · K review log · L worked artifacts · M known-answer suite · N counterexample catalogue · O refusal code registry