Intentset
Build the connections before building more workflow.
The first goal is practical: take one real product behavior from readable source to implementation ownership, current evidence, and reviewed knowledge.
Available in this draft
Core and architecture specifications, a TypeScript + Amplify profile, a worked model, an adoption roadmap, and the 0.1 reference toolchain on npm, with a conformance suite other implementations can use.
Delivered in 0.1: validate the model
Safe parsing, typed relationships, stable diagnostics, and independent conformance fixtures.
Delivered in 0.1: connect the repository
Slice ownership and contracts resolved against the code, test evidence collected per snapshot, and the impact of a change explained.
Delivered in 0.1: help people and agents review
A Product Atlas, reviewed Markset publication, and bounded agent context over a read-only MCP server.
Next: a second pilot and a stable 1.0
The first pilot, on Streamlane, changed the specification in four places. A second pilot on a different codebase decides what 1.0 keeps.
Bring a real example
The most useful early feedback is a capability that is difficult to model, a boundary that is hard to enforce, or an explanation that is hard to publish safely.