Start with the accepted baseline
Choose a safely simulated or approved fixture. Record the accepted baseline and closure evidence, then capture the new request and its designated intake channel separately. Do not relabel an accepted record as open simply because a message arrives.
NIST defines configuration control as controlling modifications before, during, and after implementation. That frames explicit proposed-change handling; it does not prescribe a client policy, contract term, or priority.
Run a bounded receipt check
The local validator requires closure evidence, a new request, reopening authority, explicit impact disposition, impact owner, procedure, and escalation route:
node --test sites/howtox.com/evidence/P151/reopened-work-receipt.test.mjs
It accepts review, defer, or new request as a declared disposition; it does not decide which is correct. It does not contact a customer, calculate price, alter a ticket, or verify an integration.
Stop where authority or impact is hidden
Pause the handoff if nobody can show what was accepted, name the request source, identify the disposition owner, or own impact review. A manual procedure can be the smallest credible improvement while those questions are resolved.
For another bounded change boundary, see Test a CSV Import Before Coworkers Rely on It. For record agreement across systems, see Test Booking-to-Calendar Synchronization Before Staff Rely on It. For recovery after an attendance report, see Test Missed-Appointment Recovery Before Staff Rely on It.
Does this receipt decide whether a request is in scope or billable?
No. It keeps authority and impact review visible. Commercial terms and real-system decisions remain with accountable people and their approved procedure.