The experience graph

The Experience tab describes the product you're building — not as a document, but as a graph of entities that each carry a reason for existing. Where the research graph holds what you know, the experience graph holds what you've decided to ship, and the two stay linked.

Entity kinds

Create any of these from the Create menu in Experience.

Short IDs and the why

Every entity gets a stable short ID like ex-158204. That ID follows the entity everywhere — into code via crux-attr attributes, into live-site links, and into Ask citations. Alongside the ID, each entity carries a description of why it exists and evidence links back to the research that justifies it. Ask "why does this page exist?" and Crux can answer with citations.

Relations and iterations

Entities relate to each other: a page contains features and content; a menu navigates to pages. Link any other existing item on the graph when you need to explain why it belongs there. These relations are what make it a graph rather than a list. Entities also keep per-sub-project iterations, so a page can evolve differently across the sub projects in your workspace.

Both the entity and its links are versioned, and any version can carry a change note — so an evidence link that was added or dropped has a reason attached to it, not just a timestamp.

Filtering

Filter the experience list by source, build status, sub-project, activity, and labels. Build status shows whether an entity's code is Synced, Stale, or Not synced — see Experience scan & code sync. The activity filter narrows the list to the entities grouped under a given Activity, so you can see what one workshop or audit actually changed.

Next

• Pages & structure
• Menus & sitemaps
• The research graph