# Incident Report

Formal artifact: `Cell Truth Report`.

This report summarizes one recorded run: a saved sequence of object positions and timestamps from a bounded workcell.

## What happened

- Metriplane reviewed 70.0 s of recorded activity.
- It recorded 6 events and grouped them into 1 incident.
- An event is one observed change, such as an object arriving or a required tool being absent.
- An incident groups related events that need review because an expected process condition was not met.
- Incident `INC-0001` (warning): torque driver 1 missing during Torque driver available before fastening. Torque driver available before fastening waited because torque driver 1 was absent.
- Suggested follow-up: Add a required-tool staging check. INC-0001 shows a required asset was absent while a process step waited. Add a visible pre-step tool/material check.

## Why it was flagged

Process rules describe the expected steps, required objects and locations, and allowed waiting times. Metriplane flags a deviation when the recorded run does not meet one of those rules.

| reason | severity | expected step | object | supporting event records |
|---|---|---|---|---|
| missing required asset (`missing_required_asset`) | warning | `torque_driver_available` | `torque_driver_1` | `evt_0003`, `evt_0004` |

## When it happened

The times below are measured from the start of the recorded run.

| time | what was observed | object | technical event record |
|---:|---|---|---|
| 0.0 s | Kit arrives at the cell completed. | `kit_bin_1` | `evt_0001` / `step_completed` |
| 10.0 s | Workpiece arrives at station A completed. | `workpiece_7` | `evt_0002` / `step_completed` |
| 20.0 s | torque_driver_1 was not present for Torque driver available before fastening. | `torque_driver_1` | `evt_0003` / `required_asset_missing` |
| 55.0 s | Torque driver available before fastening waited 35.0 s for torque_driver_1. | `torque_driver_1` | `evt_0004` / `step_delayed` |
| 70.0 s | Torque driver 1 was present for Torque driver available before fastening. | `torque_driver_1` | `evt_0005` / `required_asset_present` |
| 70.0 s | Torque driver available before fastening completed. | `torque_driver_1` | `evt_0006` / `step_completed` |

## Evidence that was saved

An evidence bundle is a checksummed ZIP that keeps the incident report and supporting records together so another person can verify what was reviewed.
- Evidence bundle for `INC-0001`: `evidence_bundles/INC-0001.zip`
- Event records: `physical_event_log.jsonl`
- Incident records: `incidents.jsonl`
- Supporting recorded state: `state_segment.jsonl`
- Formal Cell Truth Report: `cell_truth_report.html`

## Repeatable check that was generated

A regression check is a generated test that replays the saved incident and checks that the expected events and incident still appear within declared timing tolerances.

Deterministic replay uses the saved inputs and recorded time sequence instead of live timing, so repeated evaluations can be compared consistently.
- Repeatable check for `INC-0001`: `regression_tests/INC-0001.yaml`

## Limits of this result

- This result is derived from replayed calibrated planar state, not a fresh judgement of raw video.
- It depends on the tracked or tagged objects and the process rules supplied for this run.
- It does not prove root cause; suggested follow-ups require before-and-after validation.
- It is not a certified safety or quality decision and does not control machinery.