Surgical Robot first-pass decomposition closed — baseline DECOMP-2026-03-20
System
The {{entity:Surgical Robot System}} first-pass decomposition reaches closure this session. Thirteen functional subsystems are fully decomposed: {{entity:Motion Control and Scaling Subsystem}}, {{entity:Safety and Interlock Subsystem}}, {{entity:Haptic Feedback Subsystem}}, {{entity:Vision and Imaging Subsystem}}, {{entity:Surgical Instrument System}}, {{entity:Power Management Subsystem}}, {{entity:Energy Delivery System}}, {{entity:Communication and Data Management System}}, {{entity:Surgeon Input Console}}, and four associated sub-systems and assemblies. The project holds 366 requirements across all six standard documents, 332 trace links, and 80 PART_OF facts in namespace {{entity:SE:surgical-robot}}. Status advances from in-progress to first-pass-complete; baseline {{stk:BL-SESURGICALROBOT-027}} (DECOMP-2026-03-20) locks the decomposition state.
Decomposition
The {{entity:Motion Control and Scaling Subsystem}} internal architecture illustrates the signal pipeline adopted across the project: a strict unidirectional data flow from surgeon input through tremor rejection and motion scaling into Cartesian kinematics, joint servoing, and finally CAN-FD commands to the {{entity:Patient-Side Cart}}. The {{entity:Workspace Safety Enforcer}} sits orthogonally to this pipeline, intercepting validated commands and injecting a fault signal to the {{entity:Real-Time Compute Node}} {{hex:50A50208}} rather than to the actuator chain — a deliberate architectural choice to keep the safety path off the high-rate kinematic thread.
flowchart TB
TRF["Tremor Rejection Filter"]
MSM["Motion Scaling Module"]
KE["Kinematics Engine"]
WSE["Workspace Safety Enforcer"]
JSC["Joint Servo Controller"]
RTCN["Real-Time Compute Node"]
SC(["Surgeon Console"])
PSC["Patient-Side Cart"]
TG["Trajectory Generator"]
SC -->|6-DOF vel cmds 1kHz| TRF
TRF -->|filtered vel 1kHz| MSM
KE -->|joint setpoints| WSE
WSE -->|validated cmds| JSC
JSC -->|CAN-FD 5Mbps| PSC
WSE -->|fault signal| RTCN
RTCN -->|heartbeat 200Hz| TRF
MSM -->|scaled velocity 1kHz| TG
TG -->|Cartesian poses 1kHz| KE
Analysis
Lint produced 128 findings: 4 high (ontological mismatches), 18 medium, 106 low. The 4 high findings all flag {{trait:Physical Object}} absent on {{entity:Procedure Data Recorder}} {{hex:50851208}}, {{entity:Power Management Subsystem}} {{hex:54F53018}}, {{entity:Real-Time Compute Node}} {{hex:50A50208}}, and {{entity:Motion Control}} {{hex:40A53A08}}. These entities were classified as pure functional or software-layer constructs; the physical housing constraints in {{sub:SUB-MAIN-086}} and {{sub:SUB-MAIN-102}} are acknowledged and flagged for QC resolution rather than reclassification, since the functional classification is ontologically sound for requirements tracing purposes. Acknowledgments stored in the SE:surgical-robot namespace.
The 18 medium findings split between Regulated-but-no-compliance-requirements ({{entity:Motion Control System}} {{hex:51F73A18}}, {{entity:Power Management Subsystem}}, {{entity:Workspace Safety Enforcer}} {{hex:51B73818}}, {{entity:Motion Scaling Module}} {{hex:50B53B18}}) and concept coverage gaps where SYS-level terms do not appear verbatim in SUB requirements. Manual inspection confirms the concept gaps are phrase-matching artifacts: {{sys:SYS-MAIN-018}} (cryptographic authentication) is covered by {{sub:SUB-MAIN-097}}, {{sub:SUB-MAIN-098}}, and {{sub:SUB-MAIN-099}}; the SYS concept “surgeon’s master manipulator” maps to {{sub:SUB-MAIN-066}} (Surgeon Interface Panel 7-DOF pose transmission). The compliance requirements gap is genuine and remains for the QC session.
Requirements
The single orphaned requirement this session — {{stk:ARC-MAIN-020}} ({{entity:Communication and Data Management System}} dual-redundant fibre architecture) — received two trace links: one from {{sys:SYS-MAIN-002}} (single-point failure detection, driving the fibre redundancy decision) and one from {{sys:SYS-MAIN-015}} (1kHz kinematic recording, driving the DMA shared-memory design for the {{entity:Procedure Data Recorder}}). Orphan count now stands at 0/366.
Forty-six requirements carry null documentSlug values (refs REQ-SESURGICALROBOT-001 through REQ-SESURGICALROBOT-049). Thirty-six are verification plans created without --document verification-plan during an earlier session; ten are regulatory requirements missing --document system-requirements or --document subsystem-requirements. These ref-prefix mismatches do not affect content but break the trace linkset topology. QC must reassign them.
Next
QC session: (1) reassign 46 null-doc requirements to their correct documents and sections; (2) resolve duplicate subsystem naming ({{entity:Vision and Imaging System}} vs {{entity:Vision and Imaging Subsystem}}, {{entity:Motion Control System}} vs {{entity:Motion Control and Scaling Subsystem}}); (3) add compliance requirements for Regulated components flagged by lint; (4) verify verification coverage reaches ≥50% of IFC requirements.