status
View the status command →
activeFeatures entries always contain id, behavior, and owner; they contain title only when the feature defines one. readyFeatures and blockedFeatures summaries additionally contain dependencies and sourceRefs. This helps an Agent choose the next step without traversing the entire JSON itself.
traceability
View the traceability command →
The complete matrix contains parsed requirements, stories, acceptance criteria, features, and verification mappings, plus these diagnostics:
applicable: whether the current repository is in scope for real traceability checks.deferred: whether checks are still deferred because of a scope placeholder.ok: whether the matrix has no gaps.uncoveredRequirements, orphanStories, and orphanFeatures.uncoveredAcceptanceCriteria and unverifiedAcceptanceCriteria.unknownReferences: unknown requirement, story, or acceptance criterion IDs, plus verification references to acceptance criteria that the feature itself does not declare. Path existence is checked separately by validate under [stage-gate].
On a normal read, status does not fail because of governance gaps and provides an observational view. Loading or parsing errors can still make it exit nonzero. traceability exits nonzero when it applies and has actual gaps, so it can serve as a CI gate.
When scripts consume these commands, parse the JSON. Do not depend on field order or natural-language nextActions, which primarily guide developers and Agents.
