Read the expected mixed-revision bundle
Synthetic expected bundle is headline H2, artwork A1 and action C3. A1 remains the specified artwork despite newer draft A2. Observed P1 serves H2/A1/C2, P2 H2/A1/C3. Local reconciliation uses the exact expected bundle; it does not approve drafts or infer live state from a publishing receipt.
| Placement | Observed | Mismatch |
|---|---|---|
| P1 | H2/A1/C2 | Action C2→C3 |
| P2 | H2/A1/C3 | None |
Compare observed placement tuples
- Load expected H2/A1/C3
- Compare all placement components
- Request P1 action C3
- Reobserve P1 tuple
Changing A1 to draft A2 merely to use the highest revision would create a new mismatch.
How many component patches are required?
Show the worked answer
One, P1’s action. Headline and artwork already match on both placements; P2 needs no patch.
Request the exact component patch
| Case | Decision or result | Reason |
|---|---|---|
| Replace every component with latest draft | Reject extra scope | Expected artwork A1 |
| Patch only P1/C2→C3 | Matches discrepancy | One stale action |
Close the discrepancy with a new observed tuple, keeping the earlier observation. A patch request alone is not evidence of what the placement serves.