For a while, building software felt like magic. You typed a sentence and an app appeared. It demo'd great. You showed your friends.
Then you tried to change it. And the magic turned into a black box — code you didn't write, couldn't read, and couldn't fix without breaking two other things. You weren't the author of your product. You were its customer.
Almost working isn't working.
Doric exists for the moment after the demo — the day you actually have to live with what you built. We think that moment deserves better tools than a prompt and a prayer.
The end of the black box
You should be able to see your whole system — every flow, end to end — on a map that tells the truth. You should be able to change anything and know what it touches. You should never lose the reason a decision was made, even six months later, even after the team turns over.
That's not a luxury feature. It's the difference between owning a product and renting one.
You can only be proud of what you really built
Other tools leave you impressed for a moment. We'd rather leave you proud for years. Impressed is something that happened to you. Proud is something you did.
So in Doric, you don't describe an app and hope. You set a mission, real features, a real architecture — and an AI team builds the real thing underneath, in steps you can follow, on a foundation built to last.
You don't prompt an app. You build a product — that will still evolve in five years.
Software that stays yours
Platforms abandon you. Runtimes get sunset, pricing changes, products get acquired and shut down. Your product shouldn't depend on any of that. So Doric is the tooling layer, not the cage: preview here, then deploy to your own cloud and keep going — with or without us.
A city outlasts the people who founded it because it was built to. We think your software should be the same. You lay the foundations, the roads, the structure — and it endures.
The Doric laws
- Closed loops. Every action returns to where it began with a verified result — no fire-and-forget.
- Verified writes. Nothing is claimed that wasn't observed; a write isn't done until it's read back.
- Captured once. One source of truth — no second artifact left to drift.
- No hard delete. Removed things become tombstones that remember why.
- Agents are thinking partners. They brainstorm and push back — never a yes-machine.
- The map is honest about its gaps. It flags what it can't confirm rather than pretending to be right.
- Ship in provable steps. Releases are ordered by dependency and proof, never by the calendar.
See twenty things Doric does to hold these laws in practice — the machinery behind the manifesto.
All roads start with Doric
Not "all roads lead to" — start with. This is an origin, not a destination. Come with an idea. Leave with something you built, understand, and own.
Then keep building. That's the whole point.