Intent-System: an operational implementation of IDD
Intent-System is our implementation of Tree-Structured Operational IDD. It runs today. We take a stance against the spec-as-source camp: instead of putting spec at the center, we put intent there. We call it Intent-as-source.
The operational loop
The loop runs on GitHub issues. A slice of the intent tree becomes an issue that already carries the architecture, contracts, and UI patterns it needs — so writing a clear issue, the highest-leverage skill in modern AI-assisted coding, becomes feasible. Implementation runs on context that is already there. Review compares the PR to the intent slice, not to the reviewer's taste. Closeout writes any new decisions back into the tree as canonical intent.
The tree itself doesn't need to be perfect on day one. A continuous Clarification step lets AI surface "what about this?" questions in bulk with recommended answers; humans accept the recommendation where they have no strong opinion and override it where they do. Intent grows incrementally, not in an upfront marathon.
The actual operational flow as it runs today is on the Current Flow page. See it →
Read Intent-System in detail
Seven detail pages, in reading order. Each opens its own page; the same step indicator at the top of every one lets you move between them.
Built on our proposals
Intent-System embodies both proposals — but they don't depend on it. Intent Compass — the Intent Tree supplies the direction for each slice. Git-AI-Flow — the implementation cycle runs naturally on ai-develop.
What Intent-System is not
- Not a code generator. Code is downstream; we don't ship a model.
- Not a replacement for your IDE.
- Not a project management tool, though it can integrate with one.