FrankenRobotics

Verb registry

5,809 words5 subsections4 tables1 listingPlan version 1.1

On this page5
J.1 One entryJ.2 Every verb of the mechanical inventory, by clusterJ.3 Verbs the chapters define that the mechanical inventory does not holdJ.4 One name per verbJ.5 What an agent sees: task clusters of at most seven tools

The registry is registries/verbs.toml, owned by frob-verbs. The CLI, the daemon protocol, the MCP tool definitions, the schemas, the refusal table and robot-docs are generated from it, so the surfaces cannot drift (GATE-TETHER-02 diffs the served tools/list against it). Kinds: read returns stored or cheaply computed facts and changes nothing; run spends compute, takes an idempotency key and a budget, accepts the bounded synchronous wait (sync_wait_ms) and otherwise returns a job handle with exit code 8; mutate creates or changes a named object in the caller's namespace and takes an idempotency key and an expected parent; admin cancels, stops, evicts or deletes and needs a capability scope.

J.1 One entry

[[verb]]
name = "design.check"
cluster = "design"
kind = "read"
tier = "S"
capabilities = ["design:read"]
input_schema = "frob.design.check.in/1"
output_schema = "frob.design.check.out/1"
refusals = ["FROB-REF-101", "FROB-REF-104", "FROB-REF-107", "FROB-REF-110"]
idempotent = true
cost_model = "static: under 2 s for template-sized designs"
first_milestone = "M1"
task_clusters = ["author", "places"]
examples = ["frob design check quad-a --json"]

A run verb adds its per-surface wait default (wait to completion on the CLI; 5,000 ms on MCP, at most 30,000). No verb has a second spelling (J.4). The MCP tool name is the verb name with . and - replaced by _ (telemetry.inspect-pixel becomes telemetry_inspect_pixel); no registry name contains an underscore, and a lint checks that the map is one-to-one (§32.12.3).

J.2 Every verb of the mechanical inventory, by cluster

The inventory of Phase 1 holds 169 dotted names. One, policy.rs, is a source file name in a sibling and not a verb. Five more were second names for a mechanism that an owner chapter registers under another name, or had no owner, and are not registered (J.4). The other 163 are below. Kinds and milestones come from §32.6 where it lists the verb and from the defining chapter otherwise; where a verb has two milestones the first is the one at which a reduced form lands.

