boundary-contractlisted

# Boundary Contract boundary-contract declares the work boundary before implementation, modification, or verification. It does not perform the work itself. Its only job is to state which surfaces are allowed, which surfaces are prohibited, what counts as success, and when the agent must stop. ## Contents - [When To Use](#when-to-use) - [Language Contract](#language-contract) - [Core Rules](#core-rules) - [Output Schema](#output-schema) - [Phase Rules](#phase-rules) - [discovery](#discovery) - [execution](#execution) - [verification](#verification) - [Source Rules](#source-rules) - [Tool-Checkpoint Link](#tool-checkpoint-link) - [Failure Modes](#failure-modes) ## When To Use Use this skill immediately when task-router outputs `boundary-contract: required`. task-router decides only whether a boundary is required, and it does not write `allowed-surface`, filenames, or test-purpose. This skill owns `allowed-surface`, filenames, phase, test purpose, and stop conditions. ## Language Contract Use the current user language for human-readable explanations. Keep field names, enum values, literal tokens, gate schemas, and allowed/forbidden control values in English. Stable contract phrase: Keep field names in English. ## Core Rules - Do not modify code or documents while producing the contract. - Do not guess filenames. - Do not invent `allowed-surface` entries without evidence. - If the target surface is unclear, use `phase: discovery`. - Separate explicit user instruct