Standing on the shoulders
of software giants.
OpenLogos isn't invented from scratch. It's built on 40+ years of battle-tested software engineering theory — carefully recompiled for an era where AI writes the code.
Six pillars, one methodology
Each OpenLogos principle maps to established engineering theory. Nothing is arbitrary.
Behavior-Driven Development
GIVEN/WHEN/THEN acceptance criteria. User-facing scenarios as the source of truth.
Test-Driven Development
Tests before code. Red → Green → Refactor. The test defines the contract.
openlogos verify Domain-Driven Design
Ubiquitous language. Bounded contexts. Domain model drives architecture.
Stage-Gate Process
Quality gates between phases. Each gate has pass/fail criteria before proceeding.
Documentation as Code
Version-controlled docs. Treat documentation with the same rigor as source code.
logos/ directory Executable Methodology
Methodology encoded as Markdown files that AI agents read and execute automatically.
SKILL.md), AGENTS.md Theory is not overhead — it's leverage
Predictability
These practices have been validated across millions of projects over decades. When you apply them to AI-assisted development, you get predictable results — not random walks.
Composability
BDD + TDD + DDD + Stage-Gate compose naturally. BDD defines the scenarios, TDD verifies them, DDD models them, Stage-Gate ensures quality between phases. OpenLogos wires them together.
Teachability
AI agents can learn from established patterns far more effectively than ad-hoc instructions. When you say "use GIVEN/WHEN/THEN," AI understands the pattern because it appears in millions of training samples.
Addressing the skeptics
"Isn't this just waterfall?"
No. Waterfall sequences all requirements before any design before any code. OpenLogos sequences per scenario. S01 can be in Phase 3 while S04 is still in Phase 1. The phases are a progression model, not a schedule.
"AI is supposed to be fast. This adds process."
A 5-minute prompt that produces garbage you debug for 3 hours isn't fast. A 30-minute structured process that produces correct, tested, traceable code in one shot is fast. Speed is measured in shipped features, not generated tokens.
"This is overengineering for small projects."
OpenLogos scales down gracefully. A solo project might skip the HTML prototype phase. A weekend hack might compress Phase 1 + 2 into one doc. The methodology is a toolkit — use what you need.
"Why not just use Agile?"
Agile assumes human developers who can hold context in their heads. AI doesn't have a head — it needs context written down. OpenLogos is Agile-compatible but context-explicit, because that's what AI requires.
Ready to try it yourself?
Two commands. Five minutes. A project built the right way from day one.