Verb Kind First milestone Purpose Defined in
analyze
analyze.symmetry read M1 Γ_mech and Γ_obs of a design, with the element that breaks each excluded generator (A-03) §13.4
autopsy
autopsy.attribute read M3 Contrasts, flip rates, pairs, labels and an optional Shapley summary for a fork §27.6, §27.7
autopsy.intervene run M3 Run interventions, placebo forks, replicates and coalitions from a fork handle made by run.fork §27.5
autopsy.repair run M3 Minimal repair sets, by shrinking the intervention set §27.7
autopsy.rerun run M3 Paired re-run from the episode start for design-parameter and structural edits §27.8
autopsy.show read M3 The transcript of an attribution session, token-budgeted §27.12
control
control.estimate read M1 Replay a run's packets through the invariant filter and its comparator §22.3
control.ladder read M3 The control rung a design is on, the reason, and the next experiment with its cost §22.7
control.mpc run M3 The sampling-based predictive controller, as a screening rung; three episodes per design by default, and up to the break-even count for a paired screening comparison §22.8
control.symmetry read M4 Γ_mech, Γ_obs, the stabilizers in force and the group a controller may use §22.13
design
design.bisect run M4 Find the edit in a lineage that changed a verdict, with an anytime-valid comparison at each step §28.7
design.blame read M1 The edit that last changed a field or a derived quantity §28.7
design.check read M1 The eight preflight stages and the analyses marked for check; findings with ranked repairs §14.11, §28.4
design.diff read M1 Structural and parameter difference of two versions, with the symmetry effect §28.7
design.edit mutate M1 One typed edit; returns the new DesignId, the symmetry effect and the invalidation set §14.7
design.patch mutate M1 Several typed edits against a named parent, with locks and required analyses §14.8
design.templates read M1 The eighteen archetypes and their parameters §14.10
eval
eval.compare run M3 Plan and submit a paired study on common world addresses; the reachability pre-analysis is eval.preanalyze §28.6
eval.detect run M3 The exploitation detectors, on one result §23.16
eval.ledger read M3 A qualification campaign's index, levels spent and receipts; nothing sealed §24.13
eval.preanalyze read M1 Reachable verdicts and power of a fixed-n rule at a given n and level §24.12
eval.promote run M3 Apply the promotion rule and the tier correction to a fast-tier result §16.8
eval.qualify run M3 Submit a committed request to the blinded lane; returns a receipt and nothing per world §24.13
eval.rank-agreement run M4 Measure rank agreement between two rungs in a stratum and write the ledger record §28.10
eval.run run M2 Run a battery and record verdicts §24.8
eval.scorecard read M3 Metrics by scene class with the outcome columns and two denominators §24.8
experiment
experiment.suggest read M4 Ranked information-gathering proposals with testable predictions §28.16, §25.14
explain
explain.compare read M3 Why two designs differ on a task: first divergent event and binding atoms §28.5
explain.design read M1 What limits a design, by analysis, ending with next actions §28.5
explain.run read M1 First cause of a run's outcome, token-budgeted, ending with next actions §28.5
foundry
foundry.check run M5 Independent stress, buckling, modal, fatigue and manufacturability check of a geometry §31.15
foundry.export run M5 Write geometry and the build packet; --with-firmware under its feature §31.12
foundry.lifecycle run M8 A lifecycle run under the feature lifecycle §31.15
foundry.loads run M4 Run or read a load campaign; envelope cases, spectra, the free-body residual §31.15
foundry.optimize run M5 Topology optimization of link classes with the loads–mass loop §31.5
foundry.size read M4 Beam-rung sizing and the structural margin of A-15 §31.15
foundry.tolerance read M5 Sensitivity-driven tolerance allocation, stacks and the band-extreme check §31.11
gait
gait.atlas read M4 Enumeration of gaits as (H, K) pairs with phase lags (analysis A-04) §22.9
gait.continue run M4 Pseudo-arclength continuation of an orbit in a design parameter §22.9.5
gait.gradient run M4 Design gradient of an orbit and its metrics, with derivative labels §22.9.6
gait.orbit run M4 Solve a periodic orbit by shooting; multipliers, residual, standing screening §22.9
ground
ground.band read M5 Issue or refuse a reality band; cells, coverage accounting, monitor states; --retire needs a capability §30.16
ground.excite read M4 Identifiability report and excitation plan for a design, a card set and a rig §30.16
ground.identify run M5 Staged identification; writes candidate card versions and the calibration record §30.9
ground.ingest mutate M1 Admit a log, a bench measurement or a scan; fit clocks; seal splits §30.5
ground.kit run M5 Build or check a replication kit §30.16
ground.predict mutate M5 Freeze a prediction for a planned real trial §30.11
ground.score run M5 Open sealed data once, score, retire the holdout, admit or reject the posterior §30.11
job
job.cancel admin M2 Ask the daemon to cancel; it drains at the kernel-batch boundary and names the last committed tick §32.10
job.find read M2 Find a job by idempotency key after a transport failure §32.7
job.list read M2 Jobs in the caller's namespace with state and progress §32.10
mission
mission.distinguish run M4 The smallest admissible intervention or instrument that separates alternatives §25.14
mission.refute run M1 A scoped impossibility bound, or a witness defeating one design and controller; the smallest relaxing change §25.3.1, §25.9
mission.revalidate run M4 Surviving certificates, invalidated regions, reruns and their cost after an edit (one engine with result.revalidate) §25.8
mission.separate run M4 A minimized, admissible pair of worlds in which a design ordering or a diagnosis changes §25.9
mission.show read M1 A stored answer by set (inner, outer, excluded, unresolved), ordered and paged §32.6
mission.synthesize run M1 Inner and outer design sets with witnesses, exclusions, unresolved cells and cost bounds §25.3
mission.transport run M8 Move a certified claim through a map between task interfaces with a bounded error, or return a counterexample naming the lost mode F; static core at M4. A skill artifact with a learned residual is skill.transport §25.3.1, §25.11
module
module.check read M1 Check a module's ports, parameter schema, local certificates and contract digest §14.6
module.list read M1 Modules in the catalog, by content hash §14.6
module.show read M1 A module's ports, parameters, guarantees and assumptions §14.6
module.substitute mutate M1 Replace a module at a path; reports leaf-local or global and what is reused §14.6
nemesis
nemesis.audit run M4 Audit a screening stage with stratified discards and a planted winner; the one screening audit, applied by the cascade of §28.12 §26.10
nemesis.bound run M3 Certify, refute or estimate a failure probability against a target §26.9
nemesis.cover read M3 Select a covering scene set and return it with its certificate §26.11
nemesis.hardset read, run M3 Show, add to, retire from and run the hard-world set of a class §26.8
nemesis.oracle run M3 Classify one world for one candidate: a witness, or the failed necessary condition §26.5
nemesis.search run M3 Adversarial worlds inside a declared legality profile, with the baseline arm's count at equal budget §26.4
nemesis.shrink run M3 Shrink a promoted failure to a minimal counterexample world and write the .fmcw §26.7
opt
opt.archive read M4 The quality-diversity archive of a campaign §28.8
opt.cascade run M4 The six-stage co-design cascade, with a control in every stage; solve.run calls it §28.8, §28.11
opt.start run M4 Start an optimization or a race; --family evaluates a family per dispatch §28.8
opt.status read M4 Progress, survivors and spend of a campaign §28.8
phylum
phylum.generate read M3 Sample designs from a generator with derivations and log-probabilities §17.15
phylum.gradient run M4 Paired finite-difference design gradient with intervals and divergence steps §17.13
phylum.map read M4 The quality-diversity map of a campaign or one dispatch §17.12
phylum.plan read M2 Buckets, padding overhead, bytes, the machine that fits a population; never runs physics §17.5
phylum.quotient read M3 Orbit representatives under Γ_obs and mission-digest classes for a design set §17.11
phylum.reuse read M3 For an edit: which cached results survive and the field that forced each invalidation §17.15
phylum.sweep run M2 Run a population of designs in mixed batches; a provisional scorecard per design §17.15
policy
policy.apply run M4 Apply a family policy to a design, with or without fine-tuning; refused out of distribution §23.11
predict
predict.register mutate M4 Register a prediction with an interval and a confidence before a run §28.17
predict.report read M4 Calibration of an agent's registered predictions §28.17
prove
prove.bundle run M1 Assemble a .frobcert bundle for a claim (mission slice at M1, full at M5) §12.4
prove.kernel read M0 The instance certificate of a kernel and what it states §12.4
prove.list read M0 Certificates and theorem cards with their classes and checkers §12.3
prove.reflect run M5 Promote an instance certificate through a reflected checker F §12.4
prove.verify read M0 Re-check certificates in tree; frob-verify repeats the check offline §12.4
report
report.campaign read M4 A campaign's modes, fallbacks, audits and phase ledger §28.18
report.design read M3 The evidence package of a design §28.18
result
result.revalidate run M4 After a change: which results and certificates survive, which are invalidated, what reruns cost §28.13
run
run.export run M1 Export a .frun bundle or a view of it §29.3
run.fork run M2 A new branch from a run and a checkpoint with a change set; returns its class (one of the five of §27.4), the earliest valid tick and the null-replay result; --classify-only restores nothing §29.8
run.show read M1 A run's manifest, standing and summary §32.6
scene
scene.accept run M3 The acceptance report of a pack §19.5
scene.bank read, admin M3 The resident set on a device, an admission estimate, eviction §19.15
scene.compile run M2 A pack from source geometry, with compile receipts §19.4
scene.fit run M3 A feasibility witness, an impossibility cut or unresolved for a footprint family and a route §19.11
scene.gen run M2 A pack from (family, parameters, seed): terrain at M2, interiors at M3 §19.6, §19.7
scene.hazards read M3 The hazard registry of an archetype with the provenance of every dimension §19.8
scene.import run M3 A pack with a loss report, a scale label and an unknown mask: assets at M3, real places at M5 §19.13
scene.list read M2 The scene catalog §19.3
scene.probe-request read M5 The measurements that would settle an unresolved answer §19.13
scene.purge admin M3 Remove a private scene pack and the lineage closure of everything derived from it §37.6
scene.retrofit run M3 The cheapest building amendment that flips a failing verdict, beside the cheapest redesign §19.12
scene.show read M2 A manifest, the hazards drawn and the feasibility tag §19.3
scene.split mutate M3 A split over scene groups, with feasibility counts §19.14
sense
sense.alias run M3 An alias witness with its class and the priced separating changes, or "none found" §20.12
sense.calibrate run M3 Extrinsic corrections with covariance and residual per edge: simulation at M3, imported logs at M5 §20.14
sense.causal-test run M2 Pass, or the first decision instant and channel at which causality fails §20.15
sense.observability run M3 The Gramian spectrum along a route, with named weak directions §20.11
sense.profile read M2 The sensor suite, cards, clocks, link models and queue capacities of a design and task §20.18
sense.schedule read M2 The exact boundary schedule over one repeat of the clock lattice, with lateness per event §20.4
sense.symmetry read M3 Γ_obs, the elements of Γ_mech it excludes and what excludes each §20.13
session
session.focus mutate M0 Switch the visible task cluster; lists the now-visible tools §32.12.4
session.open mutate M0 Open a session with scopes and budgets (tokens and budgets at M2) §32.13
session.show read M0 Scopes, budgets left, namespace and focus §32.13
shield
shield.budget run M3 Build and admit an energy budget for a design and a boundary §22.11
shield.check run M3 Replay a run against a budget or a shield §22.11, §22.12
shield.fit run M4 Rows, measured margins, backup and monitors for a design, a controller and a task family §22.12
shield.report read M4 Interventions, alarms, the violation bound and the return kept §22.12
sim
sim.estimate read M2 Cost, memory, capacities, expected Degraded rate and referee coverage; never runs physics §16.13, §32.9
sim.replay run M2 Reproduce a world from its address; --tier teleports it §29.8
sim.run run M0 Run worlds under a profile, a law and per-world designs: referee at M0, all tiers at M2. --profile takes a step profile (lockstep, strict, referee); determinism and precision profiles take --determinism and --precision (§35) §16.13
skill
skill.check run M4 A feasibility or infeasibility witness for a skill over a set of states §22.10
skill.compile run M4 A .fskill and a design to per-mode maps and a program §22.10
skill.show read M4 A skill artifact, its phases and assumptions §22.10
skill.transport run M8 Move a skill artifact to another body with a learned residual M. A certified claim moves through mission.transport §22.10
solve
solve.run run M4 One call from a task and a budget to a ranked set with verdicts; the agent-facing orchestration verb, which calls opt.cascade F §32.6.2
spark
spark.cache read, admin M2 The binary kernel cache: contents, hits, eviction §21.10
spark.check run M0 The CPU-versus-device check per kernel, with its currency §21.13
spark.devices read M0 Devices with capabilities, ceilings and current fingerprint digests §21.16
spark.fingerprint run M0 Measure and write the hardware fingerprint record §21.16
spark.place read M2 The placement plan and the residency map, before anything runs §21.12
spark.precompile run M2 Compile or load the kernel set of a shape class §21.10
spark.probe run M0 Arithmetic probes and the boundary corpus on a device §21.8, §21.15
study
study.compare read M3 Per metric: settled, tied or inconclusive, with intervals and exact pair counts §32.6.1
study.plan mutate M2 Bind a manifest and one study type; returns the plan address, the cost and the reachable verdicts §32.6.1
study.status read M2 Progress of a submitted study §32.6.1
study.submit run M2 Submit a planned study under an idempotency key §32.6.1
task
task.check read M1 Units, clocks, windows, reach against horizon, labelled examples, the mutation check §24.5
task.fixture run M1 Run a registered fixture's analytic layer or batch against its known answers §24.10
task.list read M1 Tasks, by content address §24.14
task.new mutate M1 Create a task from a document §24.4
task.settle run M1 Build or refresh the settled-pose cache for a model and task §24.7
task.show read M1 A task's sections, requirement and examples §24.4
task.verdict read M1 Evaluate a task's requirements on a recorded run; returns frob.verdict/1 §24.5
telemetry
telemetry.divergence read M2 First divergence between two runs, in exact mode along the digest chain or in tolerance mode §29.8
telemetry.energy read M1 The energy ledger and the created-energy audit §29.9
telemetry.export-html read M2 A replay as one self-contained HTML file §29.12; viewer text in §32.15, §32.24
telemetry.failures read M1 Failures by class, with first offending events §29.10
telemetry.histogram read M2 Deterministic integer log-bin histograms and quantiles §29.7
telemetry.inspect-pixel read M2 The quantity under a pixel with its unit, channel and world address §32.15
telemetry.query read M1 Columns by stream and range, paged against a committed frontier §29.4, §29.5
telemetry.stills read M2 A still or a contact sheet with overlays §20.9
telemetry.summary read M1 A token-budgeted run summary with handles for drill-down §29.12
train
train.distill run M4 Distill a teacher into a student policy §23.10
train.export read M2 Export a policy with its manifest and mapping table §23.7
train.family run M4 Pretrain a family policy for a morphology class, after the envelope check §23.11
train.inherit run M4 Start a child's policy from a donor through the typed edit that joins them §23.12
train.start run M2 Start training; algorithm, network, devices, tying and profile are arguments §23.6
train.status read M2 Return, steps, learner share and flags of a training run §23.6
train.stop admin M2 Stop a training run at a commit boundary §23.6

