Skip to content

Uncovered-Target Triage

Gap-resolution process — instantiates Target-Complete Mapping Design

Works the register of uncovered targets one by one, assigning each an accountable owner and a disposition — fix, defer, or authorized exclusion — so no gap sits unowned or silently dropped.

A register of gaps that nobody owns is just a list of future surprises. Uncovered-Target Triage takes the set of targets with no valid witness and, gap by gap, assigns an accountable owner and a disposition: remediate now, defer with interim handling, or route to an authorized, time-bounded exclusion. Its defining move is that it neither detects gaps nor fixes them — it converts a passive register into assigned accountability, and it forces the honest choice between fixing a target and formally excluding it, so that a hard target is never quietly dropped to make the numbers look complete.

Example

An accessibility audit of a government web portal finds 40 WCAG success criteria unmet across various pages — a register of uncovered targets. Triage works each one. A keyboard trap on the login form is high-consequence and assigned to the front-end lead to fix this sprint. A missing caption on an archived video is deferred with an interim "captions on request" handling. A decorative-image alt-text issue on a page slated for deletion is routed to the exclusion register with sign-off, since the page retires next month and fixing it would be waste. Every one of the 40 now carries a name and a disposition. The outcome is that nothing sits in the register unowned, and each exclusion is explicit and authorized rather than a silent scope cut.

How it works

What distinguishes this process is per-gap owner plus disposition, with exclusion as a governed path — not detection and not repair. For each register entry it assesses consequence (reading the target's priority weight), assigns an accountable owner, and chooses a disposition: remediate, defer-with-interim-handling, or exclude. Exclusions are treated as a first-class, dangerous outcome: each requires authorization and an expiry, so an excluded target stays reviewable rather than disappearing from the denominator.

Tuning parameters

  • Prioritization rule — consequence, affected population, or effort. This sets the order gaps are worked and which get attention first.
  • Disposition thresholds — when a gap qualifies for deferral vs a mandatory fix vs an exclusion.
  • Exclusion authority — who may sign off an exclusion, and for how long, before it must be revisited.
  • Interim-handling bar — what stopgap must be in place before a gap may be deferred rather than fixed now.
  • Ownership model — a named individual owner vs an owning team.

When it helps, and when it misleads

Its strength is guaranteeing accountability — the archetype's "no unowned gap" — and forcing exclusions to be authorized and visible instead of a quiet scope reduction.[1] Its failure mode is that triage disposes of gaps but does not verify a fix actually landed; a target marked "remediated" still needs re-validation before it counts as covered. And lax exclusion authority turns triage into a laundry for dropping inconvenient targets under a respectable label. The classic misuse is mass-excluding low-visibility gaps to clear the board before a review. The discipline that guards against it is to bound and authorize every exclusion with an expiry, and to send every remediated gap back for validation rather than trusting the "done."

How it implements the components

Uncovered-Target Triage realizes the accountability-and-disposition slice of the archetype — the components that turn detected gaps into owned work:

  • gap_resolution_owner — it assigns a named, accountable owner (and a repair path) to each uncovered target so no gap is orphaned.
  • exception_and_exclusion_register — it routes accepted gaps to an authorized, time-bounded exclusion, keeping deliberate non-coverage explicit and reviewable.

It does not detect the gaps in the first place (that's Service-Area Gap Analysis and Coverage Counterexample Search), define the target space or its priorities (Scenario Enumeration Workshop), or confirm a remediated target is now genuinely covered (Witness Validation Test).

References

[1] Triage — from battlefield and emergency medicine — sorts cases by urgency and assigns each to a track when not everything can be handled at once. Applied to coverage gaps, it prevents the register from being worked in arrival order, or not at all, and makes the "we chose not to cover this" decision an owned, visible one. ↩