# Completed fictional measurement contract: workflow review

This fictional example defines the events, owners and checks for the workflow-review route. The definitions support a planning review; live implementation still needs verification.

## Record control

| Field | Value |
| --- | --- |
| Contract | `maestro.facebook_ad_funnel.route.v1` |
| Record ID | `fixture-direct-workflow-review` |
| Route version | `1` |
| Measurement owner | Analytics owner |
| Checked at | Planning fixture only |

## Measurement layers

| Layer | Event or outcome | Exact trigger or rule | Join key name | Owner | Status | Source ID | What it establishes | What it does not establish |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Platform | `Lead` | Send after the destination returns a successful workflow-review request response. | `event_id` | Analytics owner | supplied | fixture-direct-brief | The intended Meta event and local trigger. | Firing, site receipt, CRM acceptance, revenue or causality. |
| Site | `workflow_review_requested` | Record after server validation accepts the request and creates one event ID. | `event_id` | Web owner | supplied | fixture-direct-brief | The intended accepted site action. | CRM receipt, qualification or Meta causality. |
| CRM | `qualified_review`; `review_denied` | Accept only when the company has 20+ employees, the named recurring request loses an owner or due date at least twice per month, and a workflow owner accepts the request. Deny when any condition fails. | `event_id` | RevOps | supplied | fixture-direct-brief | Fictional executable lifecycle rule. | Meeting held, revenue or Meta causality. |
| Commercial | `review_completed` | Offer owner records that the scheduled review occurred. | `event_id` | Offer owner | supplied | fixture-direct-brief | The intended completion definition. | Revenue, satisfaction or causal lift. |

## Join and deduplication

- **Join key name:** `event_id`
- **Created:** Server creates one opaque event ID after validation succeeds.
- **Stored:** Site event, platform event payload and CRM test record.
- **Deduplication rule:** Browser and server copies with the same `event_id` count as one accepted request.
- **Duplicate test:** Submit one fixture, replay the server event once, and require one site request, one platform event identity and one CRM record.
- **PII boundary:** This file contains only the key name. It contains no real person's identifier.

## Reporting and attribution

- **Reporting window:** Seven calendar days after the accepted request for operational reconciliation.
- **Timezone:** America/New_York for this fictional fixture.
- **Late event rule:** Reconcile a late CRM status by `event_id`; do not rewrite the original site timestamp.
- **Attribution limit:** A Meta-attributed `Lead` does not prove CRM qualification, a completed review, revenue or causal effect.

## Verification queries

1. In the platform, find exactly one current event named `Lead` with the fixture `event_id` and expected trigger timestamp.
2. On the site, find exactly one accepted `workflow_review_requested` event for the same ID.
3. In the CRM, find exactly one record with the same ID. A 45-person company with three ownerless requests per month and an accepting owner must record `qualified_review`; a 12-person company must record `review_denied`.
4. For the commercial outcome, find `review_completed` only when the offer owner records that the review occurred.
5. Assign event mismatches to Analytics and CRM-rule mismatches to RevOps. Keep the route on Launch Hold until they are resolved.

## Native delivery receipts

| Receipt ID | Status | Owner | Evidence needed | Result |
| --- | --- | --- | --- | --- |
| receipt-platform | Unknown | Analytics owner | Current native event readback | Launch Hold |
| receipt-site | planned | Web owner | Test request and server response | Launch Hold |
| receipt-crm | pending | RevOps | Matching CRM record and rule result | Launch Hold |
| receipt-dedup | Unknown | Analytics owner | Browser/server replay fixture | Launch Hold |
| receipt-suppression | denied | RevOps | Current exclusion readback | Launch Hold; denied is not a pass or false. |

## Readiness

- **Draft status:** **Draft Complete** only for this reviewed fictional meaning. The definitions, owners, executable acceptance rules, key and mismatch actions are present. Any meaning-bearing edit returns Draft Hold until the four-part coherence review is repeated.
- **Launch status:** **Launch Hold**. No required current native receipt is verified.
- **Next action:** Execute the five native fixtures and save the account, destination and CRM readbacks tied to route version 1.

Changing the offer, destination, trigger, join rule or CRM acceptance rule invalidates the prior route approval and this measurement handoff.