Service promise, then the hold.
Halo-inspired CRM analogue. Workday-like worker. SAP-like business partner and invoice. No edition is claimed. No volume is claimed. Draft-only agent designed; never sends; not deployed.
- Account ACC-61003, Harbour Grid Municipal, exists on the fictional CRM.
- CASE-61003 opens on 6 October 2026 with a restoration promise of 20 October. Stock is not confirmed. That is the defect in DATA-001.
- Service coordinator WKR-61003-01 acknowledges the date. The acknowledgement is a human act.
- Parts stay unconfirmed the same afternoon.
- Canonical partner BP-61003 and alias BP-61003-A both point at the account. The alias is a duplicate suspect.
- Billing analyst WKR-61003-02 raises INV-61003 and holds it. Amount: blank. Not measured.
- Data steward WKR-61003-03 reviews the join and does not merge it.
- No agent acts. AGT-61003-DRAFT is not deployed, may_act_on_case stays no, and does not count toward the 50,000 humans.
Day 16 — remediation design (fixture unchanged)
A stock-confirmed gate belongs before Amina acknowledges a promise. If parts are unconfirmed, she may refuse the date or publish an explicit unconfirmed status. Duplicate BP-61003-A stays unmerged. INV-61003 stays held. The published sample still shows the defect on purpose. See data join remediation.
Day 17–19 — draft only
AGT-61003-DRAFT may propose a schedule note for Amina only. It never sends to the customer or crew, never clears a hold, never merges partners. Red-team pass conditions are hard gates. Handoffs are on the people page.
Timestamps are in data/sample/process_events.csv. They are evidence. They are not a cycle-time KPI.
The three owners Day 22 Org map
Forty O*NET tasks on this path are listed in northwater_ai_workloads.csv. Human gates are on each row. Safety-critical work is human-only. Nothing in that file is a measured saving. Day 20 ranks send/act as explicit no-go.