Coverage / Reachability¶
Core Idea¶
Coverage asserts that every required target in a target set is reachable from the system's inputs, pathways, or mechanisms — completeness in the surjective direction. The failure mode is a gap: a required target reached by no source. The claim is silent about uniqueness, efficiency, or whether multiple pathways exist.
How would you explain it like I'm…
A Crayon for Every Colour
Reach Everything, No Gaps
Every Target Reachable
Broad Use¶
- Software testing: branch, path, and statement coverage — every code branch exercised by at least one test.
- Network reachability: every required destination reachable from every required origin in the routing fabric.
- Public policy: every entitled beneficiary class has at least one accessible pathway to the benefit; gaps are eligible-but-unreachable populations.
- Access control: every required action permitted by at least one granted role; an unpermitted required action breaks the workflow.
- Curriculum design: every required competency taught by at least one course; an uncovered competency is a graduation gap.
- Failure-mode analysis: every documented failure mode has at least one mitigating control; an uncovered mode is a hole in the safety case.
Clarity¶
It distinguishes completeness in the surjective direction from neighbouring completeness claims, and foregrounds the target set as a design object: coverage is meaningful only relative to a stipulated set, so an honest claim must state its target set explicitly.
Manages Complexity¶
It reduces heterogeneous problems to one five-step procedure — enumerate targets, map pathways, identify gaps, close gaps, watch for target-set drift — that a test engineer, network architect, and safety analyst all run under different names.
Abstract Reasoning¶
Because coverage is monotone in pathways and relative to the target set, the non-obvious move is to treat target-set drift, not pathway failure, as the dominant silent failure: a quietly growing target set leaves an old, still-cited coverage proof that no longer covers.
Knowledge Transfer¶
- Across domains: required-target set maps to branches / destinations / beneficiary classes / competencies; the relation maps to exercises / routes-to / reaches / teaches; the audit is invariant.
- The portable lesson: the most dangerous coverage failures are usually unexamined growth of the target set, so the audit must re-anchor on it every time.
Example¶
A test report citing "92%" branch coverage silently goes stale the moment a developer adds a new if, because the target set enlarged while the old proof was measured against a smaller one — fixed honestly by writing a test, cosmetically by excluding the file.
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Coverage / Reachability is a kind of Surjectivity — The file states outright "Formally, the pattern is the surjectivity of a relation R from a source set S to a required-target set T", calls itself "the surjective sibling of injectivity" and "the specific surjective form" of completeness, and its own cross-ref link is
surjectivity. The worklist confirms surjectivity is a canonical/candidate prime (injectivity its co-equal dual). Direction: coverage_reachability is-a surjectivity, specialized to an explicit required-target set with the gap/monotonicity/ target-drift apparatus added — genuine specialization, not a duplicate. surjectivity is a valid (CAND-NEW-011) slug. Medium conviction because the added target-set-relativity makes it arguably a co-equal applied sibling rather than a strict child; child_of surjectivity is the better-fitting direction.
Path to root: Coverage / Reachability → Surjectivity
Not to Be Confused With¶
- Coverage / Reachability is not Traceability because traceability is a per-element provenance claim (each artefact links back to its source), whereas coverage is surjective completeness (every target reached by some source).
- Coverage / Reachability is not Redundancy because coverage demands at least one pathway and is silent about a second, whereas redundancy demands more than one and adds resilience coverage never offers.
- Coverage / Reachability is not general Completeness because coverage is the specific surjective form — completeness of a relation relative to a stipulated target set, monotone in pathways.