1. Sensors
Presence, linkage, consistency, readiness, policy, and deadline sensors read the case shape.
Diagnostic architecture
Signals → features → thresholds → fault codes → repair.
This is the control system behind the new product. The site now has a public scan flow, but the engine itself is what matters: deterministic sensors, threshold logic, localization, freeze frame, and reviewer simulation.
2. Thresholds
Hard triggers and composite triggers decide when a fault should fire.
3. Localization
Every fault must identify a module, submodule, object, and missing link.
4. Freeze frame
The engine stores the values and missing items that existed when the fault fired.
5. Repair routing
The fault report routes directly to the repair protocol and pack.
6. Reviewer simulation
Before sealing, the system checks whether the file will likely survive outside review.
Stage map
What is now in place.
Stage
What is live now
What it unlocks
Stage 1
Fault taxonomy · module map · sensor registry · threshold table · fault report
Formal diagnostic language
Stage 2
Scan flow · repair routing · reviewer simulation · homepage IA shift
Decision-led entry instead of pack-led entry
Stage 3
Woo integration direction · documented case proof · metrics snapshot
Wedge proof and merchant path
Stage 4
API / SDK · white-label layer · partner integrations
Adoption-ready layer
Stage 5
Conformance suite · profiles/registry · platform adoption path
Standardization route