Raven Public Research Report
Failure Engineering (Technical)
Why preserved failures improve trust more than hidden pass rates. This technical version exposes the evidence mechanics, replay boundary and test lineage.
What this report shows
Failure preservation
Failed scenarios become permanent engineering evidence instead of being silently optimised away.
Defect closure
Defect closure records root cause, correction and regression status, not just a final PASS.
Regression
Replay and regression prevent a later improvement from erasing a known weakness.
Technical boundary
The technical version preserves source identifiers, test families and limitations without exposing private implementation paths.
Engineers should treat the numbers as internally reproducible counts from local artifacts, not as external validation.
Required customer validation
A customer pilot must provide incident history, topology context, ticket or dispatch evidence, decision timestamps and a mutually accepted ground-truth method.
Raven should prefer UNKNOWN or HUMAN_REVIEW_REQUIRED when those inputs are missing or contradictory.