{"repo":"SihyeonJeon/why-was-fable-banned","free":true,"listed":false,"github":"https://github.com/SihyeonJeon/why-was-fable-banned","clone":"git clone https://github.com/SihyeonJeon/why-was-fable-banned.git","description":"Fable-style spec + evidence gate for Claude Code + Codex. Makes Opus/Codex work under Fable-like discipline: blocks every edit until a deterministic spec passes, and there is no \"done\" without live acceptance evidence. Spec-first, verification-gated, forbidden-paths enforced.","language":"Python","stars":47,"topics":["ai-coding","claude-code","codex","guardrails","hooks","llm","spec-driven-development","agent-harness","claude-fable","claude-fable-5"],"license":"MIT","category":"ai-agents","readme_excerpt":"why-was-fable-banned English · 한국어 Gate for AI coding agents: blocks edits until a spec passes. The agent can't edit code until it writes .wfb/spec.json and a deterministic gate accepts it: restated goal, non-goals, context chosen by authority, ≥2 rejected alternatives with the boundary each breaks, risks, and runnable acceptance. One shared gate, installed as hooks. Works in Claude Code and Codex . Same prompt, same model — gate off vs on. \"Implement a water-current + fish simulation,\" Opus 4.8, identical prompt both runs: Left (naked) stops at thin ripples. Right, the gate makes the model keep working until its own acceptance criteria pass — a volumetric vortex with schooling fish. One anecdote (n=1), not a capability benchmark; measured numbers are below. [!NOTE] A spec must exist and pass before edits land, and unspeced or forbidden-path work never reaches your repo. Every change ships with an auditable decision record. Why \"Fable-style\" Fable-style discipline means spec before code, scoped execution, and verification you can re-run — long-horizon work that doesn't drift. WFB doesn't make the model that disciplined; it externalizes the discipline as a hard gate the model can't skip: - No edit before a passing spec — PreToolUse hook exits 2 until the spec validates. - No \"done\" without live acceptance output — verification is fail-closed. - Forbidden paths are enforced, not suggested. - High-risk work auto-escalates to a heavier gate (typo → LIGHT, auth/migration → HEAVY).","default_branch":null,"files":null,"tree":[],"storefront":"/r/SihyeonJeon","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/SihyeonJeon/why-was-fable-banned/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}