FrankenRobotics

Foundry: structure, manufacture, lifecycle

10,601 words23 subsections15 tables5 listingsPlan version 1.1

On this page23
31.1 What Foundry owns31.2 An output-quality subsystem, not a speed lever31.3 Decisions31.4 What the siblings provide today31.5 The structure loop31.6 Load cases extracted from telemetry31.7 Sizing and topology optimization of links31.8 Stress, buckling, modes and cumulative fatigue damage31.9 Inertia fed back into the model, and the convergence test31.10 Manufacturability31.11 Tolerance allocation driven by sensitivities31.12 Bounded export and the build packet .fbuild31.13 Firmware export31.14 Lifecycle compression31.15 Verbs31.16 Refusals31.17 Invariants and proof obligations31.18 Known answers31.19 Pilots, gates and kill gates31.20 Open questions31.21 Packet review as an imported record31.22 Referee re-extraction of load cases that enter a build packet31.23 Member sizing as a validity check in screening

Crates frob-foundry and frob-lifecycle (layer 5). Cluster foundry. The structure loop, manufacturability, tolerance allocation, export and the build packet are F. Firmware export and lifecycle compression are M, behind feature flags, and nothing depends on them.

31.1 What Foundry owns

  • The structure loop: load cases extracted from telemetry, sizing and topology optimization of links, an independent check of stress, buckling, modes and cumulative fatigue damage, the feedback of mass and inertia into the model, and the convergence test of the loads–mass loop. It serves analysis A-15 of §28.
  • Manufacture: manufacturability constraints, tolerance allocation driven by sensitivities, bounded export of geometry, and the build packet .fbuild.
  • Two Moonshots: export of fixed-point controller code with overflow checks, and lifecycle compression (frob-lifecycle).

Foundry fabricates nothing, buys nothing, flashes nothing and signs nothing off. Every artifact it writes says so in machine-readable flags (INV-FOUNDRY-01).

31.2 An output-quality subsystem, not a speed lever

