القائمة
Load when the stop gate blocks twice on the same task. Do not load for ordinary unfinished work, first gate blocks, or reports where no completion claim is being made.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | completion-gate |
| description | Load when the stop gate blocks twice on the same task. Do not load for ordinary unfinished work, first gate blocks, or reports where no completion claim is being made. |
Extend charter §7 when the stop gate repeats. Treat the gate as a diagnostic, not a wording problem.
| Condition | What it means | Honest resolution |
|---|---|---|
| Open tasks | Task tracking still has work not completed or blocked. | Complete the task, or mark it blocked with evidence and user-only dependency. |
Failing last_test | The latest recorded validation failed. | Fix and re-run, or report the failure as remaining risk with exact output. |
Empty verification.md on workbench tasks | No verification record exists for a task that required one. | Record checks run, results, skipped checks, and reasons. |
| Completion-claim heuristic | The final message claims done without enough evidence. | Remove the claim or add direct evidence from files, tests, or observations. |
Use only when the task genuinely cannot complete inside the contract.
Blocked by:
Evidence:
What would unblock:
Work left untouched:
Satisfying the gate with hollow content violates charter contract rule 5. The gate is a floor, not the standard. A passing gate can still hide a false claim; remove the claim or verify it.
Load before implementing anything that runs continuously or per-item at scale — animation and render loops, timers, pollers, per-request middleware, large-collection iteration. Do not load for one-shot scripts, setup code, or paths that run a bounded handful of times.
Load before hand-writing or hand-editing files a toolchain normally generates or owns — Xcode project files, lockfiles, generated schemas or migrations, IDE workspace files. Do not load for ordinary source code.
Load when entering an unfamiliar codebase, or before proposing an architecture-level change. Do not load for tiny edits, known local fixes, post-implementation summaries, or tasks already scoped by a current state-map.md.
Load on strike 3, a tangled run, or a contradiction that cannot be localized. Do not load for first failures, ordinary test red/green loops, or known environment outages.
Load for cross-session orchestration — dispatching work to an Albion/GLM worker over tmux, polling a worker completion manifest, or reviewing worker output. Do not load for in-session subagent delegation; use delegation instead.
Load when writing a subagent brief for non-trivial dispatched work. Do not load for direct edits, trivial lookups, user-facing summaries, or delegation already covered by an existing brief.