The life of one Intent
One statement-of-work request, followed end-to-end: decision → sourcing → contract → signature → committed spend → audit. The same Intent ID rides every hop, so months later one query still explains the whole engagement.
Lena Brandt, platform lead in the EMEA services program, needs the EU reporting warehouse migrated before the Q4 close — fixed scope, roughly twelve weeks. Triage diagnoses the request instead of routing it straight to a requisition form.
What Triage concluded
work_type service · channel SoW (confidence 0.87) · risk medium. Contingent labour was considered and rejected: the ask is a deliverable with acceptance criteria, not a seat to fill. That reasoning is captured — not lost in a hallway conversation.
The Compliance File
Request summary, classification rationale and confidence, constraints and assumptions, alternates considered, required approvals — bundled and referenced from the Intent Record at df://emea-services/itn_Vq3kX9mR2d/v2. It travels with the decision into every downstream system.
v1 was minted straight from Triage output. Mapping preflight for the Coupa step found one gap — cost_center_id is mandatory there — so composerID raised an enrichment request back to Lena instead of failing the publish. Her answer produced v2. No reject/resubmit loop, no re-keying.
The Channel Registry resolves the SoW channel for this program into an ordered destination chain. Each step carries its own mapping profile and idempotency key — swap Coupa for SAP Ariba by swapping a mapping profile; the Intent Record doesn't change.
Every create/update is keyed, logged, and written back. Each destination object also carries the Intent ID — a custom field, a workflow property, an envelope field — so correlation survives outside composerID too.
| When (2025) | Destination | External object | Intent ID carried as | Status |
|---|---|---|---|---|
| Jun 08 | Globality | GLB-EVT-88412 | event reference | created |
| Jun 15 | Globality | award → Meridian Data Partners | — | awarded |
| Jun 16 | Ironclad | WF-2419 · RCD-99871 (Statement of Work) | workflow property intentId | launched |
| Jun 17 | DocuSign | envelope 9f2c1e77-… | textCustomField intent_id | sent |
| Jun 19 | DocuSign | certificate of completion | — | completed |
| Jun 22 | Coupa | REQ-55208 → PO CPO-104233 | custom field intent-id | PO issued · €144,000 |
Webhooks feed the intent timeline from every destination. In August, a €4,200 change order was keyed directly into the Coupa PO — human-in-the-loop drift. Reconciliation caught the delta between the destination and the last-published intent; program policy said require re-approval, not silently accept.
| When (2025) | Event | Detail |
|---|---|---|
| Jul 07 | delivery_started | Meridian mobilised; fixed-scope milestones, no timesheets |
| Aug 14 | drift_detected | drift PO amount 144,000 → 148,200 (edited in Coupa) |
| Aug 15 | reapproved · override_event | Business owner approved the change order; intent → v3 |
| Oct 02 | invoices_matched | €148,200 settled against CPO-104233 |
| Oct 02 | closed | Timeline sealed — decision to reconciliation, one key |
Any republish after the change order uses v3 keys (…-3-coupa); retries of stale v2 keys stay inert by design.
Months on, finance asks the question every program eventually gets. Without a spine, the answer is archaeology across five systems. Here, it's one query by Intent ID.
For the exec
No orphan spend. Every euro traces to a scored, defensible decision — with the alternates considered on record.
For procurement & HR
One front door, enrichment instead of rejection loops, and the same request experience whichever systems sit underneath.
For the CTO
Deterministic keys, mapping-profile portability, evidence propagation. Integration as policy, not as projects.
All identifiers, parties and amounts on this page are illustrative.