Product · Documentation

Where the intent
actually lives.

PRDs, experiments, and roadmap plans in a Notion-shaped editor — but every doc anchors to a delta. Comments anchor to sections. When the delta ships, its doc becomes the record of decision.

trunk.dev/norrland/norrland-shop/main/docs/cart-recs
PRD in review anchored to delta #142 · owner Ada

Cart · empty-state recommendations

Problem
62% of visitors reach /cart with items but bounce before checkout. The empty-cart-adjacent state (small cart) shows no product context — users don't see what they've considered.
Hypothesis
A "You may also like" strip below cart items — powered by recently-viewed — will keep users in the funnel.
Success criteria
+20% CTR on cart-page recommendations; no drop in checkout-start rate.
Scope
  • Empty-adjacent state on /cart
  • Recs API endpoint returning 3 items
  • Analytics event · recs impression + click
The anchor

Every doc knows its delta.

A PRD isn't a floating page. It's the intent of a specific change. Trunk enforces the link — the PRD is the delta's Document phase artifact, gated by PM + Tech Lead.

  • ✓Comments anchor to sections — not to line numbers, not to pixels.
  • ✓Linked signals, components, pages update in place when they change.
  • ✓When the delta ships, the doc becomes the record of decision — versioned.
Anatomy of a doc
delta#142 · Cart empty-state
phase2 · Document
gatePM + Tech Lead
statusin review · 3 comments
Slash · like Notion
/ shows blocks
§Section
•Bullet list
σAttach signal
◇Link primitive
☑Task
Familiar editor

Notion-shaped. Domain-aware.

Same slash-menu you already know. But the blocks are product-native — attach a signal, link a primitive, reference a delta. The doc understands what it's about.

Documentation on its own isn't enough.

A PRD in a wiki is a stranded artifact. In Trunk, it's stitched to signals, primitives, flags, PRs, and the delta lifecycle.