[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74JGMME0MXWE2FSHTYWF6BD":3,"skill-same:01M74JGMME0MXWE2FSHTYWF6BD":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M74JGMME0MXWE2FSHTYWF6BD","halt-as-deliverable",null,"When a pre-registration, pre-flight or sanity gate refuses to produce your deliverable, the catch is often worth more than the deliverable. Use when a discipline you built caught your own work.","MrBinnacle\u002Fskills","MrBinnacle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F124333270?v=4","01M74JFP3ZCYZP94CVBY1JR1E6","Matthew Gruber","01M74JFP4K4A75MGTZBC9D836G",1,"MIT","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fhalt-as-deliverable\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: halt-as-deliverable\ndescription: When a pre-registration, pre-flight or sanity gate refuses to produce your deliverable, the catch is often worth more than the deliverable. Use when a discipline you built caught your own work.\n---\n\n# HALT as Deliverable\n\n## Problem\n\nA quality discipline (pre-registration, pre-flight check, sanity gate) refuses\nto produce the intended result because it detected an inconsistency in the\nsurrounding state. The engineer reflex is to fix the inconsistency and re-run,\ntreating the HALT as a setback — which discards the most valuable artifact the\nwork produced. A discipline-gate catching its own author's accidental\nfalsification, before any contaminated result ships, is an uncopyable\ncredibility signal: it proves the discipline works on real, unrehearsed\nmaterial. Where the framework's credibility matters more than the specific\nresult, the HALT is the higher-value deliverable.\n\n## Use when\n\n- A pre-registered prediction is falsified by a known class of error before\n  the experiment executes: registry drift, version mismatch, schema change,\n  baseline\u002Ftag documentation inconsistency.\n- A pre-flight verification refuses the run because operational state is\n  inconsistent with the experiment's preconditions.\n- A self-audit, linter or regression check catches a defect in the author's\n  own shipped work — the defect the audit existed to demonstrate the absence\n  of.\n- Any \"the discipline refused to produce X, and here is why\" outcome where the\n  why is structurally informative rather than transient infrastructure noise.\n\nDeciding between the two paths:\n\n| Apply HALT-as-deliverable | Apply fix-and-re-run |\n|---|---|\n| The HALT reveals a structural inconsistency the audience would care about | The HALT reveals transient infrastructure (rate limit, flaky network) |\n| The discipline's credibility is itself the claim at stake | The experiment's specific result is the claim at stake |\n| The catching is uncopyable \u002F hard to fake | The catching is generic \u002F commodity |\n| The audience is field-skeptical (impressed by the discipline) | The audience is result-focused (would not engage with meta) |\n| The author's own work was caught | Someone else's work was caught |\n\n## Solution\n\nThe worked record behind every step is in [`case-study.md`](case-study.md).\n\n### 1. Commit the audit trail publicly before deciding the path forward\n\nThe HALT findings, the failed pre-registration, the pre-flight log — commit\nthem to public history immediately, before deciding whether to re-run. This\nlocks the catching in place; it cannot be retroactively papered over.\n\n### 2. Make the catching the headline, not a quiet fix\n\nThe reflex — fix, re-run, ship the corrected number, mention the re-baseline\nin passing — is correct for routine engineering and WRONG when the\ndiscipline-catching IS the demonstration. Name the HALT in the title, document\nthe audit trail explicitly, narrate the discipline-catching-itself moment as\nthe lead. The corrected result is a number; the HALT is a story, and a story\nis a character claim about the work. In fields where the dominant pattern is\n\"produce a confident number even when you shouldn't,\" publicly halting before\nfabricating is itself the artifact — loudness is substance here, not\nmarketing.\n\n### 3. Reframe the deliverable around the catching\n\nIf the original deliverable was \"experiment produces result X showing claim\nY,\" the reframed deliverable is: \"the discipline pre-registered claim Y,\nattempted the experiment, refused to proceed because Z was inconsistent, and\nhere is the audit trail.\" Same evidence, sharper story — the catching of Z is\nthe demonstration of claim Y.\n\n### 4. More than one HALT compounds\n\nA series of HALTs catching different classes of inconsistency (documentation\ndrift, operational state, environment configuration) is dramatically more\ncredible than one HALT plus more than one silent fix. The compounded trail\ntriangulates what doing this honestly looks like.\n\n## Verification\n\nThe reframe is correctly applied when:\n\n1. The audit trail was committed to public history BEFORE the reframe. Order\n   matters; backdating breaks audit integrity.\n2. The headline names the HALT explicitly — \"we caught X\" is the lead.\n3. A reader who came for the original deliverable would accept the substitute\n   on its merits, not because they were told to.\n4. The discipline is recoverable from the trail: someone implementing it would\n   have caught the same class of error.\n\nThe reframe FAILS when the HALT reads as marketing spin; when the original\nclaim was specific (a number, a comparison) and the substitute is vague — the\nreframe does not work for narrow factual claims; or when the audience\nexplicitly came for the result, where meta reads as evasion.\n\n## Notes\n\nOpen [gotchas.md](gotchas.md) when a pre-flight gate refuses to produce your deliverable and you are about to treat the HALT as a setback. It records the origin incidents and a second, independent occurrence.\n\n- The pattern requires the discipline to be REAL — falsifiable, recoverable\n  from the audit trail, applied uniformly, catching real problems including the\n  author's own mistakes. Decorative pre-registrations produce HALTs that do\n  not generalize.\n- Identity match amplifies it: \"the framework I built refused to validate my\n  own shipped work\" is uncopyable; \"the framework caught someone else's work\"\n  is much weaker.\n- The whole pattern collapses if the framing is perceived as motivated\n  reasoning. Mitigations: commit the trail first, make every input to the\n  catching publicly verifiable, and report HALTs unselectively.\n","# HALT as Deliverable\n\n## Problem\n\nA quality discipline (pre-registration, pre-flight check, sanity gate) refuses\nto produce the intended result because it detected an inconsistency in the\nsurrounding state. The engineer reflex is to fix the inconsistency and re-run,\ntreating the HALT as a setback — which discards the most valuable artifact the\nwork produced. A discipline-gate catching its own author's accidental\nfalsification, before any contaminated result ships, is an uncopyable\ncredibility signal: it proves the discipline works on real, unrehearsed\nmaterial. Where the framework's credibility matters more than the specific\nresult, the HALT is the higher-value deliverable.\n\n## Use when\n\n- A pre-registered prediction is falsified by a known class of error before\n  the experiment executes: registry drift, version mismatch, schema change,\n  baseline\u002Ftag documentation inconsistency.\n- A pre-flight verification refuses the run because operational state is\n  inconsistent with the experiment's preconditions.\n- A self-audit, linter or regression check catches a defect in the author's\n  own shipped work — the defect the audit existed to demonstrate the absence\n  of.\n- Any \"the discipline refused to produce X, and here is why\" outcome where the\n  why is structurally informative rather than transient infrastructure noise.\n\nDeciding between the two paths:\n\n| Apply HALT-as-deliverable | Apply fix-and-re-run |\n|---|---|\n| The HALT reveals a structural inconsistency the audience would care about | The HALT reveals transient infrastructure (rate limit, flaky network) |\n| The discipline's credibility is itself the claim at stake | The experiment's specific result is the claim at stake |\n| The catching is uncopyable \u002F hard to fake | The catching is generic \u002F commodity |\n| The audience is field-skeptical (impressed by the discipline) | The audience is result-focused (would not engage with meta) |\n| The author's own work was caught | Someone else's work was caught |\n\n## Solution\n\nThe worked record behind every step is in [`case-study.md`](case-study.md).\n\n### 1. Commit the audit trail publicly before deciding the path forward\n\nThe HALT findings, the failed pre-registration, the pre-flight log — commit\nthem to public history immediately, before deciding whether to re-run. This\nlocks the catching in place; it cannot be retroactively papered over.\n\n### 2. Make the catching the headline, not a quiet fix\n\nThe reflex — fix, re-run, ship the corrected number, mention the re-baseline\nin passing — is correct for routine engineering and WRONG when the\ndiscipline-catching IS the demonstration. Name the HALT in the title, document\nthe audit trail explicitly, narrate the discipline-catching-itself moment as\nthe lead. The corrected result is a number; the HALT is a story, and a story\nis a character claim about the work. In fields where the dominant pattern is\n\"produce a confident number even when you shouldn't,\" publicly halting before\nfabricating is itself the artifact — loudness is substance here, not\nmarketing.\n\n### 3. Reframe the deliverable around the catching\n\nIf the original deliverable was \"experiment produces result X showing claim\nY,\" the reframed deliverable is: \"the discipline pre-registered claim Y,\nattempted the experiment, refused to proceed because Z was inconsistent, and\nhere is the audit trail.\" Same evidence, sharper story — the catching of Z is\nthe demonstration of claim Y.\n\n### 4. More than one HALT compounds\n\nA series of HALTs catching different classes of inconsistency (documentation\ndrift, operational state, environment configuration) is dramatically more\ncredible than one HALT plus more than one silent fix. The compounded trail\ntriangulates what doing this honestly looks like.\n\n## Verification\n\nThe reframe is correctly applied when:\n\n1. The audit trail was committed to public history BEFORE the reframe. Order\n   matters; backdating breaks audit integrity.\n2. The headline names the HALT explicitly — \"we caught X\" is the lead.\n3. A reader who came for the original deliverable would accept the substitute\n   on its merits, not because they were told to.\n4. The discipline is recoverable from the trail: someone implementing it would\n   have caught the same class of error.\n\nThe reframe FAILS when the HALT reads as marketing spin; when the original\nclaim was specific (a number, a comparison) and the substitute is vague — the\nreframe does not work for narrow factual claims; or when the audience\nexplicitly came for the result, where meta reads as evasion.\n\n## Notes\n\nOpen [gotchas.md](gotchas.md) when a pre-flight gate refuses to produce your deliverable and you are about to treat the HALT as a setback. It records the origin incidents and a second, independent occurrence.\n\n- The pattern requires the discipline to be REAL — falsifiable, recoverable\n  from the audit trail, applied uniformly, catching real problems including the\n  author's own mistakes. Decorative pre-registrations produce HALTs that do\n  not generalize.\n- Identity match amplifies it: \"the framework I built refused to validate my\n  own shipped work\" is uncopyable; \"the framework caught someone else's work\"\n  is much weaker.\n- The whole pattern collapses if the framing is perceived as motivated\n  reasoning. Mitigations: commit the trail first, make every input to the\n  catching publicly verifiable, and report HALTs unselectively.\n",{"name":5,"description":7},"main","fb8ab02da6c849e2cdb704371f5c8c190512d15e","skills\u002Fengineering\u002Fhalt-as-deliverable","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills","https:\u002F\u002Fmrbinnacle.github.io\u002Fskills\u002F","https:\u002F\u002Fgithub.com\u002FMrBinnacle","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmatthew-g-83390523","I make AI coding agents work in messy, real environments, and measure whether they did. Ex-Army NCO, ex-J.P. Morgan.","2026-11-15 04:37:29",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add MrBinnacle\u002Fskills --skill halt-as-deliverable",{"tool":39,"command":40},"bunx","bunx skills add MrBinnacle\u002Fskills --skill halt-as-deliverable",{"tool":42,"command":43},"pnpm","pnpm dlx skills add MrBinnacle\u002Fskills --skill halt-as-deliverable","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fhalt-as-deliverable\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"case-study.md","REFERENCE","参考文档",3836,"https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fhalt-as-deliverable\u002Fcase-study.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"evals\u002Fevals.json",3342,"https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fhalt-as-deliverable\u002Fevals\u002Fevals.json",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"EVIDENCE.md",5374,"https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fhalt-as-deliverable\u002FEVIDENCE.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"gotchas.md",1350,"https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fhalt-as-deliverable\u002Fgotchas.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74JHKQKA5V9N4B4VDAHBGAP","subagent-handback","Use when prompting, briefing or dispatching a research subagent, or when one goes idle with no report. Name a return channel, check its tool grant, verify every claim, negatives first.","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Forchestration\u002Fsubagent-handback\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74JHGXP4YFAGQCRTMFQ8Q5F","disposition-schema","Use when dispatching parallel agents to verify or adjudicate findings (adversarial verify, security disposition, council fires), or before you consolidate their outputs and risk an ID collision.","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Forchestration\u002Fdisposition-schema\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74JHDMFE7VN27QTC6YRPW22","decision-rights","Use when writing a handoff, plan, ADR or subagent brief, or one says \"do not re-litigate\" or \"final\". Separates evidence access from decision rights and marks what is non-negotiable.","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Forchestration\u002Fdecision-rights\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M74JHARZJ246DYV6SSXFRNXT","dead-predicate","Use when a hook didn't fire, a reminder never arrived, or before claiming a rule is hook-enforced: a live router rule can match nothing (missing word, JSON escape, shadowing, stale name).","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmeta\u002Fdead-predicate\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M74JH7P66AGN3RHKH7DVA5Y4","vacuous-check","Fail-open success checks. Use when a script says OK but nothing happened, a probe batch returns a false negative or 0 results, or `String(got) === String(want)` passes on a type mismatch.","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fvacuous-check\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M74JH59H7FJZW0VR6EXMHQJ5","stale-deploy","Use when asking \"is it live\", a deploy looks stale, or a poll loop exits instantly. Verify a GitHub Pages or CDN deploy serves new content: poll a marker new to this deploy.","https:\u002F\u002Fgithub.com\u002FMrBinnacle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fstale-deploy\u002FSKILL.md",[],[]]