Correspondence And Rationale

Correspondence And Rationale

• Requirement-to-component notes: see Requirements-Traceability-Matrix for the full REQ-### -> component linkage.
• Decision rationale: see the ADR Index below.
• Spec-to-CI wiring: repo-standards-review's scanner expects a plain checkout, not a separate wiki repo -- resolved between v0.3.10 and v0.3.13 (commit c3a36ae) by standards-assurance-scan.yml, which clones this wiki at scan time, copies this Architecture Packet to docs/architecture/overview.md and the SRS/RTM to docs/requirements/, then runs the real assurance pipeline against that assembled checkout. That copy is ephemeral (scan-time only, never committed); this wiki remains the one real source of truth.
• Known tradeoffs: standards-review-local binds one specific gate (compliance re-certification) to one physical machine's private credentials and PDF corpus -- deliberately kept off the public upstream's own CI token scope (see docs/architecture/standards-compliance.md's living re-certification policy), at the cost of that check being unavailable on any fork that doesn't set up the same local runner. Evidence-strength caveat: the physical-host and private-PDF-corpus details themselves are operator-attested, not independently re-verified by standards-compliance-recheck.yml/standards-assurance-scan.yml -- those workflows verify the private-runner label dependency and document ambient-credential use, but do not and cannot confirm which specific physical machine or PDF corpus is actually behind the runner that picks up the job.