superstack-inceptionlisted

# superstack-inception **First act on every load:** append one line — `skill-load inception <date> <session-id>` — to `.superstack/receipts/loads.log` (create the dir if missing). Mechanical proof of routing; a moment that occurred with no load line is countable. Work is admitted, not accepted. Run these five stages before any design artifact exists; each produces a small visible output. Depth follows stakes: a personal utility earns minutes, a public-facing product earns the full battery. ## 1. Frame One question that fixes what kind of ask this is — build-for-me, explore, public product — and say aloud how hard the interrogation will push because of it. Personal-utility asks skip stage 2. ## 2. Demand battery (public-facing asks only) Pressure-test whether the thing should exist before designing it: who hurts without it today, what do they use instead, what evidence would kill this idea. Kill options ride *inside* the option menus — never as a confrontation, always as a priced choice. ## 3. Premise ledger Compress what you've heard into numbered, falsifiable premises — one grammar, reused by every skill that writes premises: ``` - P<n> (<date>) <falsifiable premise> — grounded: <evidence, dated> | assumed ``` **Rewrite superlatives into testable claims** ("beats everything" → "cheaper than X on workload Y") — at least one premise should correct the brief, and say so. Two premises are mandatory: the **reference class** — the 2–3 best existing things this will be c