DekEn

อัปเดต 2026-09-07

Steady scope-note register (A1–A52)

refuse · blocking · warn · info

A structured register of roughly 50 detectors (A1–A52) watches every steady solve and classifies each finding into one of four tiers — refuse (HTTP error, no numbers at all), blocking (numbers returned but datasheet/export gated), warn, or info — so the caller always knows exactly how much to trust a given result.

เมื่อไรจึงใช้
  • You got a result and want to know whether it's fully trustworthy, trustworthy-with-a-caveat, or not safe to size equipment from.
  • You're deciding whether a builder result can be issued as a datasheet — check has_blocking before anything else.
  • You're extending the solver into new physics and need to know whether the new gap should refuse, block, warn, or just note.
ค่าที่ต้องกรอก
ค่าคำอธิบาย
คำนวณอย่างไร

Each detector is an independent, additive check against the actual solved state (not the user's stated intent) — for example one detector blocks a network-global result when a relief device is present without proper handling, another refuses outright, others warn on wide-boiling mixtures, high-pressure Z-factor deviation, or a gas node flashing non-vapour. Detectors never silently combine — every fired note keeps its own code and message.

ข้อควรระวัง
noteA 'warn' note does NOT gate anything — only 'blocking' (has_blocking=true) disables datasheet/export; don't assume a visible orange banner means the result is unusable, read which tier actually fired.
noteSome known gaps are deliberately NOT built as detectors when they'd be false-positive blockers on the current data surface — a missing detector for a known limitation is a documented choice, not an oversight.
ที่เกี่ยวข้อง