Read public machine state, command history and operating context.
→A08 Repair Runtime
Keep the model aligned with the machine.
A08 sits beside the controller. It predicts machine response, detects consequential mismatch and routes only corrections that pass an independent check.
Forecast the expected effect of candidate controls.
→Measure when observed dynamics leave the supported model.
→Compile a bounded correction around the affected mechanism.
→Test new competence, old-regime retention and declared limits.
→Activate an immutable model version or abstain.
Integration boundary
The controller remains in control.
A08 is not a replacement policy and does not repair hardware. It maintains a predictive model of the machine and exposes a verified version to the existing planning or control stack.
POST /v1/observeValidate public state and provenancePOST /v1/predictForecast action-conditioned transitionsPOST /v1/detectMeasure a consequential model gapPOST /v1/repairCompile a bounded candidate patchPOST /v1/verifyAccept, reject or request more evidencePOST /v1/routeResolve the approved versionRepair contract
Small enough to inspect. Strict enough to reject.
A candidate repair identifies its affected mechanism, evidence, bounds, parent model and rollback path. Failing any check leaves the current version unchanged.
Read the package contract →repair.json{
"mechanism": "left_leg_command_response",
"parent": "sha256:current-model",
"candidate": { "transform": "invert_sign" },
"evidence": {
"acquisition": "trace:858110-a",
"verification": "trace:858110-v"
},
"decision": "verified"
}Product surface
One loop, three deployable components.
The current system is available for research and design-partner evaluation. Physical execution remains subject to the partner's safety and control authority.
Self-model runtime
Prediction, uncertainty and change detection close to the machine telemetry.
Repair gate
Independent evaluation of competence, regressions, constraints and provenance.
Evidence registry
Immutable model versions, repair lineage, deployment scope and rollback.
Why keep the registry
Distribution follows verified use.
A08 can eventually support third-party machine models and commercial repair modules. The registry is valuable because it carries operational evidence and compatibility, not because it contains a large number of model files.
Open the model registry →01One machine
Qualify a self-model against a real operating change.
02One fleet
Reuse verified versions across compatible machines and sites.
03One ecosystem
Publish proven models and repairs through a common evidence contract.
Design partnership
Start with one machine and one measurable failure mode.
A08 will define the model boundary, evidence protocol and shadow deployment with your engineering team.