Counts (FACT about this table): 163 verbs in 34 clusters. By kind: 73 run, 73 read, 11 mutate, 3 admin, and 3 with two kinds. By first milestone: M0 11, M1 33, M2 31, M3 39, M4 35, M5 11, M8 3.

J.3 Verbs the chapters define that the mechanical inventory does not hold

The inventory matched one spelling, so it missed three groups. All are registry entries.

Verb Kind First milestone Purpose Defined in
doctor, capabilities, robot-docs, schema read M0 Operator verbs: toolchains, pins and devices; what is implemented; the agent guide; a schema with a minimal example §32.6, §32.17
session.close mutate M0 Close a session and release its reservations §32.6
job.status, job.wait read M2 Job state; a bounded wait on a job §32.10, §32.12.5
artifact.read, artifact.list, artifact.export read, read, run M1 Read by digest and byte range; list; export under the session's export root §32.6, §29
design.new, design.show, design.import, design.export, design.view mutate, read, mutate, read, read M1 Create from a template or a mission cell; show; import and export with a loss report; convert between the JSON and S-expression views §14, §32.6
analyze.<name> read M1 to M4 One verb per analysis A-01 to A-26 (analyze.symmetry is A-03); A-19 and A-26 read runs and never join check §28.4
algebra.irreps, algebra.orbits read M1 Isotypic decomposition and block types; orbit counts and one canonical representative per orbit §13.5, §13.6
actuator.list, actuator.show, actuator.check, actuator.envelope, actuator.thermal, actuator.bus read M1 Cards and their provenance; admission checks; the torque–speed envelope; the thermal steady state and runaway; the shared bus ceiling §15
control.synth, control.show run, read M1 Synthesize the baseline controller for a morphology class, with three outcomes; show it §22.4
fidelity.ledger, fidelity.energy, fidelity.coverage read M2 Ledger rows and frozen envelopes; created-energy totals; both coverage figures §16.13
fidelity.rank run M3 The rank-agreement record for a design set and a tier pair, with the permitted use per stratum (between controller rungs the record is eval.rank-agreement) §16.9
fidelity.modelform run M3 model-robust or model-conditional for a ranking (the rank-agreement record for a tier pair is eval.rank-agreement) §16.9, §16.13
fidelity.shadow admin M3 Start, stop and configure the background referee for a job §16.13
contact.laws, contact.probe read M1 The admitted laws per tier and profile; a law, cone or film evaluated at a contact state §18.13
contact.capacity, contact.audit read, run M2 Static contact maxima against capacities; the tunnelling audit §18.13
contact.clearance run M3 clear with a certificate, penetrates with a witness, or unknown §18.13
contact.soil, contact.response read, run M4 Sinkage and thrust on a soil card; the response batch F §18.13
fleet.status, fleet.plan read M4 Roles and queues of the two machines; the assignment by role affinity and estimated work §21.17
run.list read M1 Runs in the caller's namespace §32.6
study.cancel admin M2 Cancel a submitted study §32.6
mission.new, mission.check mutate, read M1 Create a query from a document or a template; admit it, refuse an empty or inconsistent domain, echo the quantifier order §32.6
result.show read M4 A stored result with its claim product and dependencies §32.6
report.run, report.mission read M3 The evidence package of a run; of a mission answer §32.6
cores.show read M3 A decision core's table, loss model, obligations and fallback §28.19
evidence.trace read M1 The evidence closure of a claim identifier §29.13
store.status, store.collect read, admin M2 Store size, pins and retention; a collection cycle with tombstones §29.16
module.characterize run M3 Characterize one module's capability table for the composed quasi-static screen §14.16
sense.visibility run M3 Visibility of each sensor along a nominal motion, with the robot's own limbs and payload as occluders §20.24
control.lift run M6 Fit and calibrate a lifted linear planning model for one soft-soil regime §22.20
task.audit run M3 Attack a task before any candidate is scored: foil bodies and intent invariants §24.20
eval.items read M3 The item bank of a battery and the sampling weights a close comparison used §24.21

