-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Status: Complete · The fastest answers to the questions everyone asks first. Each links to the deep dive — and stays honest about what SAE is and isn't.
This page is the quick-reference. For the full treatment of the hard objections, see Objections; for the limits, see When Not to Use SAE.
No — it's the disciplined opposite. Vibe coding prompts, accepts, and ships on feel. SAE makes the spec the source of truth, measures preparation difficulty as Context Entropy, and never lets the writer judge its own work — a fresh-context Guardian tries to refute the output. SAE competes on discipline and measurement, not speed. See Objections.
A team can — and most should start there. Adopt the practices — Spec-Driven Development, vertical slices, AI hygiene, adversarial verification — without literally collapsing to one person. The N=1 Architect-Engineer collapse is the radical end of the spectrum, not the price of entry. The honest headline is collapse the handoff, not the headcount.
No. It means absorb their function into the operator + Guardian loop and remove the handoff latency — not the concern. The 12 layers are queues to strip while keeping every ounce of diligence. QA and security stay non-negotiable; see Risks, Security, and Governance.
No — it's shorthand, and a sloppy one. Single-shot vertical slicing removes the cross-team integration seam that integration testing used to police. You still test the slice's behaviour — edge cases, concurrency, auth, external failures. The Reality Check in Module 2 says this plainly.
Reality check. "Bypass testing" is the single most misread line in the framework. Read it as "the handoff that testing policed is gone," never "verification is optional."
Be careful. In health, finance, aviation, and government, layers like architect review and change sign-off are legally mandated — not optional friction. Keep the mandated gates; apply SAE inside them to remove latency, never the controls. See When Not to Use SAE.
Yes — it's the framework's main structural cost, and SAE concedes it openly. The mitigation is Spec-Driven Development: if the specs/ folder is authoritative and current, the project is legible to anyone who reads it. The spec is the succession plan. More in Objections.
It's a real trade-off. Favour tools with standard exit formats — plain Postgres, portable components — so Zero-Ops doesn't become zero-leverage. The vetting criteria live in the Approved Zero-Ops Tooling List and Module 4.
A stale spec. The moment code and spec disagree and the code wins silently, you've lost your source of truth and the whole thing degrades into ad-hoc AI coding. That's why SAE instruments measured spec drift — the discipline is catching divergence, not just writing a spec once. See Best Practices.
Less than you think. A capable coding agent, a clean repo organized for AI hygiene, and a Zero-Ops stack (managed Postgres, managed hosting). The Getting Started and Agent Setup and Configuration pages walk the minimal setup.
SAFe and Agile coordinate many humans — they optimize the O(N²) communication problem with ceremonies, roles, and cadences. SAE collapses the coordination problem to O(1) by removing the handoff, then reinvests the freed energy into clarity and verification. They solve opposite halves of the cost equation. The lineage and what SAE inherits vs. rejects is in Evolution and Positioning.
Bottom line. SAE is honest by construction — every bold claim ships paired with a Reality Check. The boldest lines are targets, not literal instructions. Use the parts that fit; keep the gates that exist for good reason.
See also: Objections · When Not to Use SAE · Evolution and Positioning · Risks, Security, and Governance · First Principles · The SAE Manifesto · Framework at a Glance
The Sovereign Architect‑Engineer (SAE) Framework · Maintained by Sanjeev Azad · Repository · MIT License · Contribute
- Module 1: The Sovereign Paradigm Shifts
- Module 2: Core Pillars of SAE Architecture
- Module 3: The Digital Org Chart
- Module 4: The Lean SAE Tech Stack
- Module 5: Project Navigation & Metrics
- The End‑to‑End Lifecycle
- Operator Competency Model
- The Verification Doctrine
- Scenario Playbooks
- Operator Techniques
- Best Practices
- KPIs & Metrics
- The Maturity Model
- The Anti-Pattern Catalog
- Risks, Security & Governance
- Governance, Versioning & Stewardship