How CRUCIBLE validates.
CRUCIBLE is JourdanLabs' research and validation hub. Every product that ships from a JourdanLabs division passes through CRUCIBLE validation before it reaches a customer. This page documents how that validation works.
The validation stack has three layers: VANTAGE as the diagnostic suite, the benchmark program as the public reproducibility layer, and RAVEN as the memory validation layer.
Every validation run produces a methodology arc with per-fix attribution. When a product improves from one version to the next, the improvement is traceable to specific changes. When a product regresses, the regression is documented and visible.
Confidence gating is treated as first-class output. A product that says "I don't know" when it doesn't know is not failing — it is passing the CRUCIBLE standard.
Per-fix attribution
Every CRUCIBLE validation produces a checkpoint arc. Each checkpoint records:
- —The specific code change or fix applied
- —The metric delta attributed to that change
- —The corpus SHA at time of measurement
- —Any regressions introduced (documented openly)
The arc is append-only by convention. Prior checkpoints are never edited or smoothed. An external reviewer can trace every metric point back to a specific change.