Foundry makes the answer better. It does not make the answer arrive sooner, and no part of the ten-fold thesis of §2 rests on it. The numbers (FACT, Appendix H; each to be re-read from its primary source before a gate cites it):

  • Savings against engineered parts are roughly 7–30% of link mass. Reported cases: an industrial forearm 7%, an exoskeleton arm 10.4%, a hydraulic leg unit 24.5%, and two links of a table-tennis arm 25% and 29% (2.27 → 1.70 kg and 0.84 → 0.60 kg; https://arxiv.org/html/2606.26643v1). That last study optimized under natural-frequency constraints only, evaluated stiffness, stress and fatigue afterwards, and excluded two links as already near their limits. Against primitive shapes the saving is larger and means nothing, because nobody ships a solid capsule.
  • Link structure is a small share of a robot. In one 15 kg quadruped the four legs weigh about 4 kg (27%) and the twelve actuators about 6 kg (40%) (https://www.atlantis-press.com/article/15203.pdf). Seven percent off the whole leg mass is about 2% of the robot, and thirty percent about 8%, before shafts, gears and bearings inside the leg are excluded. The expectation is 2 to 8% of robot mass on this one quadruped, the only one with a published mass breakdown; there is no figure for humanoids.
  • It lengthens the loop. Each design gains finite-element solves per link, and three-dimensional optimization of 12 to 20 links is CPU-hours. Nothing here shortens a decision.
  • It is established practice. Feeding multibody loads into topology optimization is routine in commercial tools, and the cited arm study used one. No novelty is claimed.
  • Link fatigue is a safeguard, not an observed failure mode. Published fatigue analyses of legged robots concern gears; a bounded search found no report of a link failing by fatigue. The check exists because an optimizer that removes material can create the problem.

Ceiling, stated before any test. With link structure a fraction f_L of robot mass and a saving s, the direct ceiling is f_L·s ≤ 0.27 × 0.30 ≈ 0.08. The mass spiral (worked card GB-03, loop gain κ) multiplies a structural saving by 1/(1 − κ) only if actuators are then re-selected from a discrete catalogue, which is a separate decision with its own revalidation (HYPOTHESIS; the loop of §31.9 measures the realized multiplier).

Consequence (ADR-FOUNDRY-01): Foundry's topology rung, finite-element checks and build packet run on finalists, after qualification (§24). Its beam rung also runs inside screening, as a validity check on declared link walls (§31.23).

31.3 Decisions

ADR Decision Reason
ADR-FOUNDRY-01 Foundry's optimization and build output run after the design decision, on qualified finalists. The beam rung also runs at preflight and after the first rollouts as a validity check that can block promotion. An exploratory run is allowed, is labelled, and cannot enter a build packet. §31.2, §31.23.
ADR-FOUNDRY-02 Two rungs: closed-form beam sizing by default and as fallback; three-dimensional topology optimization for finalists. The beam rung costs milliseconds, serves A-15 and is the engineered baseline every optimized part is judged against.
ADR-FOUNDRY-03 A load case is one instant of one episode. Peaks from different instants are never assembled. The assembled case can be unsafe (§31.6).
ADR-FOUNDRY-04 Symmetric limbs share one optimization only after their load histories are transformed into one frame and unioned. An offset payload loads nominally identical limbs unequally.
ADR-FOUNDRY-05 The optimizer never checks its own result. Stress, buckling, modes and fatigue are evaluated on a separately generated body-fitted mesh. The optimizer's stress aggregate is not a bound, and thresholding changes the structure.
ADR-FOUNDRY-06 Fatigue is reported as utilization under a named empirical law with card provenance, class Estimated. The word "life" is not used for a result. The sibling states the same limit; curves for printed and cast material are model claims.
ADR-FOUNDRY-07 Actuator cards are held fixed inside the structure loop. Re-selecting an actuator is an outer step with full revalidation. Combining the two loops raises the loop gain and can cycle between catalogue sizes (§31.9).
ADR-FOUNDRY-08 Exported STEP is a faceted solid and is described as interchange evidence. No curved-surface re-fit is attempted. That is what the sibling exporter emits and checks.
ADR-FOUNDRY-09 Every exported artifact carries the no-authorization flags; the exporter has no code path that sets one true. §12; a packet must not be mistaken for a release.
ADR-FOUNDRY-10 No priced bill of materials without a pinned, licensed catalogue. OPEN-FOUNDRY-2.
ADR-FOUNDRY-11 No gate depends on a reviewer, a machine shop or a board. Those are import lanes that rest at no-claim. A simulator cannot gate on what it lacks.
ADR-FOUNDRY-12 Firmware export and lifecycle compression live behind features firmware-export and lifecycle; the latter is its own crate. Moonshots stay off the critical path and out of the build packet's dependency graph.

31.4 What the siblings provide today

FACT throughout, read at FrankenSim commit 483d09c682; paths are under frankensim/crates/ unless stated.

Crate Provides today Missing for Foundry
fs-topopt (40,000 lines, L4; depends on fs-solid, fs-material, fs-spectral) Density optimization with Helmholtz filtering, Heaviside projection, continuation, and chain-rule sensitivities checked against finite differences (pipeline, continuation, gradient_check). Optimality-criteria drivers for independent multiple loads (multi_load). A stress-constrained formulation with relaxation and a p-norm aggregate (stress). Eigenfrequency objectives (eigenfreq, modal). A robust erode/dilate formulation that enforces a minimum length scale (robust). Buckling-constrained modulus allocation (buckling). Behind feature cutfem-marquee, tagged Frontier upstream: three-dimensional optimization on cut cells over Cartesian and octree backgrounds (sdf3), with material body loads (sdf3::body), a relaxed stress measure and a sampled peak bound (sdf3::stress), minimum volume under a stress cap (sdf3::design), modal design (sdf3::modal), and goal-driven refinement (sdf3_goal). The three-dimensional lane is feature-gated. Its documentation says that cut volumes, discrete sensitivities and the stress aggregate are not continuum certificates, and that the aggregate is not a bound on the maximum. No load-case extraction, no ports, no interface tractions, no process constraints beyond length scale, no surface extraction for export.
fs-topols (15,700 lines, L4) Level-set optimization in two dimensions: a bilinear grid level set with exact enclosures (gridsdf), high-order advection, redistancing, velocity extension, topological derivatives for hole nucleation (topder), compliance descent with volume control and checkpoints (optimize), multi-load robust selection (robust), sampled stress admission (stress, robust_stress), hard-area projection (volume, projected). Two-dimensional only. The sampled stress is plane strain, and a thin plate is a plane-stress problem.
fs-solid (212,000 lines, L3, depends on fs-qty) Small-strain elasticity on body-fitted tetrahedra with consistent stiffness and mass (linear3). Consistent surface and volume loads (loads3), load histories sampled to quasi-static cases (loads3::history), sparse average-acceleration dynamics with an energy check (loads3::transient). Fatigue observation on the quasi-static path, with fixed-plane stress-life gauges whose rainflow residues persist across calls and a critical-plane utilization on closed windows (fatigue); the same observers on the inertial trajectory (loads3::transient::fatigue); Mode-I crack growth under a declared geometry factor (fatigue::crack_growth). Tensile assessment (strength), buckling pencils with eigenvalue derivatives (stability), force-based beam-columns (beamcol), frames, shells and rods. No path from telemetry to load cases and no multibody interface. A port wrench is not turned into interface tractions. Gauges are placed by the caller. Fatigue is elastic, small-strain and rate-independent, and the critical-plane result is utilization of a limit: "time labels do not turn the quasistatic solve into dynamics". No bolted-joint, press-fit, thread or weld models.
fs-material (src/fatigue.rs, src/fatigue/) Streaming rainflow with Palmgren–Miner damage (RainflowMiner), stress-life curves with an explicit reference stress ratio (SnCurve), named mean-stress corrections, strain-life, critical-plane and crack-growth laws. Unclosed reversals survive across input blocks; finish is called once, at the end of the whole observation. Calibration for printed and cast material is whatever a card supplies. The module calls itself an empirical baseline, "not a validated component-life claim".
fs-mesh (L2) Incremental Delaunay tetrahedralization on exact predicates with quality refinement and audits; constrained recovery and labelled volumetric meshing of piecewise-linear complexes (recovery, volumetric). Its crate documentation still lists full boundary conformity as successor scope. Whether an optimized link surface meshes cleanly is an admission test inside GATE-FOUNDRY-04.
fs-mbd-material (26,000 lines, depends on fs-qty) Mass, centre of mass and spatial inertia compiled from geometry volume moments and card density, with sources retained. Geometry coverage and rigidity are the caller's obligations. Material uncertainty is retained, not turned into an inertia bound.
fs-geocon (1,300 lines, L4) Soft minimum thickness (min_thickness_soft), draft violations with undercuts flagged (draft_violations), symmetry by quotient chart (QuotientChart), keep-in and keep-out envelopes (envelope_violation), an outward-rounded volume enclosure (volume_certified) and a smoothed volume with its shape derivative (volume_smooth). Thickness and envelope values carry estimate authority. No overhang, tool-access or corner-radius measure.
fs-fab (355 lines, L4) Scalar limit constraints by process (overhang angle, minimum feature size, tool radius, draft angle, and three structural-code and transport limits), each declaring its differentiability and certificate availability; check_all with a repair target per violation; parametric cost and embodied-carbon estimates with a relative uncertainty. It compares a supplied number with a limit. It does not measure geometry. No process-capability data, no machine models, no prices.
fs-toleralloc (6,500 lines, L4) Cost-optimal allocation t_i ∝ (c_i/s_i²)^(1/3) to a variance budget (allocate, variance_budget). A check of the linearization at tolerance-band extremes (robustness_check). A report in which each tolerance carries its sensitivity and that sensitivity's evidence colour (gdt_report). First-order correlated stacks aᵀ·C·a, up to 128 terms (propagate_correlated_stack), and grouped allocation (allocate_grouped). Finite-population propagation through piecewise-quadratic clearance laws with a gear-backlash consumer (structured_propagation, gear_backlash). No datum reference frames or feature control frames: the report is a list of suggestions, not a drawing annotation. Sensitivities and cost coefficients are inputs. Worst-case stacks are a separate analysis.
fs-io (22,300 lines, L2) Bounded Part-21 parsing and canonical writing at the syntax level (step). Strict decoding of a triangle-only faceted solid (step_faceted). Deterministic re-emission of a decoded faceted solid with mandatory self-parse and bit-exact replay (step_faceted_export). STL, OBJ, PLY, 3MF, GLB and VTK export. Quarantine of every import. Schema-checked catalogue ingestion (catalog) and a retained supplier-geometry corpus with a scorecard (supplier_corpus). The faceted exporter accepts only a solid produced by its own decoder; there is no entry point from a mesh. The file has no curved surfaces, no units or product context, and no application-protocol conformance claim. Default limits admit 10⁶ instances per file.
fs-contact (src/interface_binding/wear.rs) Archard wear volume advanced from caller-supplied sliding distance and compressive load. No recession geometry, and no map from volume to backlash.
fs-orbit (L2) Periodic orbits by harmonic balance and by shooting, Floquet multipliers from the monodromy matrix, pseudo-arclength continuation. Its problem shape is a nonlinear island on a linear port, not an articulated robot in contact. An oracle for toy known answers only.
fs-phs (src/circuit.rs) A finite state-of-charge battery with open-circuit voltage and polarization. No capacity fade or resistance growth. A search of the workspace found no cell-ageing law and no insulation-life law.
fln-verdict (franken_lean/crates/fln-verdict, commit 4426f8ea7) A bit-blaster, a CDCL solver, a proof stream with an independent streaming checker, and bv_decide, which returns a re-decoded counterexample or a replayed unsatisfiability candidate. The step that would derive the kernel proof term from the replayed certificate "is not built". A result is a checked certificate, not a kernel proof.

Consequences. Foundry's own code is the robotics and the glue: load extraction, interface tractions, gauge placement, feature measurement, the loop, the packet. fs-solid, fs-material and fs-mbd-material depend on fs-qty and are reached through the airlock (§33); Foundry jobs are whole jobs of seconds to minutes, so the worker-process fallback suits them. Upstream work items, numbered in Appendix F (FD-FSIM-26 to -30): a mesh entry point to the faceted STEP exporter; a plane-stress option in fs-topols; a stable (ungated) surface for fs-topopt::sdf3; geometric evaluators in fs-fab for overhang and tool access; a statement of boundary conformity in fs-mesh.

31.5 The structure loop

 qualified design ─► load campaign (T2 telemetry) ─► load cases and spectra ─► size (beam rung)
        ▲                                                                          │
        │                                                        finalists only    ▼
        │                                                              optimize (topology rung)
        │                                                                          │
        │            independent check: stress, buckling, modes, fatigue  ◄────────┘
        │                         │
        └── typed edit: new mass, centre of mass, inertia          repeat until the convergence test passes
                                  │
                                  ▼
          manufacturability ─► tolerances ─► export ─► .fbuild (flags false) ─► as-built scan (§30.14)

31.6 Load cases extracted from telemetry F

Source. Chronicle's T2 traces (§29) hold joint constraint wrenches, contact wrenches and body twists at control rate. A load campaign is the qualified task set plus push-recovery and drop tasks, run with T2 on every world at fixed world addresses, so the campaign is reproducible and is paired across loop iterations.

The load on a link at one instant is the wrench at each port (joint interfaces and, for a foot or wheel, the contact patch) in the link frame, together with the rigid-body acceleration field a(x) = a₀ + α × x + ω × (ω × x), with gravity folded into a₀. The free-body check is that port wrenches and the body load −ρ·a(x) sum to zero in force and moment. Its residual is recorded per sample; a sample above tolerance is dropped and counted, and more than 0.1% dropped (TARGET) refuses the campaign (FROB-REF-167).

Unit loads. The structural model is linear, so stress anywhere is linear in the load coordinates: six per port except the port used as a statically determinate 3-2-1 restraint, plus twelve for the body field (three for a₀, three for α, six for the products ω_i·ω_j). A two-port link has 18 coordinates and a three-port link 24 (FACT, arithmetic). One solve per coordinate gives a stress influence matrix, and the stress history at any gauge over a whole campaign is then a matrix product.

Envelope cases drive optimization. For a fixed, deterministic set of directions in scaled load space, the case is the sample that maximizes the projection; every case is a real instant with all ports and the body field taken from the same sample. Spectra drive fatigue: signed stress histories at gauges, in episode order.

Rules:

  1. Time-coherent cases only (ADR-FOUNDRY-03). Counterexample: a simply supported beam of span L carries P at L/3 at one instant and P at 2L/3 at another. The mid-span moment is P·L/6 each time. Assembling both peaks into one case gives P·L/3, a twofold over-design. If the second load has the opposite sign, the assembled case gives zero while each real case gives ±P·L/6: the assembled case is unsafe.
  2. Symmetric limbs are unioned, not assumed equal. Each limb's history is transformed into the canonical limb frame, with forces reflecting as polar vectors and moments as axial ones under a mirror (§10, C-09), and the cases are unioned. A payload offset sideways breaks equal loading.
  3. Impact loads carry a model-form label. Peak contact forces depend on contact stiffness. The campaign is re-extracted with stiffness halved and doubled and under the alternative contact law (§18). The envelope over variants is the load set, and a peak that moves by more than 20% (TARGET) marks the case model-conditional, a label the structural margin inherits.
  4. Quasi-static superposition needs separation of frequencies. It is used only when the link's first natural frequency is at least five times the highest frequency carrying 99% of load power (TARGET; the dynamic amplification 1/(1 − (f/f₁)²) is then at most 1.042). Otherwise impact windows go through the transient path of fs-solid (FROB-REF-262 if that is not enabled).
  5. A port wrench becomes tractions by a declared interface pattern on the port boss: a traction field affine in position whose resultant force and moment equal the wrench exactly. Stress within one boss diameter of an interface is no-claim; bolted joints and press fits are outside this chapter.
  6. Missing samples refuse the metric (FROB-REF-169). Nothing is interpolated across a telemetry gap.

31.7 Sizing and topology optimization of links F

Beam rung. Each link is idealized between its ports as a thin-walled tube or a rectangular section. For a tube of mean radius r and wall t: area 2π·r·t, second moment π·r³·t, section modulus π·r²·t, torsion constant 2π·r³·t; stress σ = N/A ± M/Z and τ = T/(2π·r²·t); the check is √(σ² + 3·τ²) ≤ S_y/SF, Euler buckling P_cr = π²·E·I/(K·L)², local wall buckling with a card knock-down, and a first bending frequency from the beam formula with end masses. Sizing picks the lightest stock size that passes every envelope case and the fatigue utilization at declared notches. Comparisons with rational inputs run in exact arithmetic (class D0). This rung answers A-15, is the engineered baseline, and is the fallback of KILL-TOPOPT.

Topology rung, finalists only. The design region is the keep-in envelope, minus the volumes swept by neighbouring bodies over the joint ranges (the swept charts of A-13), minus actuator, bearing and cable keep-outs, with port bosses frozen solid. The formulation minimizes projected volume subject to a stress cap S_y/SF on the relaxed measure (sdf3::design), a stiffness cap per envelope case from the control budget, a first-mode floor above actuator bandwidth (A-12; sdf3::modal), a minimum length scale (robust), and the process constraints of §31.10. Where a sibling driver takes compliance at fixed volume (multi_load), an outer bisection on volume fraction finds the lightest feasible design. Plate parts use fs-topols for shape in two dimensions and are checked in three. Mirror-image links are one problem (fs-geocon::QuotientChart).

Extraction. The surface is the level ½ of the projected density. Smoothing may change volume by at most 1% (TARGET) and is always followed by the independent check.

Budgets (TARGET, unmeasured). At most 120 s per unique link class for the coarse solve and 10 minutes for a finalist solve on the CPU cores of the M5 Ultra. A symmetric quadruped has three to five classes.

31.8 Stress, buckling, modes and cumulative fatigue damage F

The check runs on a body-fitted tetrahedral mesh of the extracted surface (fs-mesh), a different discretization from the optimizer's cut cells. fs-topopt depends on fs-solid, so the independence is of mesh and formulation, not of codebase; the cantilever and two-bar known answers anchor both paths.

  1. Stress. Every envelope case, plus the instants that govern each gauge under the influence matrix of the final geometry. Utilization is u = σ_vm/(S_y/SF) per element. The mesh is refined until the peak moves by under 5% (TARGET). A peak at a re-entrant corner that does not converge is reported as singular: fillet required, with the radius as the repair.
  2. Buckling. The first positive load factor from stability is at least 2 (TARGET) in every envelope case.
  3. Modes. The first frequency clears its floor.
  4. Cumulative fatigue damage. Gauges sit at the 16 highest-stress locations per unit load (TARGET) and at declared notches. Signed stress on each gauge plane feeds RainflowMiner across the campaign. With damage D accumulated over H_c campaign hours, utilization for a service duration H is U_f = (D/H_c)·H against a limit of 1 divided by the card's scatter factor.
    • Signed stress only. Unsigned von Mises is never fed to a cycle counter.
    • Residues are carried between episodes and finish is called once (see the window-split case in §31.18).
    • The mean-stress policy is named in the result.
    • The curve must be valid for the material state, the process and the surface finish. Otherwise the result is fatigue: no-claim (FROB-REF-163).
    • Cycles that span tasks (a loaded leg, then an unloaded one) are counted, because the campaign's duty sequence is part of the history.
  5. Class. Every number here is Estimated. A structural margin enters a claim product as its weakest input.

31.9 Inertia fed back into the model, and the convergence test F

The checked geometry and its material card go through fs-mbd-material, and the resulting mass, centre of mass and inertia replace the link's primitive Region by a typed edit (§14). That is a new DesignId. The baseline controller is re-synthesized (§22), the campaign re-runs on the same world addresses, and loads are re-extracted.

Why it can fail to converge. Structural mass of a link sized to a stress cap grows with the loads, and the loads grow with total mass. In the linear model, link mass S and other mass M₀ satisfy S = A + λ·(M₀ + S), with fixed point S* = (A + λ·M₀)/(1 − λ) and error contracting by λ per iteration. The actuator spiral of GB-03 has the same form with gain κ. If both run in one loop the gain is about κ + λ: at κ = 0.59 and λ = 0.15 it is 0.74, and five iterations contract the first step only to 0.74⁴ = 0.30 of itself (FACT, arithmetic). That is the reason for ADR-FOUNDRY-07.

Test. Let x_k collect link masses and principal inertias after iteration k, and Δ_k = x_k − x_{k−1}.

  • Estimated contraction: λ̂_k = ‖Δ_k‖/‖Δ_{k−1}‖, reported every iteration.
  • Converged when the relative change is at most 2% for two successive iterations, the a-posteriori bound λ̂/(1 − λ̂)·‖Δ_k‖ is at most 2% of ‖x_k‖, the load envelope moved by at most 5%, and the final geometry passes §31.8 under the loads it itself generates (all TARGET). The budget is five iterations; Aitken extrapolation x_k − Δ_k²/(Δ_k − Δ_{k−1}), applied componentwise, may propose the next iterate, which is then evaluated like any other.
  • Diverged when λ̂ ≥ 1 on two successive iterations: refused (FROB-REF-260) with the beam rung as the repair.
  • Cycling when Δ alternates in sign with λ̂ near 1, which a discrete stock size produces: one under-relaxed step x ← x + ½·(G(x) − x) is tried, then refusal.

The map G is deterministic only because the campaign reuses its world addresses (§35). With fresh random worlds each iteration, sampling noise sets a floor above 2% and the test cannot pass.

31.10 Manufacturability F

Each made part declares a process: cnc-3axis, cnc-5axis, sheet, fdm, sls or slm. fs-fab holds the limits and fs-geocon measures two of the features; the rest is measured by frob-foundry.

Feature Measured by Limit from Process
Minimum wall and member thickness fs-geocon::min_thickness_soft fs-fab::min_feature_size All
Internal corner radius Curvature of the distance field (ours) fs-fab::cnc_tool_radius Milling
Tool access Visibility of each surface point along the declared setup directions for the stated tool radius and reach (ours) Setup list on the process card Milling
Overhang angle Angle between surface normal and build direction (ours) fs-fab::overhang_angle Additive
Draft and undercut fs-geocon::draft_violations fs-fab::draft_angle Moulded
Enclosed voids Connected components of the complement (ours) None for milling; drain holes for powder processes All
Keep-in and keep-out fs-geocon::envelope_violation The design region All

Inside the optimization only constraints with usable derivatives are active: length scale, envelope, symmetry, and for additive parts an overhang filter. The others are checked after extraction. A violation returns the repair from check_all (target value and difference) and triggers a re-run with a tightened length scale. Cost and embodied carbon are parametric estimates with a relative uncertainty, class Estimated, and are printed only when a process card supplies the unit rates.

31.11 Tolerance allocation driven by sensitivities F

Quantities of interest. Foot or tool position error, joint-axis offset and parallelism, closure error of a loop, backlash, minimum clearance, wheel radius as an odometry scale. Sensitivities. For kinematic quantities they are exact derivatives of the product-of-exponentials map with respect to geometric parameters (§13), class Certified when evaluated in exact or interval arithmetic. For simulated task metrics they come from A-16 (§28), class Estimated. The allocation inherits the weaker class.

  1. variance_budget(spec_margin, target) turns the specification into a variance budget.
  2. allocate(features, budget, k) returns t_i ∝ (c_i/s_i²)^(1/3), normalized to meet the budget.
  3. Features that share a setup or a datum go through propagate_correlated_stack or allocate_grouped.
  4. robustness_check evaluates the true quantity at band extremes. Features that fail fall back to worst-case boxes by interval evaluation (fs-uq::product_epistemic), which is also the fallback of KILL-TOLERANCE.
  5. Clearances and backlash, which switch modes, go through structured_propagation.
  6. gdt_report enters the packet. It is a list of suggested tolerances with their justification, not a drawing annotation: datum frames are declared by Foundry in the packet (§31.12).
  7. The as-built audit of §30.14 compares each measured feature with its allocation.

Worked case. Two features with sensitivities 1 and 4, equal cost coefficients, k = 3, budget √B = 10 µm. The allocation is 16.0 µm and 6.35 µm. Equal tolerances meeting the same budget are 7.28 µm each, and the allocation costs 19.9% less under the 1/t cost model (FACT, arithmetic).

Counterexample: a zero first-order sensitivity is not insensitivity. For q(x) = x² at nominal zero the sensitivity is zero and a first-order allocator would loosen without limit, while the deviation at tolerance t is t². The sibling requires positive sensitivities; Foundry refuses the feature (FROB-REF-165) and routes it to the band-extreme check.

31.12 Bounded export and the build packet .fbuild F

Geometry export. The extracted surface passes repair and validity checks (watertight, manifold, oriented) through the quarantine path of fs-io, then is written as STL, 3MF and GLB. STEP is produced without an upstream change: Foundry builds a syntax-level StepDocument of the faceted-solid entity chain, writes it with write_step, parses and decodes it with decode_faceted_brep_with_limits, and re-emits it with export_decoded_faceted_brep, which refuses unless every coordinate bit and triangle index replays. Bound. The default limit of 10⁶ instances admits about 285,000 triangles for a closed mesh, at three instances per triangle, about half a point per triangle, and two more (FACT, arithmetic). A larger part is decimated under a stated Hausdorff tolerance and re-checked, or refused (FROB-REF-824). The file has no curved surfaces and no units entity; the manifest states metres.

The packet is one directory written atomically and addressed by the hash of its manifest (FMT-FBUILD, schema frob.build/1).

quad-a.fbuild/
  manifest.json         identities, flags, evidence classes, BLAKE3 of every file
  parts.json            made parts (geometry, material, process, mass) and purchased parts (card references)
  geometry/<part>.{step,stl,3mf,glb}      with triangle counts, datums and fiducials
  tolerances.json       per feature: tolerance, action, sensitivity, class; stack and robustness results
  mass.json             per part and assembly: mass, centre of mass, inertia, each with uncertainty
  harness.json          nets, connectors, conductor sizes, lengths with slack, checks
  schedule.json         actuator and sensor schedule
  structure/            load cases, utilizations, buckling factors, modes, loop convergence record
  fab.json              manufacturability report with repairs
  firmware/             optional; Moonshot; present only with feature firmware-export
  certs/*.frobcert      certificates the packet cites
{ "schema": "frob.build/1", "design": "DesignId", "model": "ModelId", "qualification": "verdict id or null",
  "authorization": { "execution_authorized": false, "hardware_safety_signoff": false,
                     "sim_to_real_certified": false, "fabrication_released": false },
  "reality": "no-claim", "review": "no-claim", "units": "SI", "exploratory": false }
// DESIGN: fixes intent, not signatures.
pub struct NoAuthorization { _sealed: () }      // the only value; it serializes to the four false fields
impl NoAuthorization { pub const fn new() -> Self { Self { _sealed: () } } }
// No constructor, setter or deserializer yields `true`. A packet that parses with a flag absent or true is
// rejected by the reader and by `frob-verify` (FROB-REF-860).
Section Contents Rules
Parts list Made parts with geometry, material, process and mass; purchased parts by card reference and quantity A continuous optimum snapped to a catalogue part, stock size or gear ratio is revalidated after the snap: hard constraints and the controller are re-checked on the snapped design. A failed simulation removes a whole part family only when an algebraic bound shows the failure holds across the family. No prices without a pinned, licensed catalogue (FROB-REF-818).
Geometry The four exports per made part; datum scheme and at least three non-collinear fiducials per part Datums and fiducials are placed at design time so that the as-built scan registers (§30.14).
Tolerances §31.11 Each tolerance carries its sensitivity and class.
Mass properties Mass, centre of mass and inertia per part and for the assembly, recomputed from the exported geometry Must equal the model's values within 10⁻⁶ relative (TARGET), which is the cross-export identity.
Wiring harness A netlist from the electrical ports of the design (§10, C-12); routes along the kinematic tree through declared cable ports; conductor size, length and slack per net The kinematic tree makes the shortest connecting tree the union of paths, so no approximation is needed. Checks: voltage drop I·ρ·L/A against the bus budget; current density against a declared limit; bend radius against the cable card; slack across a joint of at least ρ_c·Δθ for a cable at offset ρ_c from the axis. Sag and dynamic whip need a rod model, which is Frontier scope elsewhere in this plan, and are no-claim here.
Actuator and sensor schedule Per joint: actuator card, gear ratio, mounting interface, encoder, driver rate, limits, thermal derating. Per sensor: card, mount frame, extrinsic tolerance, clock contract (rational period and phase, §20), cable Every joint has an actuator card and every net has two ends.
Structural and manufacturing evidence §31.8 and §31.10 Classes are printed per number.

The prune rule has a counterexample that must be kept. Two gripper fingers each need one powered tick and the bus powers one finger per tick. With a one-tick deadline no schedule works; with two ticks exactly two do, and the motor limits are identical in both cases. A rule that adds both peaks prunes a feasible design. A prune is rejected if any discarded design is independently feasible under the same mission.

Review is an import lane. A human review of a packet, a quotation from a machine shop, and a first-article inspection are records that may be imported. Until one is, review reads no-claim.

31.13 Firmware export M

Scope. Joint-level controllers and monitors only: a proportional–derivative or proportional–integral loop, the energy-budget monitor of §22, a shield projection with a few rows. Whole-body controllers and state estimators in fixed point are out of scope. Output. Source for a no_std, heap-free crate that forbids unsafe code and sits behind a caller-owned bus trait; Q-format declarations; a test-vector manifest; overflow certificates; quantization error bounds; the flags. The exporter emits no register access, no bus driver and no stop-circuit code.

Checks, in order.

  1. Range analysis. Declared input ranges are propagated through the kernel IR (§21) by interval arithmetic, fixing a Q format for every intermediate.
  2. Bit-vector queries. Where intervals are too coarse (correlated terms such as a·x − a·y), the question "is there an input in range for which this intermediate overflows?" is bit-blasted and decided by fln-verdict::bv_decide. An unsatisfiable answer with a replayed proof stream is an instance certificate, class Certified. It is not Proved, because the proof-term step is not built upstream (§31.4). This is theorem card T-14 of §12.
  3. State. Integrators and filters need an inductive range invariant: one query for the base case and one for the step.
  4. Quantization. The difference from the real-valued controller is bounded by interval arithmetic, and its closed-loop effect is measured by running the fixed-point controller in the loop in the exact-integer kernel class of §35, so the simulated controller computes the same integers on every backend. Class Tested.
  5. Vectors. 10⁶ vectors agree bit for bit between the exported crate built for the host and the integer kernel (TARGET). That is a test, and it is not called equivalence.
  6. Not claimed. Execution time, stack depth and behaviour on a board. timing: no-claim until a receipt from a linked binary on real hardware is imported.

Counterexamples that seed the registry: in Q15, (−1)·(−1) is 0x8000·0x8000 = 0x40000000, which shifts to 0x8000 and reads as −1; the negation of −32768 overflows; an integrator adding 400 counts per tick from zero overflows sixteen bits at tick 82, and without a clamp the one-step query returns the state 32,400 at once.

Ceiling. No speed claim. The benefit is that the controller evaluated in simulation is, integer for integer, the arithmetic that would be shipped.

31.14 Lifecycle compression M

The question it answers. Whether the design that passes today still passes after months of its duty cycle; which component reaches its limit first, and when; what maintenance interval that implies; and what a lighter link costs in service duration. Outputs: time to first threshold per component with an interval, aged model variants at stated ages for Arena and Nemesis (§24, §26) as per-world variants in one batch (§17), and a front of mass against service duration. Every output is Estimated.

Method. The state splits into fast x and slow z with ẋ = f(x, z, u) and ż = ε·g(x, z). At 500 Hz, 1,000 hours is 1.8 × 10⁹ steps (FACT, arithmetic). Two-timescale averaging advances z with macro steps and estimates the averaged rate ⟨g⟩ from short micro windows at fixed z: a settling phase with a periodicity residual, then about twenty gait cycles of averaging (TARGET), or for a mixed duty an ergodic sample of the mission profile with its confidence interval. Macro steps use step doubling for error control.

Slow state Law (empirical; coefficients from cards) Feeds back into
Backlash β per joint Archard volume k·F_n·s/H mapped to recession by a card geometry factor The backlash rows of §18
Fatigue damage per gauge Rainflow with Miner's sum, residues carried across windows; cycles between duty modes counted at the macro level A threshold only
Winding insulation An Arrhenius rate in winding temperature A threshold only
Cell capacity and resistance Calendar fade in √t plus fade per unit of charge throughput Bus voltage sag in the actuator model of §15

Return to full resolution when a Floquet multiplier of the gait orbit (§22) approaches the unit circle, when the macro error estimate fails, or when the slow rate is no longer small. Rare overloads are invisible to short windows: their damage enters as rate times damage per event, with rates from Nemesis (§26).

Counterexample: the law of the average is not the average of the law. With the common halving of insulation life per 10 K, a duty that spends half its time at T_ref and half at T_ref + 20 K consumes life at 2.5/τ_ref. Evaluating the law at the mean temperature gives 2.0/τ_ref and overstates service duration by 25%. Micro windows therefore average the rate, never the input.

Ceiling. A run of 100 macro steps with three micro evaluations each, of 30 gait cycles at 0.5 s, simulates 2.25 × 10⁶ steps for 1,000 hours, a ratio near 800 in simulated steps (DESIGN, illustrative). It is a count of steps, not of wall time and not of field experience. Accelerated estimates can also change the failure mechanism; each law carries a validity domain and refuses outside it (FROB-REF-831).

31.15 Verbs

Verb Kind First milestone Does Refusals
foundry.loads run M4 Runs or reads a load campaign; returns envelope cases, spectra and the free-body residual 161, 162, 262
foundry.size read M4 Beam-rung sizing and the structural margin of A-15 163
foundry.optimize run M5 Topology optimization of link classes with the loads–mass loop 160, 164, 260
foundry.check run M5 Independent stress, buckling, modal, fatigue and manufacturability check of a geometry 163, 261
foundry.tolerance read M5 Sensitivity-driven allocation, stacks and the band-extreme check 165
foundry.export run M5 Writes geometry and the build packet; --with-firmware under its feature 160, 860, 861, 862, 863
foundry.lifecycle run M8 A lifecycle run under feature lifecycle 864

Seven verbs, the limit of §32. Long verbs take the bounded synchronous wait and otherwise return a job handle.

31.16 Refusals

Code Refused Repair offered
FROB-REF-166 Optimization or packet export for a design with no qualification verdict Qualify, or run with --exploratory (labelled; cannot enter a packet)
FROB-REF-167 A load case that is not one instant, or a campaign failing the free-body check The offending samples and residuals
FROB-REF-169 Telemetry without the traces or samples a load metric needs The telemetry level and worlds required
FROB-REF-163 A check whose material card lacks the field or provenance it needs The missing field; fatigue: no-claim
FROB-REF-164 An empty design region, or ports with no load path inside the envelope The blocking keep-outs
FROB-REF-165 An allocation with a zero or unknown sensitivity, or a failed band-extreme check Worst-case boxes for the named features
FROB-REF-260 A loads–mass loop that diverges, cycles or exceeds its iteration budget λ̂, the last iterates, and the beam rung
FROB-REF-261 An optimized part that fails the independent check The governing case and location; tighter cap or length scale
FROB-REF-262 Quasi-static superposition where the frequency separation fails Enable the transient path for impact windows
FROB-REF-860 An export without the flags, or any attempt to produce a true flag None
FROB-REF-818 A priced parts list without a pinned, licensed catalogue Omit prices
FROB-REF-824 A STEP export above its bounds or failing bit-exact replay Decimate under a stated tolerance
FROB-REF-827 A fixed-point obligation refuted or undecided within budget The counterexample input, or a wider format
FROB-REF-831 A lifecycle law outside its validity domain, or cited above class Estimated The domain and the card needed

31.17 Invariants and proof obligations

ID Statement How it is tested
INV-FOUNDRY-01 Every exported artifact carries the no-authorization flags, all false. The type has one value; a mutated packet is rejected by reader and auditor
INV-FOUNDRY-02 A load case is a single instant of a single episode at a recorded world address. Each case replays to its sample
INV-FOUNDRY-03 No geometry enters a packet without passing the independent check on a mesh the optimizer did not use. Packet manifest cites the check's mesh hash
INV-FOUNDRY-04 Mass properties in the packet equal those of the model the evidence was computed with. Recomputed from exported geometry
INV-FOUNDRY-05 A packet is written whole or not at all. The writer is killed at every file boundary
INV-FOUNDRY-06 Foundry and lifecycle results are at most class Estimated, except instance certificates of §31.13. Claim-product types (§8)
INV-FOUNDRY-07 The build packet does not depend on frob-lifecycle or on the firmware feature. Dependency firewall in xtask
PO-FOUNDRY-01 The unit-load superposition reproduces a direct solve of any campaign sample. 10³ random samples, relative difference at most 10⁻⁹ on the referee
PO-FOUNDRY-02 The interface traction pattern returns the port wrench exactly. Resultant force and moment to rounding
PO-FOUNDRY-03 The a-posteriori bound of §31.9 holds for a contraction. Derivation on file; the planted-gain fixture
PO-FOUNDRY-04 For each exported controller, no intermediate overflows on the declared input ranges (T-14). Replayed bit-vector certificates

31.18 Known answers

Values are hand calculations filed under docs/derivations/; fixture dimensions and material constants are DESIGN choices. Each row has a negative control.

Known answer Fixture Expected Negative control
Cantilever L = 0.20 m, section 20 × 10 mm, E = 69 GPa, tip load 50 N Tip deflection P·L³/(3·E·I) = 1.159 mm; root stress 6·P·L/(b·h²) = 30 MPa; shear adds about 0.2% Halving the load halves both; a millimetre-for-metre unit error is caught by dimension typing
Planted overstressed link The same beam with a root section 4 mm deep, 80 N, yield 240 MPa Stress 300 MPa, utilization 1.25, located at the root The unthinned beam passes
Two-bar optimum Load P at distance L from a wall, domain height 2L Bars at 45°; compliance 4·P²·L²/(E·V); minimum volume 2·P·L/σ_allow Swapping the support and the load port is caught
Assembled peaks Simply supported span, P at L/3 then at 2L/3 P·L/6 per instant; assembled P·L/3 or 0 The assembling mutation is refused
Fatigue block N(S) = 10⁶·(100 MPa/S)³, fully reversed; 2,000 cycles at 200 MPa, 50,000 at 100, 400,000 at 50 Damage 0.016 + 0.050 + 0.050 = 0.116 per block; 8.62 blocks to a sum of 1 Feeding unsigned stress changes the count and is refused
Rainflow sequence −2, 1, −3, 5, −1, 3, −4, 4, −2 in units of 40 MPa, no mean-stress correction Ranges 3, 4, 6, 8, 9 with counts 0.5, 1.5, 0.5, 1.0, 0.5; damage 8.752 × 10⁻⁶ Splitting after the fifth point and finishing each window loses the range-9 half cycle and gives 7.816 × 10⁻⁶, 10.7% low
Loads–mass loop M₀ = 12 kg, A = 0.6 kg, λ = 0.15, start 4.0 kg Iterates 3.0, 2.85, 2.8275, 2.8241, 2.8236; fixed point 2.8235 kg; λ̂ = 0.15 λ = 1.1 is refused as divergent within three iterations; a planted two-size cycle is detected
Mass properties Tube, ρ = 2,700 kg/m³, radii 15 and 13 mm, length 0.20 m Mass 0.0950 kg; axial inertia 1.87 × 10⁻⁵ kg·m²; transverse 3.26 × 10⁻⁴ kg·m² The volume enclosure must contain the exact volume
Tolerance allocation §31.11 worked case 16.0 µm and 6.35 µm; 19.9% cheaper q = x²: refused, then fails the band-extreme check
Voltage drop Copper, 1 m each way, 0.5 mm², 10 A, 24 V bus 0.0688 Ω; 0.688 V (2.9%); 6.9 W; 20 A/mm² Halving the area doubles the drop
Cable slack Offset 15 mm, joint range 2.4 rad 36 mm —
STEP round trip A tetrahedron 18 instances; bit-exact replay An open shell is refused; a part above the bound is refused with the bound stated
Fixed point §31.13 cases Each counterexample found; the clamped controller certified A widened input range breaks a certificate
Averaged growth ż = ε·a·x², x = sin ωt z(T) = ε·a·T/2 over whole periods —
Wear feedback β̇ = ε·(c₀ + c₁·β) β(t) = (β₀ + c₀/c₁)·exp(ε·c₁·t) − c₀/c₁ A planted gait collapse at β* must force full resolution before β*
Rate averaging Halving per 10 K; half the time 20 K hotter Rate 2.5/τ_ref, not 2.0/τ_ref Averaging the input is caught
Cell fade 1% per √month calendar, 0.5% per 100 cycles; 9 months, 300 cycles 3% + 1.5% = 4.5% —

31.19 Pilots, gates and kill gates

Pilots before funding (each F or M item; CPU only).

Mechanism Pilot Falsifier Ceiling
Structure loop One quadruped lower-leg link against a thin-walled tube sized by hand to the same peak load. Stage 1, runnable on the siblings today: three analytic envelope cases from stance and trot statics. Stage 2, after M2: three envelope cases from 1,000 simulated episodes, with five loop iterations. Two to three engineer-days. Saving under 5% against the tube at equal first bending frequency and equal fatigue utilization; or mass still changing by more than 2% between iterations four and five A few percent of robot mass (§31.2)
Tolerance allocation A planar linkage with eight toleranced features; allocation against equal tolerances; band-extreme check Held-out Monte Carlo coverage of the specification below target Cost under an assumed 1/t model only
Build packet One hand-built part and one purchased part through the whole export Any cross-export mismatch or failed round trip No time claim
Firmware export A Q15 proportional–integral loop with and without a clamp A missed overflow, or an obligation undecided inside its budget None on speed
Lifecycle A forced oscillator with slow wear and ε = 10⁻⁴, against direct integration Error above 5% at a compression of 50 in steps Steps, not wall time or field time
Gate Claim Threshold (TARGET) Earliest
GATE-FOUNDRY-01 Known answer Cantilever deflection within 2% and stress within 5% after refinement; the planted overstress located with utilization 1.25 ± 5%. M4
GATE-FOUNDRY-02 Known answer Free-body residual at most 10⁻⁶ relative on the referee and 10⁻³ on single-precision tiers; superposition equals direct solves (PO-FOUNDRY-01); the assembled-peak and equal-limb mutations refused. M4
GATE-FOUNDRY-03 Known answer Fatigue block and rainflow sequence exact to 10⁻¹² relative; the window-split mutation reproduces its 10.7% and is caught. M4
GATE-FOUNDRY-04 Known answer Two-bar compliance within 10% and bar angle within 5°; the extracted surface meshes and passes the mesh audit on 20 of 20 fixtures. M5
GATE-FOUNDRY-05 Design comparison The stage-2 pilot: saving at least 7% (kill threshold, as in BET-29 and C-35) with 15% the target; the convergence test passes within five iterations; coarse solve at most 120 s per link class. M5
GATE-FOUNDRY-06 Known answer Planted-gain loop: fixed point within 10⁻⁶, λ̂ within 0.01; divergence and cycling refused. M5
GATE-FOUNDRY-07 Known answer Planted violations of wall, corner radius, tool access, overhang and undercut each detected with location and repair; clean parts pass; 20 of 20. M5
GATE-FOUNDRY-08 Known answer The worked allocation to 10⁻⁹; the zero-sensitivity and quadratic cases handled as specified; a correlated stack equals its hand value. M5
GATE-FOUNDRY-09 Known answer Tetrahedron round trip bit-exact; open shell and over-bound parts refused; mass properties from exported geometry within 10⁻⁶ of the model. M5
GATE-FOUNDRY-10 Known answer Packet schema-valid, every hash matching, flags present and false, cross-consistency of parts, geometry, nets and schedule; a mutated flag rejected by frob-verify; a writer killed at any file boundary leaves no packet. M5
GATE-FOUNDRY-11 Known answer M The fixed-point cases of §31.18; 10⁶ vectors bit-equal. M8
GATE-FOUNDRY-12 Fidelity M A 100-hour reference (1.8 × 10⁸ steps) compressed at least 50-fold in steps with at most 5% error on every slow state; the planted backlash-induced gait collapse caught. M8
Kill Trigger Fallback Decided at
✖ KILL-TOPOPT GATE-FOUNDRY-05 fails: saving under 7%, no convergence, or over budget Beam-rung sizing supplies mass and inertia feedback; three-dimensional optimization becomes an offline option or is dropped; A-15 is unaffected. M5
✖ KILL-LOADS GATE-FOUNDRY-02 fails after one repair cycle Load cases are declared by hand from statics with a stated dynamic factor; spectra and fatigue read no-claim. M4
✖ KILL-FAB GATE-FOUNDRY-07 fails Manufacturability findings become advisory lints; a packet records no manufacturability pass. M5
✖ KILL-TOLERANCE GATE-FOUNDRY-08 fails, or band-extreme checks fail on more than a fifth of features in the pilot Worst-case boxes per interface. M5
✖ KILL-PACKET GATE-FOUNDRY-09 or -10 fails after one repair cycle Parts list, mass properties and STL only; STEP and harness deferred. M5
✖ KILL-FIRMWARE GATE-FOUNDRY-11 fails Controller parameters, Q formats and the test-vector manifest only; no code. M8
✖ KILL-LIFECYCLE GATE-FOUNDRY-12 fails Aged model variants at hand-specified wear states, with no time axis and no compression claim. M8

31.20 Open questions

  • OPEN-FOUNDRY-1. Whether fs-mesh produces a conforming mesh of an arbitrary optimized surface. Default: if it does not, the independent check is a second cut-cell solve at a different resolution and background offset, and results are labelled check: same-family. Owner: Foundry lead. Blocks GATE-FOUNDRY-04.
  • OPEN-FOUNDRY-2. Which parts catalogue and price data, under what licence. Default: card references and no prices. Owner: project lead. Blocks nothing.
  • OPEN-FOUNDRY-3. Which current-capacity table governs conductor sizing. Default: current density against a limit declared on the cable card, with no capacity claim. Owner: Foundry lead.
  • OPEN-FOUNDRY-4. Stress-life data for printed material by process and orientation. Default: fatigue: no-claim for printed parts. Owner: Foundry lead. Blocks the fatigue leg of GATE-FOUNDRY-05 for printed fixtures only.
  • OPEN-FOUNDRY-5. Wear, insulation and cell-fade coefficients with provenance. Default: generic cards marked assumed, which --strict-data refuses. Owner: Sinew lead (§15). Blocks GATE-FOUNDRY-12.
  • OPEN-FOUNDRY-6. The time budget per bit-vector obligation. Default: 2 s (TARGET), with a timeout treated as undecided and therefore refused. Owner: Lemma lead (§12).

31.21 Packet review as an imported record

This subsection extends §31.12 ("Review is an import lane") and keeps ADR-FOUNDRY-11: no convergence gate depends on a reviewer. It gives the import lane a protocol and a record format, so that an imported review means the same thing for every packet, and it separates what a program can check from what only a person can. Tier S. Owner: frob-foundry. Verb: foundry.check, which runs the mechanical pre-review and, with --review-record <file>, imports a record.

Hidden briefs. DESIGN: a set of 12 written briefs (TARGET), authored by someone who has not seen the development fixtures of the packet pipeline. Each states a mission, an approved parts catalogue, a budget, the interfaces and the deliverables. The digest of the set is committed before the pipeline version under test is frozen, and the briefs are opened only to the frozen pipeline. A brief is used once and then retired to the development corpus, by the rule that governs confirmation clusters in §24.13.

Unattended production. Each brief runs from mission query to design, qualification verdict and packet with no human edit in between; attempts and refusals stay in the record. A brief the pipeline cannot satisfy must end in a typed refusal that names the binding constraint. A correct refusal is a valid outcome and is reviewed as one.

Mechanical pre-review (foundry.check <packet>), each item pass or fail with the offending file:

Item Check
M1 Schema, every digest, the four flags present and false (§31.12)
M2 Cross-export identity: mass, centre of mass and inertia agree within 10⁻⁶ relative (TARGET) among the model the evidence used, mass.json, the values recomputed from each of the four geometry exports, and the URDF and MJCF exports of §14.12, with units checked
M3 Referential integrity: every joint has an actuator card, every net has two ends, every made part has its geometry files, every purchased part resolves to a card
M4 Every number carries a claim class and an evidence reference that resolves in the artifact graph (§29.13)
M5 The cited qualification verdict is for this DesignId and ModelId
M6 Every snapped part was revalidated after the snap

The review record (schema frob.review/1), a sidecar addressed by the packet's manifest digest:

{ "schema": "frob.review/1", "packet": "manifest digest", "brief": "brief digest or null",
  "reviewer": { "independent": true, "role": "mechanical designer" },
  "rubric": { "R1_producibility": "pass", "R2_assembly_and_tool_access": "fail",
              "R3_harness_and_service": "pass", "R4_quotable_from_packet_alone": "pass",
              "R5_evidence_legible_and_not_overstated": "pass" },
  "notes": [{ "item": "R2", "part": "bracket-b", "text": "second fastener is enclosed after step 3" }],
  "outcome": "accept-with-changes", "minutes": 55, "date": "YYYY-MM-DD" }

independent means the reviewer took no part in developing the pipeline or the design. Importing a record changes no byte of the packet; the manifest view then shows review as the record's outcome with the record digest in place of no-claim. A record whose packet digest does not match is refused.

What is gated and what is recorded. The gate below covers the mechanical half only. The human half is a recorded count with a TARGET: at least 11 of the 12 packets receive accept or accept-with-changes. The count, the reviewer minutes and the list of rubric failures are printed in the release rubric (§47). While no record exists the count reads no-claim, and no text may describe a packet as reviewed.

Counterexample: a mechanical pass is not a review. A two-part bracket whose second fastener sits behind the first part once it is mounted. Each part passes the tool-access check of §31.10 as a part, the packet passes M1 to M6, and the assembly cannot be completed in the listed order. Rubric item R2 exists for this case, which is why a mechanical pass is never rendered as review: accept.

Known answers. The tube of §31.18 (0.0950 kg) is reproduced from each geometry export within 10⁻⁶. A surface file written in millimetres and read as metres has 10⁹ times the volume; M2 reports the ratio and names the file. A packet that cites a verdict for the pre-snap design fails M5.

Ceiling, stated before any time comparison. No time claim is made. FACT: no reference packet has been timed by this project, so a figure such as hours for a scripted reference against minutes for the pipeline would be illustrative. Time from brief to accepted packet is measured only inside the protocol of §39, in a stratum that includes packets, with reviewer minutes inside the clock.

Gate. GATE-FOUNDRY-13 (Known answer, M5). On the 12 hidden briefs every outcome is a packet that passes M1 to M6 or a typed refusal naming a binding constraint (12 of 12); no cross-export difference exceeds 10⁻⁶; the planted unit error and the planted stale verdict are each caught in 100 of 100 runs; importing a record leaves the packet digest unchanged; a record with a wrong packet digest is refused. The fail-closed default without a reviewer is review: no-claim, and KILL-PACKET (§31.19) is unchanged.

31.22 Referee re-extraction of load cases that enter a build packet

Load cases are promoted like any other result S. This adds a seventh rule to §31.6. A load campaign runs on a fast tier, because it needs every world traced and many episodes. Peak contact and joint wrenches are exactly the quantities a compliant fast-tier contact gets wrong, and rule 3 of §31.6 bounds only the part of the error that moves with contact stiffness. A load case is therefore a fast-tier result under the trust ladder of §16.8, and it is provisional until promoted.

  1. Envelope cases are re-extracted on the referee before they enter a packet. For each envelope case, the world and instant that produced it are replayed on the referee from the nearest snapshot (the teleport of §29.8) over a window of 0.5 s on either side (DESIGN), and the port wrenches and body field are read again at the instant of the referee's own maximum projection inside the window. The case then carries both values, the tier pair and one of three labels: established when the two agree inside the fidelity envelope for wrenches, with the referee's value used; tier-sensitive when they do not, in which case the referee's value replaces the fast one and the direction is searched again among the neighbouring fast-tier samples; provisional: referee-unavailable when the referee cannot complete the scenario (§29.11), in which case the strict profile of batch-cpu adjudicates and the label names it.

A build-packet request that contains a provisional envelope case is refused; an exploratory structure run may use provisional cases and is labelled, as §31.3 already requires. Fatigue spectra are checked the same way on a keyed sample of windows: the ratio of referee to fast-tier stress range at each gauge is recorded, and a spectrum whose ratio leaves the band declared in the packet is rescaled to the referee's range before damage is summed.

Why a small tier bias matters here. Cumulative damage scales as stress range to the power m of the material card's S-N law. A load that is 10% high gives 1.1⁵ = 1.61 times the damage at m = 5 and 1.1¹⁰ = 2.59 times at m = 10. An error that would be negligible in a task score changes a predicted life by a factor of two.

Cost. One referee window per envelope case: a two-port link has 18 load coordinates (§31.6), so a direction set of 2 × 18 axis directions gives at most 36 windows of 1 s per link class, and three to five classes on a symmetric quadruped give 108 to 180 referee-seconds of simulated time per iteration of the structure loop (DESIGN arithmetic).

Owner and verb. frob-foundry; foundry.loads returns each case with both values, its label and the replay address. No new kill gate: the rule is a use of promotion, and the fallback when the referee and strict are both unavailable is the existing one, no packet.

Gate Claim Threshold (TARGET) First milestone
GATE-FOUNDRY-14 Known answer Every envelope case in a packet has a re-extraction record. A planted fast-tier artifact (a stiffness spike that doubles one peak on the fast tier only) is relabelled tier-sensitive and replaced in 100 of 100 runs; a packet request holding a provisional case is refused in 100 of 100; the referee cost per packet is reported M5

31.23 Member sizing as a validity check in screening

Member sizing inside screening S. This amends ADR-FOUNDRY-01. The topology rung, the finite-element checks and the build packet stay with qualified finalists. The beam rung of §31.7 costs milliseconds and also runs earlier, as a validity check on what a design declares. Without it a screening campaign rewards links that could not be built: a limb segment whose shell is thinner than any section that survives its own loads has less distal inertia, lower swing torque and a better score than its buildable version would have.

The check. For each link whose fill is a shell or a lattice (§14.5), foundry.size computes the lightest stock section between the link's ports that passes the criteria of §31.7 under a load set. It compares that section's mass m_min and its inertia about the proximal joint with the values the design's fill produces.

  • Before any rollout, at stage 6 of the preflight beside the actuator checks: a bounded load set from statics. Each foot, wheel or end-effector port carries the robot's weight times a class load factor (DESIGN defaults on the archetype card: 3 for legged feet, 2 for wheels, 1.5 for manipulator ports with the rated payload added), in the worst direction the port admits. The finding is under-built, with the ratio m_min over declared mass.
  • After the first rollouts: the same check under the peak port wrenches of T1 telemetry, taken time-coherently as in §31.6. A design that is under-built under measured loads keeps its scores with the label structure-unchecked. It cannot be promoted (§16.8) until it is re-run with the sized section, or until a typed edit changes the declared one.

A link may ask to be sized instead of declaring a wall: the fill {shell: sized} takes the thinnest stock wall that passes, and the model's mass properties are set from it before the first rollout (DESIGN; the default for archetype templates if the gate below supports it).

Known answer. A cantilevered tube 0.3 m long carries 600 N across its tip, about three times the weight of a 20 kg robot. The root moment is 180 N·m. In an aluminium alloy with S_y = 276 MPa and a safety factor of 2 the allowable stress is 138 MPa. At a mean radius of 15 mm the thin-wall section modulus π·r²·t requires t ≥ 180/(138 × 10⁶ × π × 0.015²) = 1.85 mm. At 2,700 kg/m³ the mass 2π·r·t·L·ρ is 0.141 kg, and the inertia about the root, as a uniform rod, is m·L²/3 = 4.2 × 10⁻³ kg·m². A design that declares this segment at 0.05 kg is under-built by a factor of 2.8, and its swing inertia is understated by the same factor.

What it is not. It is a floor on mass, not a design: no fatigue, no joints, no local buckling beyond the card's knock-down, and impact enters only through the load factor until telemetry exists. It does not make structure part of the decision-time thesis (§31.2). It removes one way for screening to mislead.

The number that decides whether it matters. HYPOTHESIS: enforcing sized members changes the winning actuator card or gear ratio in a non-trivial share of campaigns. The test: 10 quadruped and 5 mobile-manipulator campaigns from the design corpus, each run with declared walls and with sized members, reporting how often the winner or its actuator selection changes.

Owner, verb and refusal. frob-foundry sizes; frob-analyze calls it at stage 6; frob-arena applies the structure-unchecked label. The verb is the existing foundry.size, called by design.check. Promotion of a design with a link that is under-built under measured loads is refused, with the link, the ratio and the sized section as a typed repair.

Gate Claim Threshold (TARGET) First milestone
GATE-FOUNDRY-15 Known answer; Design comparison The tube case returns t = 1.85 mm and 0.141 kg within 1%. A planted under-built link is flagged before the first rollout and blocks promotion. The check adds at most 50 ms to design.check on the reference robots. The corpus comparison is run and its share recorded; if the winner or its actuator selection changes in fewer than 1 campaign in 15, the check stays as a promotion guard and {shell: sized} is not made the template default M3