Skip to content

Algorithm Evidence Console

See what STBL learned, how it performs, where it is uncertain, and why runtime prediction stays transparent.

171,000synthetic rows
38fault prototypes
19feature weights
95.51%neural synthetic fault accuracy
99.52%neural synthetic behavior accuracy
77.25%distilled synthetic fault accuracy
94.06%distilled synthetic behavior accuracy
Synthetic-onlyAdvisory-onlyStdlib runtimeGPU required: falsePyTorch required: falseExternal service required: falseDeterministic rules authoritativeHuman review required

How STBL was trained

GPU and Jupyter training used 171,000 synthetic rows offline. Neural weights are not loaded by the live app.

How runtime distillation works

Weighted fault centroids, global feature statistics, and transparent rule boosts produce advisory behavior and fault-family predictions.

Top feature weights

mappingConfidenceMin2.4

Lowest identity-mapping confidence.

temperatureSlopeCPerHour2.4

Rate of thermal change.

doorOpenCount2.3

Door events in the evidence window.

sensorDisagreementC2.2

Difference among sensors in one zone.

calibrationOffsetC2.0

Estimated calibration offset.

Fault coverage

38 project-defined synthetic fault families across 8 evidence categories.

Open coverage JSON

Case predictions

single-sensor-spike

single_sensor_false_spike / medium

Inspect plan
multi-sensor-confirmed-warming

multi_sensor_confirmed_warming / high

Inspect plan
unresolved-mapping-risk

unresolved_mapping_risk / low

Inspect plan

Weaknesses and uncertainty

Top alternatives and inspection routes expose ambiguity instead of hiding it.

Runtime safety boundary

No GPU, PyTorch, notebook, database, or external service is required. Deterministic rules remain authoritative and human review remains required.