redundancy-pattern-picker

Recommend validated redundancy patterns from FMEDA and fault tree data.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill redundancy-pattern-picker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redundancy-pattern-picker
Source: https://github.com/robotijn/ctoc/tree/main/skills/safety/redundancy-pattern-picker
Command: npx skills add https://github.com/robotijn/ctoc --skill redundancy-pattern-picker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of selecting incorrect redundancy patterns for safety-critical systems, which wastes engineering budget and creates hidden single points of failure that undermine safety claims.

Core Features & Use Cases

  • Pattern Recommendation: Selects from canonical redundancy patterns (dual-core lockstep, triple modular redundancy, hot/cold standby, N-version programming) based on safety integrity level, FMEDA failure mode data, and fault tree minimal cut sets.
  • Diversity Validation: Explicitly checks for named diversity dimensions to avoid common-cause failures that defeat redundancy claims, per 2024 Analog Devices guidance.
  • Compliance-Ready Output: Generates structured YAML recommendations with rationale, beta factor justification, voter strategy, residual risks, and cost estimates to support IEC 61508, ISO 26262, and equivalent safety certifications.
  • Use Case: For an ASIL D embedded brake controller with a size-one fault tree cut set for transient ADC faults, the Skill recommends dual-core lockstep with independent power rails and produces a certification-ready redundancy specification.

Quick Start

Use the redundancy-pattern-picker skill to analyze your FMEDA and fault tree results for your safety-critical system plan and generate a validated redundancy pattern recommendation with diversity and common-cause assessments.

Frequently Asked Questions about redundancy-pattern-picker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I select a redundancy pattern for an ASIL D safety-critical system?

Validated redundancy patterns like dual-core lockstep or triple modular redundancy are selected by analyzing FMEDA failure mode data and fault tree minimal cut sets against your target safety integrity level, such as ASIL D. This process outputs structured YAML with voter strategy and residual risk assessments.

What is the best way to validate diversity and prevent common-cause failures in functional safety designs?

Preventing common-cause failures in functional safety designs requires checking explicit named diversity dimensions within your redundancy architecture. This validates redundancy claims by generating a common-cause beta factor justification for compliance with standards like IEC 61508.

How do I generate certification-ready documentation for IEC 61508 redundancy architectures?

You generate certification-ready documentation for IEC 61508 redundancy architectures by producing structured YAML output containing pattern rationale, voter strategy, residual risk assessment, and cost estimates derived from your FMEDA and fault tree analysis.

Does triple modular redundancy work for automotive brake controllers with transient ADC faults?

For automotive brake controllers with transient ADC faults and size-one fault tree cut sets, dual-core lockstep with independent power rails is typically recommended over triple modular redundancy to meet ASIL D functional safety requirements efficiently.

When should I use hot standby versus N-version programming in high-availability systems?

Choosing between hot standby and N-version programming in high-availability systems depends on your FMEDA failure modes and safety integrity level. Hot standby addresses hardware degradation, while N-version programming mitigates software design faults for compliance.