Decisions & History
Every ruling and sprint. The searchable record of why we decided what we decided.
The decision log. When someone asks “why did we do it that way,” the answer is here. Each ruling is a real, ratified call.
Recent rulings
| Date | Decision | Verdict in one line |
|---|---|---|
| 7/12 | Five-Layer Brand Visibility | YES to “a new invisible layer.” Truth → Proof → Recommendation → Action, productized in 8 steps. |
| 7/12 | DH Consolidation + Domain Law | Only designhacker.com publishes indexable content. Subfolders compound, subdomains never rank. |
| 7/12 | Agentic X-ray ROI Engine | The X-ray report becomes a productized ROI engine for any brand. |
| 7/12 | BBE Vertical Playbook | 10-slot template. One engine, swap skin/anchor/proof, the machine never changes. |
| 7/12 | Web Optimization + Agentic Readiness | robots.txt block is the launch-day gate. JSON-LD, forms, llms.txt all need wiring from canon. |
| 7/11 | Paid Expert Brain | One brain, two doors. Chat now, MCP next. First Engine piece, TP-20. |
| 7/11 | Bridge Funnel (Strategy + Build) | Split page, StoryBrand left, concierge right. Email gate at the aha moment. |
| 7/11 | Referral & Affiliate Engine | Waits for the bridge funnel and journey map. Warm super-partner scouting starts now. |
| 7/11 | Audience & Cockpit | D1 machine truth, Attio human lens, Stripe money. One write door, nightly sync. |
| 7/11 | Cost Exposure & Guardrails | Run cheap by default. Spend caps, model defaults, degrade-to-budget at cap. |
| 7/11 | Productize & Scale (Ruling B) | Launch BBB as a $997 DIY product on Podia via a git-URL marketplace; franchise is the Q3/Q4 flag; fund the Learning Loop + audience as the real moat. |
| 7/11 | Image CDN Upload Build Plan | Browser PUTs raw bytes straight to the same-origin Worker, which streams to R2 and writes D1 in one hop. No presigned URLs, no new infra. |
| 7/11 | Frontend Design Workflow | Desk Edit Mode: click-a-section floating knob panel on the real engine preview, writing the same page-recipe JSON as chat commands. Zero foreign runtime, Build-vs-Borrow stays closed. |
| 7/10 | Content Engine Master Doc | 8 content types, voice QA gate, Review is the ceiling. Never auto-publish. |
| 7/1 | Blog Platform Verdict | The DH engine wins. Strapi stays parked, demand-gated to editorial-team clients. |
How a ruling gets made
The Fable relay
Research lanes sweep local files, Notion, project docs, and the live web in parallel. Fable judges in one pass and writes the ruling. Andrew reads, flips anything he disagrees with, and it becomes doctrine.
Sprint, then ruling
A sprint brief scopes the question. A prep doc gathers the research floor. The ruling answers it with a delegation block, one line per build step plus its acceptance check.
Where the full docs live
Every ruling has a full doc in the project (Fable-Ruling-* and Fable-Sprint-*). This log is the index. The docs curate into this section.
Session history
The handoffs/ archive holds the session-by-session record. Valuable as history, kept out of the front-line reference so it doesn’t drown the current truth.