We compress equipment-reliability knowledge (failure modes · standard basis · historical accidents · field tasks) into artifacts a field engineer can use standing in front of the unit — and explain, from first principles, the closed loop that connects them. Static, offline-ready, mobile-friendly, bilingual.
The root question of reliability is one sentence: equipment fails. It branches into three questions that must be answered—why does it fail (mechanism)? what happened when it did (evidence)? what do we do so it won't (action)?
These map to three irreducible knowledge primitives, and to three tenses of knowledge:
The field task that prevents or mitigates the mechanism — inspection, monitoring, maintenance. The future / preventive tense.
A concrete accident where the mechanism manifested — dated, sourced, verifiable. The past tense.
The failure mode itself — the universal structure of how it fails. Equipment-agnostic. The present / structural tense.
Behind all three is one ontology: equipment → subsystem → component → failure mode. A/B/C are just projections keyed differently:
Failure mode (C) sits at the hub; accidents (B) are its real-world instances, field tasks (A) are its preventive interventions, and A in turn prevents B from recurring.
Every card is a verifiable knowledge artifact; click any card to enter the bilingual library.
Bilingual field guidance for all equipment types, usable right in front of the unit.
Enter → Evidence · PastReal accident investigations (CSB / NUREG / China Emergency Mgmt / CCPS) with official source links.
Enter → Mechanism · PresentTraceability chain for failure modes: FM → evidence → accident → standard → derived analysis.
Enter →One representative card for each knowledge lens (action / evidence / mechanism); open to see that module's real artifact.
Bilingual field guidance usable right at the unit: a risk board; each FM paired with mechanism / detection / remedy / standard / accident.
Real accident investigation: lube-oil piping fatigue fracture caused a reactor trip; NRC source link and structured root cause.
Above is the static relationship; below, a real K-101 case connects A / B / C in the actual flow — note the node numbers ARE the traversal order ①B → ②C → ③A.
Traverse clockwise: Accident(B) → Mechanism(C) → Action(A) → (intervention prevents) Accident(B). Each node is clickable, linking to its card.
This is the loop 'learn from accidents → distill mechanism → convert to action → block recurrence' — and the essence of the A/B/C relationship: not three parallel pipelines, but one self-reinforcing learning cycle.
Every card is a verifiable knowledge artifact, not marketing talk.
Pure static single file, zero CDN, zero web-font links; opens with no network, works on-site with no signal.
Touch targets ≥44px, large fonts, pure-CSS paging; opens instantly in WeChat / WeCom.
Each device has Chinese / English versions; standard IDs and accident report numbers keep international codes for export.
Standard basis down to clause; historical accidents carry official source links (CSB / NRC) for one-click verification.
标准覆盖 100.0% · 事故挂载 59.4% · 含诚实缺口标注