DESIGN PREVIEW — Canonical sample fixture · schema v1.1 · Back to home
LRS in launch-with-conditions band; P30 above the 4% safety threshold.
Across 3 ranked remediation actions
VCRS 0.22 (MODERATE). Quality controls installed but partially wired.
The system scored 73.1 out of 100 on survivability. It can launch, but three issues must be addressed first.
A small group of people understands this system. Losing one creates real incident risk.
The codebase is navigable, but some areas have high cognitive load.
The system can survive some vendor failures, but not all critical ones.
Probability of a system-level failure in the next 30 days: 18.0%
Failure rate 4.3% per cascade · λeffective = 0.121 · CI95% [3.8%, 4.9%]. The model is structural — calibrates against real incident data after 100 customer assessments.
Script Discovery (SDA)
0.610DEVELOPING
CI enforces linting, type checking, and test coverage before any code reaches production. A breaking change cannot land without being caught first.
Validation Coverage (VCRS)
0.220MODERATE
ESLint is installed but not enforced. It can run on a developer's machine — but it doesn't block a bad commit from reaching production. The tool is there; the protection isn't.
What to do (20 min):
Add 'eslint --max-warnings=0' as a required CI step. This is a single-line change in your workflow file. After that, no commit can bypass the linter.
“System failure” = more than 30% of CCR-weighted nodes fail in a single cascade simulation. At current S_ops and S_fail scores, the 30-day probability is 18.0%.
Failures are well-contained and won't cascade into full outages.
Error isolation and queue-based decoupling mean a single component failure rarely becomes a system-wide incident.
Add integration tests for your circuit breaker paths to ensure they work as designed when the real failure happens.
LRS impact: improving this dimension by 0.10 adds 1.5 LRS points.
A small group of people understands this system. Losing one creates real incident risk.
2–3 people own the critical code paths. The absence of any one of them significantly slows incident response. Knowledge transfer has started but isn't complete.
Run a knowledge-transfer session for the top 5 highest-impact files. Each session should produce a short document: what it does, what can go wrong, and how to debug it.
LRS impact: improving this dimension by 0.10 adds 1.2 LRS points.
Every release is protected by automated quality gates.
CI enforces linting, type checking, and test coverage before any code reaches production. A breaking change cannot land without being caught first.
Add mutation testing (Stryker) to find tests that pass without actually verifying anything. This is the next level of release protection.
LRS impact: improving this dimension by 0.10 adds 1.0 LRS points.
ESLint blocking (--max-warnings=0)
est. 4h · Add `eslint --max-warnings=0` to lint script
Pre-commit hook (lint-staged)
est. 2h · Initialize husky and add a pre-commit hook
ADR presence
est. 45m · Write at least 3 ADR files documenting key architecture decisions
This report is reproducible. Re-run npm run verify:engines against commit 000000000000 to produce identical scores.
Mathematical specification: aura.dev/accuracy · v1.1, May 2026