Durability & recovery

Chaos readiness corpus

Describes the failure scenarios a future chaos programme could run, with admission rules that refuse experiments beyond a declared blast radius.

ResearchEngine edition 5f8ea3af

What it does

The chaos crate is a scenario corpus and a run-record library. It describes fault classes such as log corruption, replica loss and sustained health degradation, and refuses experiments that exceed a policy budget. It does not inject faults or run scenarios.

How it works

A scenario has an id, a fault class, a blast radius in nodes and a named remediation. An empty policy admits nothing, a scenario whose blast radius exceeds the policy budget is refused, and a scenario with a blank id, fault class or remediation is a typed refusal at validation. A run record is marked remediated when the caller supplies at least one named check; it does not verify that the check ran or that remediation succeeded.

The crate states that fresh-process replay, production-like cells, steady-state scheduling and incident-grade remediation evidence remain external to it.

Where you reach it

  • Librarykynetra_chaos: Scenario, FaultClass, admission and run records (engine library, not wired to the server)

Limits

  • It does not inject faults or execute scenarios, and it is not wired to the server. The fault-injection that does exist is inside the engine's own tests.

Evidence

  • TestsCovered in the engine repository by 5 tests for admission and validation rules

Test coverage is listed as present in the engine repository at this edition. This page does not report test results.

KynetraDB is in private preview

This is not available in the preview. Request a preview to discuss the current scope.