Requirements traceability
This page is for the person who owns requirements, compliance, or audit sign-off on a system — not only the person who owns the repository. YarraMate's model already carries requirements, who realizes them, and what evidence backs that claim; export rtm turns that into a document you can hand to an auditor.
What export rtm derives
yarramate export rtm <workspace.yaml> --out <directory>
This writes RTM.md — a readable matrix — plus a versioned yarramate/rtm/v1 JSON bundle for tooling. Every row carries:
- Motivation lineage — which stakeholder or goal the requirement traces back to.
- Realizers — the concepts or relationships that implement it, with their status.
- Evidence verdicts — confirmed, contradicted, or unknown, per realizer.
- Attestation state — who signed off, and whether that sign-off is current.
- A source citation per cell —
path:lineinto the native YAML, not just into the rendered document.
A requirement nothing realizes still gets a row, marked as an explicit gap, instead of silently disappearing from the matrix. Running this against this website's own model derives 10 rows — 5 requirements and 5 constraints — with 5 explicit gaps and 0 descoped: work that's traced to a stakeholder but has no realizer yet, shown rather than dropped.
Keeping sign-off honest
reconcile reports a stale attestation: a sign-off whose attested wording changed in a commit after the sign-off date.
yarramate reconcile <workspace.yaml>
This repository's own model currently reports 4 stale attestations — sign-offs recorded on 2026-08-03 against descriptions that were edited afterward. Outside git, on a shallow clone, or against an untracked file, staleness degrades to a plain note rather than a guess. It does not fail check --strict by design: gating on staleness would reward backdating a sign-off instead of re-attesting it.
Evidence with a claimed value
A constraint can declare an expected observation — not just "this must hold" but "this must measure X." Evidence providers report what they actually observed, and reconcile compares the two and renders both sides when they disagree. This is the first mechanism that catches a contradiction between a rule and reality, rather than only between two references.
What was declined, not just what shipped
A goal or requirement authored status: retired, with its rationale, is the record of what the team deliberately decided not to do. export markdown and export briefs render those under a Non-goals heading instead of leaving them to be quietly deleted from the source. export rtm's summary line counts them separately as Descoped (retired), distinct from open gaps.
Bringing stakeholders into the room
The design interview is authored in native YAML by default, which is fine for engineers and awkward for everyone else who needs to weigh in on a requirement. design --facilitate renders the same interview in plain language for a workshop — the underlying --json envelope is identical either way, so nothing about the model changes based on how it's read.
yarramate design <workspace.yaml> --facilitate
Try it against your own model
yarramate export rtm .yarramate/workspace.yaml --out .yarramate-out/rtm
Full release notes for this arc: v0.15.0.
These adoption guides are maintained by the website team. Read the normative product documentation →