System

{{entity:Remote Weapon Station (RWS)}} at session 8, interim QC pass scoped to issues since session {{sys:SYS-REQ-001}} baseline. Entry counts at start: 168 requirements, 145 trace links, 13 orphan requirements. Exit: 175 requirements, 163 trace links, 0 orphans. The project documents are STK (17), SYS (17), SUB (54), IFC (29), VER (45), ARC (13).

Findings

Orphan ARC requirements — 13/13 (critical). All 13 {{entity:architecture-decisions}} requirements (ARC-REQ-001 through ARC-REQ-013) had zero trace links. No linkset existed between system-requirements and architecture-decisions documents. The decisions were effectively floating rationale with no connection to the system requirements they derived from.

ARC-REQ-007/008 duplicate. ARC-REQ-007 and ARC-REQ-008 contain the same FCS decomposition decision (FCC/TTP/BCM/WCI separation rationale). ARC-007 is the more detailed version with complete alternatives analysis. ARC-008 could not be tagged or deleted via the API (same 404 anomaly affecting VER-REQ-027/028); instead it received a motivates link from {{sys:SYS-REQ-002}} with a note flagging the merge requirement.

Homeless VER-REQ-027/028 — unresolvable this session. These two verification requirements appear in the list with no documentSlug but return 404 on all update/reassign/delete operations. The get endpoint resolves them correctly; the mutation endpoints do not. Likely an index consistency issue in AIRGen. Logged as residual.

Lint: 52 findings (1 HIGH, 51 medium). HIGH finding: {{entity:fire control system}} ({{hex:55F7725D}}) lacks {{trait:Physical Object}} classification but {{sub:SUB-REQ-046}} imposes physical constraints. Medium findings: 8 components classified as {{trait:Physical Medium}} with no material property requirements; 8 components classified as {{trait:System-integrated}} (System-Essential) with no redundancy/failover requirements. Coverage gap findings (SYS concepts not in SUB) noted but scoped to next full QC pass.

Spray patterns — SYS-REQ-008 (9 links), SYS-REQ-013 (10 links after dedup), SYS-REQ-016 (8 links). {{sys:SYS-REQ-013}} had 2 duplicate links (SUB-REQ-034 and SUB-REQ-035 each appeared twice across two linksets). Both duplicates removed. The remaining spray counts are justified: {{sys:SYS-REQ-008}} is a SIL-3 firing interlock requirement that genuinely cascades to SIS hardware design, FCS safe-state behaviour, and PDU power independence; {{sys:SYS-REQ-013}} drives a multi-component data distribution architecture; {{sys:SYS-REQ-016}} is a system-level MTBCF requirement allocated across all subsystems.

Corrections

SYS→ARC linkset created. New motivates linkset from system-requirements to architecture-decisions established, plus a subsystem-requirements to architecture-decisions linkset. All 13 ARC requirements linked with specific engineering rationale on each link.

{{sub:SUB-REQ-050}} created: {{entity:fire control system}} physical LRU packaging to MIL-STD-810H Method 507.6/514.8 (HIGH lint fix). Linked from {{sys:SYS-REQ-016}}.

{{sub:SUB-REQ-051}} created: {{entity:hardware firing interlock relay}} ({{hex:D6F51019}}) contact material specification — gold-alloy bifurcated contacts, 50mΩ limit after 50,000 cycles and 1000h salt-spray per MIL-STD-202 (Functional safety of E/E/PE safety-related systems). Contact degradation is a common-cause failure mode that can defeat the SIL-3 interlock. Linked from {{sys:SYS-REQ-008}}.

{{sub:SUB-REQ-052}} created: {{entity:fire control computer}} ({{hex:51B73219}}) hardware watchdog — 100ms timeout, de-energises WCI firing output on expiry. Linked from {{sys:SYS-REQ-008}}.

{{sub:SUB-REQ-053}} created: {{entity:weapon control interface}} ({{hex:50F57A19}}) fail-safe output stage — de-energises firing solenoid ≤10ms on power loss, comms loss, or driver fault. Linked from {{sys:SYS-REQ-008}}.

{{sub:SUB-REQ-054}} created: {{entity:power distribution unit}} ({{hex:D6C51018}}) SSPC per MIL-STD-704F with per-channel fault isolation within 1ms. Linked from {{sys:SYS-REQ-016}}.

VER-REQ-044/045 created for SUB-052 and SUB-053, with oscilloscope-level test procedures and temperature/voltage range coverage. Both linked as verifies to their respective SUB requirements.

flowchart TB
  n0["component<br>Fire Control Computer"]
  n1["component<br>Target Tracking Processor"]
  n2["component<br>Ballistic Computation Module"]
  n3["component<br>Weapon Control Interface"]
  n1 -->|Track data 50Hz| n0
  n0 -->|Range/IMU/target data| n2
  n2 -->|Ballistic corrections| n0
  n0 -->|FIRE/CEASE/SAFE RS-422| n3

Residual

VER-REQ-027/028 homeless — API mutation failure prevents reassignment. Appears to be an AIRGen index issue on requirements created without document assignment in a prior session.

ARC-REQ-008 duplicate — cannot tag or delete via API; has a trace link from SYS-REQ-002 noting the merge requirement.

Coverage gap findings — 9 SYS concepts not yet decomposed to SUB level (lint findings 66–75). These include stabilised fire control ({{sys:SYS-REQ-001}}), traverse/elevation decomposition ({{sys:SYS-REQ-003}}), and BMS data link decomposition ({{sys:SYS-REQ-013}}). Scoped to next full QC pass.

VER trace link coverage remains at 23% (39/175). Activity coverage is 0% — VER requirements exist but are not linked as activities in the verify framework. This is the primary coverage gap for next session.

Next

VER coverage is the blocking metric: 39/175 requirements have verifies links and none have activities assigned. The next session should run airgen verify run and systematically link the 45 VER requirements to their target SUB/IFC requirements via verifies trace links, then close the activity coverage gap. The five new FCS/SIS safety requirements (SUB-050–054) should also be classified in the Substrate namespace SE:remote-weapon-station-rws to align ontological coverage with the updated requirement set.