Stop rebuilding your trace matrix before every review.
Capture intent. Trace it through the system. Baseline it. Prove it.
The same artifact whether your reviewer is a TÜV inspector or a senior engineer on call.
What you do now
Export from three places. Reconcile IDs that drifted when someone renamed a parent. Chase the four requirements that changed after the last baseline and before the freeze. Hand-build the matrix. Find a gap. Re-verify. Discover that the version the auditor received and the version you reconciled against were cut a week apart.
What you do instead
Query the matrix. It was never built, so it was never stale.
If you live in DOORS, Polarion, or Jama.
Typed links, not free-text references.
Every link carries a type: implements, verifies, derives_from, conflicts_with, and others.
The matrix is derived, never maintained.
Graph, matrix and tree read the same relationship table, so there is no second copy to reconcile.
A keyboard path through every view.
The requirements list is virtualized and driven by j, k, x and f. The traceability tree is a keyboard tree view over the graph's data.
Baselines and baseline diffs are not yet open to self-serve workspaces.
If you are escaping spreadsheets and Jira-as-spec.
Treat specs like code. Every requirement has an ID, a type and typed links, and the list is driven from the keyboard. An MCP server exposes the same requirements to agents; tokens for connecting your own agent are not yet issued.
> search_requirements {
query: "engine-out", status_filter: "active" }
{
"success": true,
"count": 1,
"query": "engine-out",
"data": [
{
"title": "Engine-out emergency descent profile",
…
}
]
}The product, on screen.
Two surfaces from the running client, captured by a deterministic script with fixture data standing in for a live workspace.
REQUIREMENTS / VIRTUALIZED, KEYBOARD-NATIVE.
The highest-density product surface. Virtualized, filterable, navigable end-to-end without leaving the keyboard.
TRACEABILITY / MATRIX VIEW, TYPED RELATIONSHIPS.
The signature surface. Every cell carries a mono relationship code, the V-model is legible at a glance, and graph and tree views are siblings on the same data.
Compliance posture.
Traceo is built for teams whose requirements will be audited. Every requirement link is typed, and every link type is encoded three ways — color, glyph, and label — so meaning never rests on color alone.
The state palette is checked in CI against WCAG 2.2 AA contrast. The traceability graph has a keyboard tree view over the same data, so the canvas is not the only road through it.
No third-party analytics or tracking scripts in the product application.
- Typed links
- Graph · matrix · tree
- MCP-native