That is 55 named verbs and the analyze family of 26, of which one is in J.2. The registry therefore holds 243 verbs (163 + 55 + 25). A compatibility tool, verb_invoke {verb, arguments}, exists on MCP only, for clients that never re-list (§32.12.4).

J.4 One name per verb

The registry holds no alias. Every verb is registered under the name its owner chapter gives it, §32.6 lists the same names, and a lint refuses a second spelling of a registered verb. Where two chapters once named one mechanism, the owner's name is the registered one and the other name is not a verb:

Mechanism Registered verb Owner
The separating pair of worlds mission.separate; its search machinery is §26's §25.3.1
Forks and their classification run.fork; the classes are those of §27.4 §29.8
First divergence of two runs telemetry.divergence §29.8
Interventions and attribution autopsy.intervene, then autopsy.attribute §27.14
The screening audit nemesis.audit; the cascade applies it §26.10
A bound on a failure rate; the hard-world set nemesis.bound; nemesis.hardset §26.12
The model-form rank check (A-19) fidelity.modelform §16.9
The rank-agreement record, for rungs and for tier pairs eval.rank-agreement §28.10
The pre-analysis of a fixed-n study eval.preanalyze; study.plan calls it §24.12
Certificate bundles prove.bundle, prove.verify, prove.list §12
Calibration ground.ingest, ground.identify, ground.score §30.16
Structure and the build packet foundry.size, foundry.optimize, foundry.check, foundry.export (--with-firmware under its feature) §31.15
The co-design cascade and its one-call form opt.cascade; solve.run is the agent-facing orchestration verb that calls it §28.8, §32.6.2
Transport mission.transport for a certified claim through an interface map F; skill.transport for a skill artifact with a learned residual M §25.3.1, §22.10
The self-contained replay telemetry.export-html, in the telemetry cluster; the viewer text is §32.15 §29.12

