Action-Admissibility Tiering

Problem

A correct diagnosis does not make the recommended intervention admissible. The same right answer can rest on a suspect flow measurement, exceed the delegated authority of the actor proposing it, violate a written procedure, be irreversible in a state where recovery matters, or arrive after the process has crossed a boundary it cannot come back from. A single flat check collapses all of these into one accept or reject verdict and cannot say which concern failed. Worse, when admissibility is folded into a score, a high usefulness rating compensates for a failed authority or evidence check, and an inadmissible action outranks an admissible one. Scoring the diagnosis alone hides the problem entirely, because the unit that hurts the plant is the action, not the answer.

Solution

Make the proposed action, not the diagnosis, the unit that is judged, and evaluate it against a versioned profile of the specific plant or platform rather than against general judgement. Order the checks as hard gates. A first gate gets the record itself into a checkable shape: required fields, identifiers, references that resolve against the declared profile. A second gate asks whether the evidence behind the decision is available, in date, and consistent with the represented state of the process. A third gate asks whether the hazard was recognised and the causal story is strong enough to justify this intervention rather than an escalation. A fourth gate asks whether the action is admissible at all for this actor and this state — permitted action family, delegated authority, procedure conformance, preconditions, reversibility, recovery path, escalation obligation. A fifth gate asks what the action does physically: consequence checks against the safety envelope over a verification horizon that the profile fixes and the proposing system cannot shorten. Only actions that clear every gate enter a ranking of usefulness, and a failed gate yields no aggregate score at all rather than a low one, so an ineligible action never competes with an eligible one. Run the gates deterministically from declared rules and human-authored profile content instead of asking another model to judge them, record the first tier that failed alongside the full set of failed checks, and keep the trace so a reviewer can reconstruct why an action was admitted, blocked, or ranked as it was.

When to use

• A proposed action changes the state of physical equipment, and being wrong costs more than being slow.
• Written procedures, delegated authority levels and safety envelopes already govern the operation and can be encoded per site or per platform.
• The concerns behind a rejection have different owners, and an operator needs to know which one failed rather than only that something did.
• Several candidate interventions compete and a usefulness ranking would otherwise let an inadmissible option win.