off-scope-finding-offload
Off-Scope Findings — Park, Don’t Interrupt
Section titled “Off-Scope Findings — Park, Don’t Interrupt”A finding the work under hand did not go looking for is not a decision about that work: park it. What qualifies is data, not prose (offscopeFindings.classes / .neverOffload in the resolved t1k-config-*.json are the SSOT; never restate either).
The veto. Anything that would change the deliverable under work stays inline; anything destructive, touching credentials or secrets, changing permissions/config, or needing consent is never parked, always raised.
On discovery: park it, do not act · never raise an AskUserQuestion for it · never list it under a plan’s or report’s unresolved items. At turn end, one line naming what was parked and where it went. A silent park is not a report. Degraded path (offload hooks absent): the existing queue path, never a silent drop. Full reference: docs/off-scope-finding-offload.md.
Full reference: docs/off-scope-finding-offload.md.