What is a traceable spec?
A traceable spec is a document where every line names its source: the meeting, the date, the excerpt and the timestamp to the second. One click takes you from a UX constraint back to the sentence that produced it, with no searching through a transcript.
The difference is checkable. An ordinary spec states "sign-in must be possible through SSO only". A traceable spec states the same thing, followed by its source.
Weekly product review · 12 August 2026 · 00:14:22 · “if we don’t offer an SSO-only way to sign in, their IT department will block us.”
What are the eight steps?
The pipeline has eight steps, from enriching the sources to the implementation plan. Every arrow between two steps is a real transformation: no step restates the one before it.
| Step | What goes in | What comes out |
|---|
| 01 | Enrichment | Transcripts, DMs, sales feedback | Dated, attributed sources |
| 02 | Extraction | Dated sources | Decisions, constraints, requests |
| 03 | Deduplication | Extracted items | One record per decision |
| 04 | Validation of detected items | Deduplicated items | Relevant items, validated |
| 05 | Feature | Sealed decision | Intent, value, source |
| 06 | UX constraints | Feature | States, edge cases, accessibility |
| 07 | Scope and DoD | Constraints | What is in, what waits |
| 08 | Claude Code plan — gate | Settled scope | Implementation plan |
Where does a person have to step in?
Two of the eight steps require human approval: the validation of detected items (step 04) and the implementation plan (step 08). No document is written into Notion without a seal, and no plan reaches Claude Code without a seal.
Both gates sit where a mistake costs the most: the moment a draft becomes a document the team reads, and the moment a document becomes code. Between them, the AI drafts without deciding anything.
What happens if nobody reviews?
Nothing ships. Drafts stay dashed in the review queue and are deduplicated against later meetings: a decision repeated three weeks running stays one record.
The queue shows how many items are pending and the estimated reading time — in the product-page screenshot, 12 items for about five minutes.
How long does the review take?
A meeting transcript is usually available within five minutes of the meeting ending. A 48-minute meeting starting at 09:12 ends at 10:00, its transcript arrives at 10:04, and the card is ready to read at 10:09.
Whoever reviews reads what was extracted, the quoted excerpt with its timestamp, and the file produced — then approves, edits or dismisses.
The trade sits in one line: five minutes deciding rather than an hour hunting for the information in a transcript.
What are the six document states?
A document moves through six states, each named for what the person controls. Dashed always means the AI; solid always means a human decision.
| State | Meaning |
|---|
| AI draft | Drafted, not yet read. Marked with a dashed border. |
| In review | Someone has opened it. |
| Approved | Sealed by a person, with their name and the time. |
| Synced | Written into Notion. |
| Dismissed | Refused, with the reason and the person. |
| Blocked | A step failed, and says so with the time. |
A blocked item is stamped in solid ink, not in red: the seal is only ever the human decision.
Where are the documents written?
Documents are written into your Notion workspace, where the team already works, and export to Markdown — seals and sources included. The implementation plan is written to a file meant for Claude Code.
The calendar brings the meetings in, Notion receives the sealed documents, Claude Code receives the plan. Nothing else is connected yet.
Connected today: Notion · Slack · Google Meet · Google Calendar · Claude Code
And if a sync fails?
The screen says so with the time and offers to resume. The item moves to Blocked and stays in the queue; no partial write is left in Notion.
“Notion sync interrupted at 09:41. Resume.”