Design
:
CollisionGuardNodeDesign

Attribute Value
id com.example.stig.components.collisionguardnode.design.collisionGuardNodeDesign
name Collision guard node design
description Detects obstacles in the forward travel corridor and publishes an asserted braking request. Two proposed input checks can request braking for detected input faults. Their effectiveness and an independent camera-and-lidar architecture remain open design work.
issues
1 item
GitLab issue #1 — all rules
design element
Collision guard node

SafetyMechanism
:
SafetyMechanism
ASIL C

Attribute Value
id com.example.stig.components.collisionguardnode.design.collisionGuardNodeDesign.inputPlausibility
name Input plausibility check
description Proposed check of image dimensions, encoding, pixel-data consistency, and acquisition timestamps before obstacle evaluation. A detected invalid input requests braking rather than allowing an untrusted image to justify continued motion.
ASIL ASIL C
issues
1 item
GitLab issue #1 — all rules
comment Accepted dimensions and encodings, timestamp age limits, and fault-response timing remain to be specified and validated. This check does not establish that every obstacle is visible or detectable.
identityOwner
Collision guard node design
identityReferenceName inputPlausibility
mitigates
1 item
Missed brake request

SafetyMechanism
:
SafetyMechanism
ASIL C

Attribute Value
id com.example.stig.components.collisionguardnode.design.collisionGuardNodeDesign.frameContinuity
name Frame continuity check
description Proposed comparison with previous frames and acquisition timestamps to detect a nonadvancing or inconsistent image sequence. Detected sequence faults request braking. Repeated pixels alone do not establish a frozen camera, and a positive obstacle detection requests braking without waiting for confirmation in later frames.
ASIL ASIL C
issues
1 item
GitLab issue #1 — all rules
comment Temporal acceptance criteria, frozen-sequence detection limits, and fault-response timing remain to be specified and validated. Comparing one camera with its own history does not provide independent obstacle detection; the camera-and-lidar design gap remains open.
identityOwner
Collision guard node design
identityReferenceName frameContinuity
mitigates
1 item
Missed brake request