How it fits
One blueprint per feature, read by every session.
With the software framework, every feature gets one file: why it exists, what it promises, and what it won’t do. Your agent reads it before it writes a line, in the app or through eidos instructions in any terminal.
- Specs
- One per feature, grouped by domain: Intent, Open Questions, Acceptance Criteria, Out of Scope. A micro variant keeps small ones small.
- Frames
- The product as a whole: architecture, audience, criteria, and market. Every spec is judged against them.
- Tasks
- The work, on a board. Each task points at its spec, so the spec never fills up with sprint state.