Subsystem names
533 words1 tablePlan version 1.1
FrankenRobotics assembles a creature from parts, so the subsystems are named for the parts, for what the creature
does, and for what is done to it. The names are handles for agents to talk to each other; the crates are in §34.
surface/frob-mcp is a member of the core workspace. The annex paths (spark/, derive/, bindings/, viewer/,
lean/) are separate workspaces or projects (§34.1).
| Subsystem | Bounded context | Primary crates | Chapter |
|---|---|---|---|
| Marrow | Lie groups and algebras, finite groups, cones, order theory | frob-lie, frob-algebra |
§13 |
| Skeleton | The robot design language, modules with port contracts, archetypes, preflight, the model compiler | frob-design, frob-model, frob-io |
§14 |
| Sinew | Actuators, transmissions, batteries, thermal limits, power | frob-actuate |
§15 |
| Kinesis | Dynamics, integrators, the constraint solve, the three tiers and the trust ladder | frob-dyn (its step kernels live in Spark's frob-kernels) |
§16 |
| Phylum | Families of bodies in one batch: per-world model variants, size buckets, design-family dispatch | frob-phylum |
§17 |
| Traction | Collision, contact, friction, wheels, tracks, terrain mechanics | frob-contact |
§18 |
| Habitat | Scenes: terrain and interiors, generated or ingested; living worlds; clearance complexes; the retrofit catalogue | frob-scene |
§19 |
| Sensorium | Sensor models, the clock contract, the observation service, observability | frob-sense |
§20 |
| Spark | GPU backends and the kernel derivation toolchain | frob-kir, frob-kernels, spark/frob-spark-cuda, spark/frob-spark-metal, derive/frob-derive |
§21 |
| Reflex | State estimation, model-based control, gait orbits, skill artifacts, runtime shields | frob-control, frob-gait, frob-shield |
§22 |
| Cortex | The vectorized environment API, learning, family policies, policy inheritance | frob-learn, bindings/frob-gymnasium |
§23 |
| Arena | Tasks, the requirement language, fixtures, metrics, batteries, blinded qualification | frob-arena, frob-spec |
§24 |
| Augur | Mission queries over design families, inverse design, synthesis | frob-mission, frob-synth |
§25 |
| Nemesis | Adversarial worlds, minimal counterexample worlds, rare-failure estimation | frob-nemesis |
§26 |
| Autopsy | Counterfactual debugging by intervention on forked replays | frob-autopsy |
§27 |
| Atelier | The studio loop: static analysis, comparison, lineage, the co-design cascade, optimization, the decision cores | frob-analyze, frob-opt |
§28 |
| Chronicle | Telemetry, replay, the energy ledger, evidence | frob-chronicle |
§29 |
| Ground | Calibration against measured reality; reality bands | frob-ground |
§30 |
| Foundry | Structure, tolerance, fatigue, build packets, lifecycle | frob-foundry, frob-lifecycle |
§31 |
| Tether | CLI, daemon, MCP server, terminal dashboard, viewer, the agent model | frob-verbs, frob-cli, frob-tui, surface/frob-mcp, viewer/ |
§32 |
| Lemma | Proofs, certificates, certificate bundles, the offline auditor frob-verify |
frob-lemma, frob-cert, lean/ |
§12 |
| Gauntlet | The verification program and the ten-fold harness | frob-conformance, xtask |
§38, §39 |
| Airlock | The only code that names volatile FrankenSim types | frob-fsim |
§33 |
frob-core (identities and hashing, evidence classes, the claim-product type, refusals, schema versions, units glue)
belongs to no subsystem and sits under all of them. frob-units exists only if the admission gate INT-TOOLCHAIN-01
forces it (§33).