SYNTHETIC HANDOFF EXAMPLE — NOT A PRODUCT DEMONSTRATION
9 September 2026. Fictional names and records only.

Question: May the successor close the repeated maintenance exception?
SOP-17 v1 §4, superseded: shift lead may close without a second review.
SOP-17 v2 §4, current: operations-owner approval is required before closure.
HANDOFF-9 v1 §2, unverified: former lead said last month's issue was approved.
Approval record: unavailable to this reader. Its contents are not disclosed.

Expected answer: keep closure on hold. SOP-17 v2 §4 governs this fixture;
the superseded instruction and unverified handoff note do not establish approval.
Morgan, the fictional operations owner, must review permissible evidence and
record approve, reject or request more information before closure.

Expected task record: owner Morgan; action verify approval; due before closure;
status awaiting owner review; citations SOP-17:v2:4; exception evidence unavailable.
No actual person has accepted this task. No connector, ACL enforcement, source
freshness, answer quality or product integration has been demonstrated by this file.

Stop: unverifiable source status, permission or approval keeps closure on hold.
Use the existing owner review process. Do not broaden permissions to force an answer.