Two QPS entries: clean replay and drift detected.
The two scenarios that every QPS deployment hits in the first month. Both entries are public-safe analogues of patterns implemented in production at two enterprises under NDA.
Clean replay
qps_technoflex_supplier_CAP-7a3f9e2b4d8c1062_20260501
The Helvian supplier manifold's QPS entry with two replays, both with drift_detected: false. The typical operational case: agent pulls L2 telemetry, sourcing lead verifies later, numbers match. Demonstrates the generation/executions split plus the access_control and ttl blocks.
Drift detected
qps_technoflex_supplier_CAP-83ab12c4f790e102_20260415
The Vorenza ChemTech entry on Industrial Colorants & Pigments. Three executions: two clean, then a finance reconciliation pass that catches row_count_increase from three late-arriving April POs. drift_delta quantifies the shift (HHI 0.947 to 0.943, within rounding) and drift_note records the impact assessment so the next reader can skip rebuilding.
Each viewer page surfaces a glossary of the QPS fields and links to the Operations reference for checksum tradeoffs, drift response patterns, retention defaults, and security guidance.