J.5 What an agent sees: task clusters of at most seven tools

A registry cluster is a namespace and can be large: scene has thirteen verbs in J.2, eval nine, telemetry nine. What an agent sees is a task cluster: at most seven tools chosen for one activity, declared in the registry beside the verbs (§32.12.4). A verb may sit in several task clusters and a lint requires every verb to sit in at least one. Three base tools are always listed and are not counted: session_focus, job_wait, job_cancel. An agent switches with session_focus {cluster}; focus changes context size, never authority, which is the capability token. TARGET: the definitions of the base tools and one task cluster occupy at most 12 kB of tools/list.

The agent's task Task cluster Tools listed
Find out what exists (default) orient capabilities, doctor, robot_docs, schema, design_templates, scene_list, session_show
Make and change a design author design_new, design_show, design_edit, design_diff, design_check, design_import, control_synth
Ask static questions analyze-body, analyze-motion, analyze-budget The analyses of §28.4, at most seven per cluster
Estimate, run, look simulate sim_estimate, sim_run, sim_replay, run_fork, telemetry_summary, telemetry_failures, telemetry_stills
Find why a run failed diagnose explain_run, autopsy_intervene, autopsy_attribute, autopsy_show, telemetry_query, telemetry_inspect_pixel, telemetry_energy
Compare designs in paired studies compare study_plan, study_submit, study_status, study_compare, eval_promote, experiment_suggest, predict_register
Ask which designs can do a mission mission mission_new, mission_check, mission_synthesize, mission_refute, mission_distinguish, mission_show, result_revalidate
Attack a design with adversarial worlds attack nemesis_search, nemesis_shrink, mission_separate, nemesis_bound, nemesis_oracle, nemesis_hardset, scene_show
Qualify a design and bundle its certificates qualify eval_qualify, eval_scorecard, eval_ledger, prove_bundle, prove_verify, report_design, prove_list
Train a policy learn train_start, train_status, train_stop, train_export, eval_run, sim_estimate, telemetry_summary
Make and inspect places places scene_gen, scene_import, scene_compile, scene_list, scene_show, telemetry_stills, design_check
Search a design space search opt_start, opt_status, opt_archive, design_bisect, design_blame, solve_run, experiment_suggest
Calibrate against reality reality ground_ingest, ground_identify, ground_predict, ground_score, ground_band, predict_report, report_run
Size structure and write a build packet make foundry_size, foundry_optimize, foundry_check, foundry_tolerance, foundry_export, prove_bundle, report_design
Watch jobs, artifacts, devices, the session operate The job, artifact, device and session verbs; the registry holds the assignment

The fourteen named rows are the principal clusters of §32.12.4; with the two further analysis clusters and operate there are seventeen. Verbs of the subsystem clusters that no principal row lists (phylum, fidelity, contact, sense, gait, skill, shield, task, module, actuator, spark, fleet, and the family-policy and ladder verbs) are assigned by the registry to further task clusters of at most seven. DESIGN, a starting assignment that the registry lint checks: families (the seven phylum verbs); fidelity (its five verbs with eval_promote and eval_rank_agreement); audit (task_audit, eval_items, module_characterize, sense_visibility, control_lift, the verbs of J.3 that later subsections define); contact (its seven verbs); sensing (the seven sense verbs); gaits (the four gait verbs with control_ladder, control_mpc and control_symmetry); shield (the four shield verbs with skill_compile, skill_check and skill_show); tasks (the seven task verbs); devices (the seven spark verbs); inherit (train_family, train_inherit, train_distill, policy_apply, eval_detect, fidelity_modelform, eval_rank_agreement); ladder (opt_cascade, nemesis_audit, eval_rank_agreement, cores_show, report_campaign, explain_compare, predict_report).