Status: <auditing facts / ready to author / qualification pending / supported>. Follow the compatibility guide. Required unknowns block the affected capability; optional unavailable values state their consequences.
Sources and scope
- Environment/task/asset/robot/controller revisions:
- Accepted baseline and current changes:
- Affected backends, arms, modes and defaults:
- Frozen/live sources and reusable evidence:
Task and evaluation
| Task/version | Public clauses and sources | Official verdict boundary/timing | Release/stability/reset requirements | Delivery consumer | Evidence |
|---|---|---|---|---|---|
| <task> | <semantics> | <owner> | <conditions> | <path/hash> | <reference> |
Record true/false/unknown, termination/stop/fault distinctions, episode/round/seed denominators, retries/exclusions, step/time counters, protocol differences and proof that private predicates/GT stay outside policy input.
Constants, frames and units
| Meaning | Source revision/location | Source value/unit | Target encoding/range | Frame/arm/point | Nominal/calibrated/measured/unknown | Conversion owner | Consumers | Independent check |
|---|---|---|---|---|---|---|---|---|
| <quantity> | <value> | <target> | <frame> | <status> | <function> | <paths> | <evidence> |
Include joint order, link/TCP/contact transforms, camera calibration/depth scale, bounds/tolerances, gripper direction/width, dt/rates, pixel/UV encoding and invalid/saturation rules. Required gaps and optional degraded behavior:
Delivery and acceptance
| Fact owner | Descriptor/profile/Bundle/tool/controller consumer | Expected | Fresh resolved value | Actual delivery/execution evidence | Outcome |
|---|---|---|---|---|---|
| <owner> | <paths> | <value/hash> | <value/hash> | <reference> | <pass/gap> |
- Conversion count/direction and no duplicate offsets:
- Schema/result/receipt/observation/Viewer consistency:
- Explicit provider/context/image/budget settings:
- Known-value, nonidentity pose, both-arm, boundary and invalid-input checks:
- Official verdict, terminal refusal, skipped stages and close checks:
- Case/dependency reuse versus concrete new physical work:
- CPU/GPU/memory/slots, parallel schedule and wall-time estimate:
- Exact source, fresh preflight and launch authorization:
- Unsupported capabilities and unresolved questions: