| name | 0.2.2-understand-high_availability |
| description | [0.2.2] system design ensuring uptime above 99.9% through redundancy, failover, and elimination of single_points_of_fa |
understand-high_availability
CALL NUMBER: resilience_and_reliability_engineering_patterns.high_availability
DEFINITION: system design ensuring uptime above 99.9% through redundancy, failover, and elimination of single_points_of_failure
Invoke this skill to understand high_availability down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP/SWI-Prolog consistency gate): every reference below resolves.
THE RELATIVE ROOT (the import cone, by lib)
from resilience_and_reliability_engineering_patterns
- redundancy (d1): duplication of critical components or functions with backup ready to assume work upon primary failure
CONSUMERS (what needs this)
active_active_failover
Projected from the resilience and reliability engineering patterns KB (118 concepts / 34 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.
(leaf — this is an actual skill.)
