ADR-0026: Spill Response is branched, and the branch question is the escalation gate

Status: Accepted Date: 2026-09-02

Decisions

D-54 Spill Response is a set of branches, each an ordered procedure, selected by a condition the SDS itself states

The glossary's singular definition is amended to plural.

D-55 The branch condition is asked before any step, and doubles as D-08's escalation gate

A branch is never auto-selected on the user's behalf.

Context

R-44: Doc B branches its spill procedure on volume — under 200 L versus over — and the large-spill branch carries a restriction the small one does not. The glossary defined Spill Response as "the ordered procedure", singular, following the poster's flat five-step mockup.

D-08 already requires escalation before procedure, with an evacuate-and-call condition for a spill that is "large, enclosed, or you are unsure". The SDS's own branch condition is that same question — written by the supplier, with a real number attached. So the branch prompt is not an extra step bolted onto the flow; it is D-08's gate with a supplier-stated threshold replacing our vague wording.

Rejected options

• Always show the most conservative branch — never under-protects, rejected because it tells someone with a cupful of solvent to evacuate, which trains people to ignore the app.
• Show all branches together — nothing hidden, rejected as the most text at the most urgent moment.
• Keep it flat and document the limitation — rejected: it either drops a branch or merges two the supplier deliberately separated.

This ruling may not be re-decided

If a change contradicts this ADR: stop and raise it. Do not implement over it. Auto-selecting the small-spill branch drops the restriction only the large branch carries — that is R-38's failure mode wearing different clothes.

Coverage

Upstream	Landed in	Evidence	Note
R-44	D-54, D-55	Doc B's 200 L branch is named in Context