Specs are contracts, not vibes.
If your AI agent has to guess what you meant, you've already paid for the misunderstanding twice — once in tokens, once in rework.
§ Manifesto
We're not making documents prettier.
We're replacing the meeting that produced them.
For two decades we've typed specs into tools that didn't care who was reading them. Then the readers became machines — and the specs stayed the same. SpecGraph is the spec layer we wished existed. Six tenets, in order:
Conversation is the natural interface.
Specs come from people. We let people talk. The agent does the typing, the tagging, and the field-by-field bookkeeping.
Every team has a wish. Every wish has a cost.
Compliance, finance, ops, design — everyone shows up with constraints. The job of the spec is to surface them, weigh them, and choose.
Disagreement before code, not after.
Conflicts caught in week one cost a meeting. Conflicts caught in week ten cost a quarter. SpecGraph forces the meeting at week one.
The artefact is the source of truth.
We seal the pack. We sign it. We pipe it. Your agent reads it. Your PRs cite it. Reviewers verify against it. The pack is the wire.
Speed without lineage is a liability.
Going faster only matters if you can prove what you shipped, why, and at whose direction. We optimise for speed and for the audit trail at once.
A spec is a small machine.When it's well-built, the team aligns and the code arrives. When it isn't, the project drifts and the team pays interest. We're building the small machine.