Framework at a Glance

Framework at a Glance

Status: Complete · The entire SAE Framework on one page. Print it, pin it, share it. Every line links to its deep dive.

---

The thesis

The cost of code, infrastructure, and boilerplate has collapsed toward zero. The bottleneck is no longer execution — it is human clarity.

One operator with deep domain insight and sharp architectural vision, orchestrating AI personas, out‑builds a legacy cross‑functional team — by managing digital context, not human headcount.

---

The shift

	Legacy	SAE
Bottleneck	Engineering hours / syntax	Human clarity
Scaling	Add headcount → O(N²) coordination	Collapse to N=1 → O(1)
Unit of work	Story points	Context Entropy
Source of truth	The code	The spec
Speed	Months	Days

→ The 12 Layers of Friction · Module 1

---

The operating loop

0 FRAME → 1 SPEC → 2 PRIME → 3 GENERATE → 4 REVIEW → 5 GUARD → 6 RECONCILE → 7 SHIP
   ↑                                                                            │
   └──────────── spec amendment ← 9 MAINTAIN ← 8 OBSERVE ←──────────────────────┘

Every change re‑enters at Spec — never the code. → The End‑to‑End Lifecycle

---

The four personas (Digital Org Chart)

Persona	Job
Conductor (you)	Architecture, edge cases, structural‑drift review, final calls
Visualizer	Generative UI → semantic components
Engineer	Repo‑aware code generation from the spec
Guardian	Adversarial QA — breaks what the Engineer builds, in a fresh context

→ Module 3 · prompts in Agent Setup

---

The four pillars

1. Architect‑Engineer Collapse — vision + execution in one person
2. Single‑Shot Vertical Slice — schema → API → state → UI in one cycle
3. Spec‑Driven Development — the Markdown spec is the source of truth
4. High‑Context Modular Design — small, isolated, AI‑readable bounded contexts

→ Module 2

---

Context Entropy scale

Rating	Band	Prep	Time
1–3	Low	Minimal — just do it	Minutes
5–8	Medium	Audit/update the spec first	< 1 hour
13	High	Redefine boundaries before touching anything	An afternoon

→ Module 5

---

The Zero‑Ops stack

Cursor + Claude Code · Next.js + v0 + Shadcn · Supabase / Neon · Vercel / Cloudflare If a tool needs a dedicated admin, it's banned. → Module 4 · Tooling List

---

The five non‑negotiables

1. The spec is the source of truth — reconcile code↔spec immediately.
2. The writer never judges its own work — verify in a fresh, adversarial context.
3. Gate the irreversible — auth, payments, deletion, schema drops: human decides, never auto.
4. Isolate bounded contexts — isolation keeps generation precise.
5. You own the output — "the AI wrote it" is not an explanation.

→ Best Practices

---

The four metrics that matter

Cycle time (flow) · Regression escape rate (quality) · Spec drift time (health canary) · Blast‑radius incidents (the line you don't cross). Read flow and quality together. → KPIs & Metrics

---

Before you bet a real product on it

Single point of failure · you can't review what you can't evaluate · "bypass integration testing" is shorthand, not literal · vendor lock‑in · regulated domains keep their gates · the #1 failure mode is a stale spec. → Risks, Security & Governance · When NOT to Use SAE

---

New here? Start with The 12 Layers of Friction, then build via Getting Started.