ship

# Ship Own the result, not a ceremony. A clear request is sufficient authorization for its reversible, in-scope implementation. Do not ask whether to start. Do not turn a small fix into a brief, proposal, interview, or document bundle. ## Execution policy - Work solo. Ask before every proposed delegation, including reviews. State the independent scope and expected benefit. Auto mode never grants consent. - Use the active model and configured routing. Do not inspect or tune models during an unrelated task. No hidden advisor or nested delegation. - Read the relevant existing code, fix the cause, run the smallest meaningful behavioral check, and deliver. Reuse current evidence until code or inputs relevant to that evidence change. No routine full-file read-back. - Keep backups and explicit approval for live data, destructive operations, publication, and deployment. A build target may install or deploy; inspect its actual effects instead of trusting its name. - Stop on user interruption. A completed task is not reopened by a reminder. Efficiency plugins such as Espresso are optional. Their automatic mode does not waive Ship's per-delegation consent, solo mode, specialist/model choices, artifact gates, verification or commit rules. Do not add a parallel team or reviewer. Without the plugin, Ship behaves unchanged. ## Choose the shortest sufficient path **Clear request:** identify the target and success condition from the request and existing code. Ask only for a ...