critical-systems-arch

Goal

Design robust, fault-tolerant architectures for safety-critical systems (e.g., medical, automotive, aerospace) conforming to standards like DO-178C or IEC 62304.

Steps

1. Hazard Analysis: Perform a rigorous failure modes analysis (FMEA) or system-theoretic process analysis (STPA).
2. Fault Tolerance: Design N-modular redundancy, watchdog timers, or explicitly separated safety silos.
3. Safety Case Construction: Document the arguments and evidence for system safety.
4. Verification: Mathematically or logically prove that critical failure states are either unreachable or fail-safe.

Security & Guardrails

1. Skill Security

• Integrity Lock: Prevent the agent from accidentally deleting or overwriting established Safety Cases or Hazard Logs during iterative design.
• Execution Sandboxing: Do not allow the agent to run unverified simulation code when analyzing failure states without formal sandboxing.

2. System Integration Security

• Fail-Safe Enforcement: Every hardware or software boundary interaction must have a defined fail-safe state (e.g., "if brake API fails, default to mechanical brake").
• State Segregation: Strictly enforce memory and process isolation between critical components and non-critical components (e.g., Telemetry vs. Flight Control).