M5 Recovery and Assurance Integration

Objective

Make the evidence chain automatic: faults, tests, and measured artifacts flow into the assurance data plane without manual rework.

Scope

Integration:

GoMyRobotOS
      │
      ├── GoMyRobotFault
      ├── GoMyRobotBench
      ├── GoMyRobotVerify
      └── GoMyRobotAssure

Generation:

partition configuration
      +
image identity
      +
test results
      +
fault results
      +
timing results
      +
deployment profile
      ↓
Evidence Graph

Deliverables

  • automatic emission of evidence inputs (as specified in [assurance/evidence-model] (../assurance/evidence-model))

  • automatic inclusion of recovery actions + T_* timings (from [validation/recovery] (../validation/recovery))

  • every recovery claim in the graph carries the Guard independence stage it was demonstrated under

  • requirement → field → test → result chain populated for the reference flight partition

  • interface documentation for the four external products (what each consumes, in what format, and what it must not assume)

Tests / acceptance gate

Faults, tests and artifacts automatically feed assurance.

“Automatically” is the gate: no human-copying of results into a spreadsheet. The demonstration is: inject a declared fault class, observe the contractual recovery, and confirm the resulting evidence node appears in the graph feed without human intervention.

Current status

Planned (after M3 measurement machinery exists to feed).

Known limitations

  • M5 is a data-plane integration; it does not build an assurance argument (that is GoMyRobotAssure’s job) and does not certify anything.

  • What actually arrives in the graph is a joint product of the four external products, M5 ships the GoMyRobotOS side of each interface and a reference dataset, not the external tools themselves.

  • “Automatic feed” ≠ “continuous feed”: the integration is demonstrated per milestone dataset first; any higher-frequency claims come later with their own gate.