Engagement Threshold Table¶
Calibration table — instantiates Conditional Authority Envelope Design
Converts severity or state tiers into a graduated ladder of proportional response, so a mild condition unlocks a light action and a severe one a stronger action.
Engagement Threshold Table turns severity into permitted intensity. Its rows are ordered tiers — of severity, risk, or system state — and against each tier it sets the maximum strength of action an actor is authorized to take. Its defining move is proportionality: as the condition climbs the tiers, the permitted response climbs with it, and no more. Where a permit/prohibit grid answers may I do this kind of thing, the threshold table answers how much am I allowed to do given how bad it is — it is a dial, not a switch. That single idea, response scaled to severity, is what keeps a bounded actor from over-reacting to a minor condition or under-reacting to a serious one, and it is what the table exists to encode.
Example¶
A site-reliability team codifies its incident response into an Engagement Threshold Table. The tiers are severity levels: SEV-5 (cosmetic, one user), SEV-3 (degraded feature, no data risk), SEV-2 (major feature down, revenue impact), SEV-1 (data loss or full outage). Against each, the table sets the permitted intensity of an on-call engineer's own authority. At SEV-5, they may open a ticket and fix in normal hours. At SEV-3, they may push a hotfix without change-review. At SEV-2, they may roll back a release and page a second engineer. At SEV-1, they may fail over to the standby region and take the write path offline. The engineer never has to ask "am I allowed to do something this drastic?" — they read the tier they're in and act to that ceiling, confident the response is proportionate to the severity and pre-authorized for it.
How it works¶
- Order the tiers — define a small, ranked ladder of severity or state, each tier separated by an observable boundary an actor can place a real case against.
- Set an intensity ceiling per tier — assign each tier the strongest action permitted at that level, so the permitted response is monotone in severity.
- Keep it monotone — anything permitted at a lower tier stays permitted at a higher one; the ladder only widens as severity rises.
- Name the boundary tests — state what evidence moves a case from one tier to the next, so tier placement is a reading, not a negotiation.
Tuning parameters¶
- Tier count — how many rungs the ladder has. More rungs track severity finely but blur the boundaries; fewer rungs are crisp but coarse.
- Boundary sharpness — how precisely each tier edge is defined. Sharp edges are unambiguous but create cliffs where a hair's difference doubles the permitted response.
- Intensity ceiling — how much action each tier unlocks. Generous ceilings speed response and risk over-reaction; tight ceilings force escalation sooner.
- Override slack — whether an actor may act above the ceiling in a declared exception, and how that is logged.
When it helps, and when it misleads¶
Its strength is calibrated response: it prevents both the timid under-reaction that lets a serious condition fester and the reflexive over-reaction that answers a small problem with a large blast radius. It operationalizes the proportionality principle — that the force of a response should be commensurate with the severity of what provokes it — which is exactly the constraint a blanket permission lacks.[1]
Its failure mode lives at the tier boundaries. Sharp thresholds create cliffs and gaming: an actor who wants a stronger action nudges the case's framing into the next tier, or a genuinely severe case sits one indicator short of the boundary and gets an under-powered response. The guarding discipline is to define tier boundaries on observable, hard-to-fake indicators and to review boundary-adjacent cases periodically, so the ladder tracks real severity rather than the labels actors can attach to it.
How it implements the components¶
Engagement Threshold Table fills the graduated-response side of the envelope — degree, not kind:
condition_trigger_set— the ordered severity or state tiers are the conditions that index the table; placing a case in a tier activates its row.proportionality_constraint— the core: each tier's permitted response is scaled to the severity it represents, and the ceiling rises monotonically with severity.permitted_action_catalog— each tier's ceiling is expressed as the concrete actions unlocked at that level.
It does not enumerate categorical off-limits actions — prohibited_action_boundary is Rules-of-Engagement Matrix's — nor does it define who is eligible to read and act on the table; authorized_actor_profile sits in Delegated Authority Charter. The table scales the degree of a permitted response; the matrix rules a kind of action in or out.
Related¶
- Instantiates: Conditional Authority Envelope Design — the table is the proportionality dial that ties permitted intensity to severity.
- Sibling mechanisms: Delegated Authority Charter · Rules-of-Engagement Matrix · Field Decision Card · Readback Authority Confirmation · Scenario Rehearsal Protocol · Exception Escalation Form · Temporary Authority Window
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Engagement Threshold Table operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it converts severity or state tiers into a graduated ladder of proportional response, so a mild condition unlocks a light action and a severe one a stronger action.
Independent corroboration: The frozen evidence defines Engagement Threshold Table as 'Converts severity or state tiers into a graduated ladder of proportional response, so a mild condition unlocks a light action and a severe one a stronger action', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Representation, Specification & Plan — Although embodied as a table, its tier cells impose standing response ceilings and boundary tests rather than only externalizing information.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Proportionality and use-of-force doctrine established observable severity and threat as limits on the intensity of an authorized response.
Related originating lineages:
- Criminology & Forensic Studies — Police use-of-force continua independently operationalized threat-to-response tiers.
- Military & Strategic Studies — Rules-of-engagement practice supplied graduated response and preauthorized force levels.
Review resolution: DOJ policy directly ties reasonable force to crime severity and immediate threat, while official rules-of-engagement guidance requires graduated response; law is the broad primary lineage.
Attribution caveat: Legal proportionality and military and policing engagement ladders are independently formative.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] United Nations. Basic Principles on the Use of Force and Firearms by Law Enforcement Officials. United Nations (1990). States the proportionality principle for force: when force is unavoidable, it must be proportionate to the seriousness of the offense and the legitimate objective. registry ↩ Show verification details
SupportedVerified against the work's full text
Principle 5(a) of the UN Basic Principles requires that unavoidable force be used with restraint and in proportion to the seriousness of the offence.
“Exercise restraint in such use and act in proportion to the seriousness of the offence”