Replay trace contract

PVE Storage Guard records metric semantics before it evaluates evidence. A synthetic trace, a modeled scenario, or another window derived from the same incident can be useful without being independent production evidence.

Every candidate trace declares its source kind, independence group, storage and workload classes, sampling interval, sanitization status, write-wait statistic and measurement layer, full window duration, window aggregation, and provenance. Relative offsets replace host timestamps and identities. Completeness uses the declared window, so missing samples at its beginning or end cannot disappear through cropping. New v1alpha2 traces represent management status as healthy, unhealthy, or unknown; v1alpha1 remains readable for diagnostics but cannot pass promotion.

The current controller API consumes a storage-domain p95 observation. Diskstats average service time and ZFS total-wait must retain those labels; neither can be renamed as I/O p95. The reference incident is therefore a pressure-proxy replay, not production p95 threshold calibration.

An independent observed trace currently requires a distinct independence group, at least 600 seconds, at least 95% structural, valid-wait, and known-management completeness, known storage/workload classes, compatible storage-domain p95 semantics, and a clean structural validation result.

python3 poc/trace_contract.py candidate.json \
  --reference-group reference-incident

The schema and validator live in the public repository. No qualifying second trace is claimed yet. Passing the machine gate is necessary but cannot prove a self-declared provenance; source hashing, redaction review, and human evidence approval remain required.

The internal ITOps draft now has a pure v1alpha2 builder for reviewed metric windows. It preserves the declared window and gaps, removes absolute times and internal selection identifiers, and fixes diskstats evidence to average, none, and derived at the block-device layer. Missing management data is retained as explicit unknown, never assumed healthy. It has no route, writer, scheduler, or publication side effect. A separate telemetry mapping is still required before true p95 evidence can be exported or qualify for the independent-trace gate.

Review the external trace research before importing third-party data.