Location
HARA.md, requirement-allocation table (around lines 48-49).
Finding
Safety goal SG-02 ("detect frame payload corruption using the LIN checksum") is allocated to requirement REQ-LIN-004 in the HARA's traceability table. But REQ-LIN-004 is tagged in code on ProtectID in lin.go, which is the PID-parity computation, not checksum logic — the checksum implementation (CalcChecksum) is tagged with a different, later set of requirement IDs. So SG-02 currently traces to a requirement that has nothing to do with checksum verification, and doesn't trace to any of the requirements that actually implement it. I confirmed at current HEAD that the code-level //fusa:req tags still match this description: REQ-LIN-004 sits on ProtectID, and CalcChecksum carries the separate checksum-related requirement IDs.
Recommendation
Re-point SG-02's requirement allocation in HARA.md to the requirement IDs actually tagged on CalcChecksum, so the traceability matrix reflects the real implementation.
Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.
Location
HARA.md, requirement-allocation table (around lines 48-49).Finding
Safety goal SG-02 ("detect frame payload corruption using the LIN checksum") is allocated to requirement
REQ-LIN-004in the HARA's traceability table. ButREQ-LIN-004is tagged in code onProtectIDinlin.go, which is the PID-parity computation, not checksum logic — the checksum implementation (CalcChecksum) is tagged with a different, later set of requirement IDs. So SG-02 currently traces to a requirement that has nothing to do with checksum verification, and doesn't trace to any of the requirements that actually implement it. I confirmed at current HEAD that the code-level//fusa:reqtags still match this description:REQ-LIN-004sits onProtectID, andCalcChecksumcarries the separate checksum-related requirement IDs.Recommendation
Re-point SG-02's requirement allocation in
HARA.mdto the requirement IDs actually tagged onCalcChecksum, so the traceability matrix reflects the real implementation.Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.