Workflow 00 · Intake
What do you believe the model gets wrong?
Four things, then the platform does the rest — silently. Typing is not committing: nothing exists until you confirm at the bottom.
1 · The hypothesis
The claim, not the task: what fails, and in what situation.
2 · The failure modes you believe are involved
A name and what it means here. The definition is what lets the
platform match your words to a mode in the failure bank instead of guessing from a label —
"cites withdrawn guidance" is stale information if it was superseded and a fabricated
citation if it never existed.
3 · Anything else you know
A prior observation, a customer complaint, a link, a transcript. Optional.
It becomes the narrative every later agent reads.
4 · Do you already have the measurement?
Only if you are sure it is associated. An unsure yes anchors the whole
workflow on the wrong measurement; "not sure" is the cheaper mistake.
Recorded with the idea as the direction for matching. A benchmark the
registry carries is matched on your word; one it does not carry is recorded as a registry
proposal and shown on the idea page.
Look at it, then create it
"Look" checks the draft against every existing idea and infers the domain —
nothing is stored. "Create" makes a page others will see and pairs a Linear ticket.
Other doors: a CSV of ideas, or a Linear ticket
A batch of ideas has its own flow — cohort, confirm, match, estimate, run —
at /batch (
POST /api/ideas/batch), and a ticket filed in
Linear becomes an idea on its own. Both end up as the same record this page creates.