One canvas per project
Requirements, stories, personas, stakeholders, risks and architecture sit on a single live canvas. Select a mark and its edit form opens beside it; the canvas does not move under you.
Graph-native SDLC engineering
Keep every engineering decision connected.
Requirements, stories, risks, architecture and the people they serve, on one canvas — with every relationship recorded rather than remembered.
The assistant proposes; a person always accepts.
What it does
One project, one canvas, every relationship typed.
The artifacts a software project actually produces, held as a connected whole instead of a folder of documents.
Connections have a type
A connection is not a line — it says what the relationship is, and the type decides what may legally connect to what. Each one can carry a description in your own words.
The project states itself first
Six authored questions capture the charter — purpose, objectives, constraints, feasibility — before anyone asks the assistant anything. Every question is skippable.
An assistant that proposes
It reads the project and stages artifacts and connections as proposals drawn on the canvas. Nothing enters the project until you accept it, one at a time or all at once.
How it works
Three moves.
- 01
State it
Answer the inception questions. They write the project charter as real artifacts.
- 02
Build it
Create artifacts and connect them — by hand, or by accepting what the assistant proposes.
- 03
Follow it
Focus shows an artifact and its neighbours; Lineage follows the thread through the project.
Start with one project.
Create it, answer six questions, and the canvas has something to show you.