System

Kids Remote Control Airplane (se-kids-remote-control-airplane) at QC status. Session 495 is an interim QC pass triggered 4 sessions after LAST_QC=491. Project stands at 174 requirements across 6 documents (down from 178 after duplicate deletion), with the {{entity:propulsion subsystem}} and {{entity:radio transmitter}} recently decomposed in sessions 492–494.

Findings

VER duplicate inflation. The previous decompose sessions added a comprehensive batch of VER requirements ({{sub:VER-REQ-040}} through {{sub:VER-REQ-094}}) covering STK, SYS, SUB, and IFC verification procedures. This overlapped with an earlier batch ({{sub:VER-REQ-001}}–{{sub:VER-REQ-039}}), producing 16 pairs where two VER requirements targeted the same source requirement. Of these, 4 pairs were outright duplicates where the older entry was strictly subsumed:

• {{ifc:IFC-REQ-003}} RF compliance: {{sub:VER-REQ-015}} covered documentation review only; {{sub:VER-REQ-059}} adds physical spectrum analyser capture confirming 40-channel FHSS hopping.
• {{ifc:IFC-REQ-014}} connector polarity: {{sub:VER-REQ-065}} duplicated {{sub:VER-REQ-014}} word-for-word in test intent.
• {{ifc:IFC-REQ-021}} power distribution polarity: {{sub:VER-REQ-018}} was a generic inspection; {{sub:VER-REQ-071}} specifies XT30 connector rating, PTC fuse placement, and 30A bench supply confirmation.
• {{ifc:IFC-REQ-022}} AC-DC PSU output: {{sub:VER-REQ-020}} tested only under full charger load; {{sub:VER-REQ-072}} covers no-load and rated-load conditions, providing fuller characterisation.

The remaining 12 pairs are complementary — different test conditions or parameter sets for the same requirement — and were left intact.

ARC orphan root cause. All 7 ARC requirements ({{sub:ARC-REQ-001}}–{{sub:ARC-REQ-007}}) showed as orphaned. Investigation revealed no linkset exists between architecture-decisions and any other document in the standard AIRGen scaffold. Attempting trace creation returned a 400 error. ARC requirements are by convention rationale records, not traceable nodes in the requirements hierarchy.

ESC entity unclassified. Lint flagged the esc concept entity at hex {{hex:00000000}} — an unclassified stub likely created by early session text extraction. This triggered spurious Biological/Biomimetic and Functionally Autonomous lint findings that inflated the high-severity count to 5.

Trace link API inflation. The project reports 2864 trace links but only 179 unique link IDs. The list endpoint returns each link ~16 times. This inflated spray-pattern detection to flag {{sys:SYS-REQ-001}}, {{sys:SYS-REQ-002}}, and {{sys:SYS-REQ-009}} as having 5+ outgoing links when the actual unique count per requirement is normal.

Zero ambiguous SUB/SYS requirements. No occurrences of “appropriate”, “sufficient”, “adequate”, or similar vague qualifiers found in the SUB or SYS document tiers.

Corrections

• Deleted: {{sub:VER-REQ-015}}, {{sub:VER-REQ-065}}, {{sub:VER-REQ-018}}, {{sub:VER-REQ-020}} — tagged duplicate-of-<original> and removed. Trace links from {{ifc:IFC-REQ-003}} and {{ifc:IFC-REQ-014}} re-pointed to the superseding VER entries before deletion.
• Tagged informational: All 7 ARC requirements marked informational + architecture-decision per QC protocol, distinguishing them from traceable requirements in orphan reports.
• Reclassified: esc entity reclassified from {{hex:00000000}} to {{hex:D6F53018}} (Physical Object, Synthetic, Powered, Observable, Intentionally Designed, Outputs Effect, System-integrated), matching the ESC’s role as an active electromechanical controller. This resolves the 3 high-severity ontological mismatch findings for Biological/Biomimetic and removes the spurious Functionally Autonomous finding.

Residual

Twelve VER pairs that verify the same source requirement via different test conditions remain — these are engineering judgements, not duplicates. Lint coverage gaps (STK concepts not flowing down to SYS) reflect terminology variation in the requirement text rather than genuine missing requirements; addressing these would require rewriting STK requirements and re-tracing, which is validation scope. The trace link API inflation issue is a platform behaviour outside QC scope.

Next

Project is ready for SE_VALIDATION. The STK-to-SYS terminology gap (basic manoeuvres, mass constraints, EN 71 labelling) should be confirmed during scenario validation walkthrough. The ARC linkset absence should be raised as a platform improvement — architecture decisions cannot currently participate in the trace matrix.

flowchart TB
  n0["system - Kids Remote Control Airplane"]
  n1["subsystem - Airframe Subsystem"]
  n2["subsystem - Propulsion Subsystem"]
  n3["subsystem - Flight Control Electronics"]
  n4["subsystem - Radio Transmitter"]
  n5["subsystem - Power System"]
  n6["subsystem - Ground Charging System"]
  n7["external - USB Power Supply"]
  n8["external - Atmosphere"]
  n9["external - 2.4 GHz ISM Band"]
  n10["actor - Child Pilot"]
  n0 -->|contains| n1
  n0 -->|contains| n2
  n0 -->|contains| n3
  n0 -->|contains| n4
  n0 -->|contains| n5
  n0 -->|contains| n6
  n5 -->|7.4V power| n2
  n5 -->|5V BEC| n3
  n3 -->|PWM throttle| n2
  n4 -->|2.4GHz control frames| n3
  n3 -->|servo deflection| n1
  n8 -->|aerodynamic forces| n1
  n9 -->|shared spectrum| n4
  n7 -->|5V 2A| n6
  n6 -->|CC/CV charge| n5
  n10 -->|stick inputs| n4