Files
chanora/docs/governance/traceability-matrix.md
T

6.1 KiB

Chanora Traceability Matrix

Document status: DV meeting baseline candidate
Date: 2026-05-29
Primary upstream documents: docs/sysrs.md, docs/sysdes.md, docs/srs.md, docs/architecture/sad.md, docs/architecture/sdd.md

1. Purpose

This matrix gives DV reviewers a compact trace from system requirements to design allocation, software requirements, SWE.2/SWE.3 design baselines, and verification evidence. The detailed allocation records remain in docs/sysdes.md, docs/srs.md, docs/architecture/sad.md, and docs/architecture/sdd.md.

2. Traceability Rule

Chanora uses this document hierarchy:

SysRS -> SysDes -> SRS -> SAD -> SDD -> Verification

The current repository has SysRS, SysDes, SRS, SAD, and SDD baselines. The SAD and SDD are DV baseline candidates: they provide architecture and detailed-design coverage sufficient for review, while strict historical item numbering and deeper API-by-API detail remain follow-up hardening tasks.

3. Baseline Coverage Summary

Layer Coverage statement Source
SysRS to SysDes SysDes Appendix A provides allocation for every SysRS requirement docs/sysdes.md Appendix A
SysDes to SRS SRS reports 110 / 110 SysDes design items covered, with 95 / 110 software-impacting items represented docs/srs.md section 9
SRS to SAD SAD section 3 allocates SRS groups to software architecture components docs/architecture/sad.md
SAD to SDD SDD section 11 maps SAD components to detailed design modules docs/architecture/sdd.md
SDD to verification Verification plans map SDD modules and SRS acceptance areas to SWE.4/SWE.5/SWE.6/SYS.4 evidence docs/verification/
Release decision Release readiness record maps evidence status to Go/No-Go decision docs/release/release-readiness-go-nogo-record.md
Waivers Waiver register maps known gaps to decision scope and unblock condition docs/release/dv-waiver-register.md

4. Verification Handoff Trace

SysRS / SysDes source SRS coverage Verification plan DV status
SysRS-233 traceability matrix SRS-005, SRS-141 through SRS-143, SRS-180 through SRS-183 Verification master plan and this matrix Passed for DV baseline
SysRS-234 protocol compatibility SRS-045 through SRS-053, SRS-131, SRS-134 SWE.5, SWE.6, SYS.4 Requires compatible-server evidence
SysRS-235 state synchronization verification SRS-054 through SRS-061, SRS-124 SWE.4, SWE.5, SWE.6 Partial; reducer suite and event replay gaps recorded
SysRS-236 audio verification SRS-062 through SRS-083, SRS-125, SRS-135 SWE.4, SWE.5, SWE.6, SYS.4 Partial; platform evidence required
SysRS-237 secure storage verification SRS-090 through SRS-095, SRS-126, SRS-137 SWE.4, SWE.5, SYS.4 Partial; Android DEK waiver and platform audit required
SysRS-238 diagnostic redaction verification SRS-093 through SRS-102, SRS-126 SWE.4, SWE.5, SWE.6 Evidence required before external tester enablement
SysRS-239 release packaging verification SRS-116 through SRS-123, SRS-127, SRS-138 SWE.5, SYS.4, release record Partial; source-build/unsigned limitations recorded
SysRS-240 public wording audit SRS-122, SRS-137 and legal review SYS.4, legal/trademark review Blocked by DEC-012 sign-off
SysDes-102 protocol verification handoff SRS-004, SRS-015, SRS-045 through SRS-052, SRS-097, SRS-100, SRS-123, SRS-128, SRS-131, SRS-134 SWE.5, SWE.6, SYS.4 Requires attached candidate evidence
SysDes-103 state verification handoff SRS-058 through SRS-061, SRS-097, SRS-098, SRS-124, SRS-128 SWE.4, SWE.5 Partial; waiver recorded
SysDes-104 audio verification handoff SRS-062 through SRS-083, SRS-099, SRS-125, SRS-128, SRS-135 SWE.4, SWE.5, SWE.6, SYS.4 Partial; platform evidence required
SysDes-105 security verification handoff SRS-090 through SRS-096, SRS-101, SRS-102, SRS-126, SRS-128, SRS-137 SWE.4, SWE.5, SYS.4 Partial; audits required
SysDes-106 deployment verification handoff SRS-116 through SRS-123, SRS-127, SRS-128, SRS-138 SWE.5, SYS.4, release record Partial; release blockers recorded
SysDes-107 MVP acceptance verification SRS-128 SWE.6 Matrix exists; candidate evidence still required

5. MVP Acceptance Trace

SysRS acceptance range Requirement group SRS anchor Verification anchor
SysRS-241 through SysRS-244 Connection, channel tree, online clients, channel join SRS-019 through SRS-024, SRS-045 through SRS-051, SRS-128 SWE.6 MVP acceptance matrix
SysRS-245 through SysRS-253 Send/receive voice, mute/deaf, PTT, audio processing SRS-062 through SRS-083, SRS-125, SRS-128, SRS-197 through SRS-200 SWE.4/SWE.5 audio evidence and SWE.6 matrix
SysRS-254 Channel text SRS-019, SRS-036 through SRS-038, SRS-170 through SRS-174, SRS-128 SWE.6 matrix
SysRS-255 Bookmarks SRS-084 through SRS-089, SRS-128 SWE.4 storage tests and SWE.6 matrix
SysRS-256 Secure storage SRS-090 through SRS-095, SRS-126, SRS-137 Security audit and SYS.4 platform matrix
SysRS-257 Redacted diagnostics SRS-028, SRS-093 through SRS-102, SRS-126, SRS-128 SWE.6 diagnostics evidence and security review

6. Traceability Limitations for DV

Limitation Impact Control
SAD and SDD are baseline candidates rather than fully item-numbered historical documents Some prior references such as SAD-043 and SDD-109 are not reconstructed as itemized records Treat the new SAD/SDD as DV baselines; add strict item IDs later if the process owner requires ID-level audit
Candidate run IDs are not embedded in the documents Evidence is not yet auditable to a specific build Release-readiness record requires run IDs before release approval
Some implementation status items may have changed after the status report Risk of stale blocker statements Waiver register calls out items that need revalidation

7. DV Conclusion

Traceability is sufficient for DV document review if reviewers accept the SAD/SDD baseline-candidate depth limitation and require candidate run evidence before release approval.