failure-escalationlisted

# Failure Escalation ## Purpose Break unproductive repair loops and return the problem to the lowest higher layer capable of correcting its cause safely. ## Trigger Run when the same failure persists after a bounded repair cycle, patches create new failures, diagnosis remains `UNKNOWN`, or evidence points above the current implementation layer. ## Inputs - Failure/RCA records, attempt history, diffs, test/build evidence, and current revision. - Classified or suspected responsible layers and confidence. - Current Stage, Minimum Necessary Path, Workflow Level, Checkpoint, and rollback points. - Affected Artifacts, Components, Contracts, assumptions, decisions, and risks. ## Prerequisites - Stop further local edits and preserve the failing workspace/evidence. - Distinguish a genuinely new failure from recurrence of the same cause. ## Procedure 1. Declare `STOP_LOCAL_PATCHING` and record the escalation trigger. 2. Summarize attempted repairs, outcomes, and why another local patch is unjustified. 3. Review or refresh Root Cause Analysis across Requirement, Architecture, Detailed Design, Contract, Interface, Data, Implementation, Test, and Environment. 4. Identify the earliest responsible layer with enough evidence to act. 5. Determine whether to rework locally with a new bounded hypothesis, transfer to a specialist, or roll back Stage/Artifact decisions. 6. Select a safe rollback/checkpoint or preserve current state for comparison. 7. Mark affected Artifacts `STALE`/`UNV