Leakage Path Walkthrough¶
Structured inspection method — instantiates Leakage Path Containment and Recapture
Walks the actual boundary of a container end to end, with the people who operate it, to name every path a constrained quantity can escape through — before any of them starts losing.
Containment fails through paths, not through walls — and the paths that lose the most are usually the ones nobody wrote down. Leakage Path Walkthrough is the discovery step: a structured, cooperative trace of the real boundary of a container — following the quantity rather than the diagram — to enumerate every route by which it can exit, authorized or not. Its defining move is that it produces a path inventory before any loss has been measured: it is not an audit of what leaked (that comes later) and not an adversary trying to break out (that is the red-team's job) — it is the census of exits that every other mechanism in the archetype then acts on. If a path is not on this list, no alert watches it, no seal closes it, and no budget accounts for it.
Example¶
A regional water utility is losing roughly a fifth of what it pumps and cannot say where it goes. The walkthrough sends engineers and meter readers along the network itself, asking at every junction how could water leave here without being billed? The inventory that comes back is not one thing but a taxonomy: physical seepage at aging joints, meters that under-register at low flow, unmetered standpipes the fire service uses, the utility's own unbilled operational draw, and a cluster of illegal connections in one district. Each is named, located, and tagged as physical loss or commercial loss — the recognized split for non-revenue water[n1].
The output is a living map of exits, not a verdict. But that map is what makes everything downstream possible: the district with illegal connections gets a targeted alert, the low-flow meters go on a repair backlog, and the standpipe draw — legitimate but untracked — is handed to governance to formalize. None of that could be aimed until the paths had names.
How it works¶
The walkthrough's discipline is that it traces the container as it actually exists, not as designed:
- Define what must stay in. Fix the constrained quantity and the boundary it is supposed to remain within, so "escape" has a precise meaning.
- Follow the quantity, not the wall. Walk the flow physically or step by step with operators, asking prompting questions at every interface — how could it leave here, and who would notice? — in the spirit of a structured HAZOP guideword sweep.
- Name every exit, authorized or not. Distinguish sanctioned crossings from unintended ones, and record location, owner-if-any, and a first guess at magnitude.
- Leave a living inventory. The product is a maintained list of paths, not a one-time report — the shared substrate the rest of the archetype consumes.
Tuning parameters¶
- Scope and granularity — the whole system in a fast sweep, or one subsystem in forensic detail. Finer walks find subtler paths but cost time and tire the attention that catches surprises.
- Guideword set — the prompts used at each interface (pressure, incentive, convenience, workaround, corruption). A richer set surfaces non-obvious exits; too rich and the walk drowns.
- Who is in the room — designers see the intended boundary; operators know the real one. Skew toward the people who actually handle the quantity.
- Adversarial lens — how hard to imagine a motivated evader versus honest slippage. Turning it up overlaps the red-team's job; leaving it off misses deliberate exfiltration.
- Cadence — one-off versus recurring. Boundaries drift, so a walkthrough that is never repeated rots into fiction.
When it helps, and when it misleads¶
Its strength is that it makes the forgotten paths speak — the interfaces, exceptions, and quiet workarounds that a containment design assumed away — and it does so before they have cost anything, which is the cheapest possible moment to act. It also assigns provisional ownership, so no exit leaves the room unattached to a person.
Its failure mode is theater: a walkthrough that re-walks only the known, comfortable paths, produces a tidy document, and is filed. The map is not the territory — an inventory can look complete and still miss the one path that matters, and a boundary re-drawn since the last walk quietly invalidates it. The classic misuse is running it to satisfy an inspection requirement rather than to find leaks, which selects for paths that are easy to close over paths that actually lose. The discipline that guards against this is to make it recurring, operator-led, and adversarially prompted, and to treat the inventory as provisional until an audit or tracer confirms which paths are live.
How it implements the components¶
Leakage Path Walkthrough fills the discovery side of the archetype — the components that turn an assumed boundary into a named set of exits:
constrained_quantity_definition— fixes what must stay contained, so escape is defined precisely rather than felt vaguely.intended_container_or_boundary_model— reconstructs the boundary as it really is, against which unintended crossings become visible.leakage_path_inventory— its primary output: the enumerated, located, owner-tagged census of exits.
It does not measure how much each path loses (that is Mass-Balance Audit), watch a path for deviation (that is Anomaly or Shrinkage Alert), close one (Seal-and-Retune Patch), or adversarially exploit one (Red-Team Exfiltration Probe).
Related¶
- Instantiates: Leakage Path Containment and Recapture — the walkthrough supplies the path inventory the whole appraisal is built on.
- Sibling mechanisms: Anomaly or Shrinkage Alert · Leakage Budget Dashboard · Mass-Balance Audit · Red-Team Exfiltration Probe · Canary Token or Tracer Dye · Controlled Release Valve · Exception Log Review · Seal-and-Retune Patch · Post-Seal Displacement Check · Recapture or Recall Protocol · Side-Channel Scan
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Leakage Path Walkthrough operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it walks the actual boundary of a container end to end, with the people who operate it, to name every path a constrained quantity can escape through — before any of them starts losing
Independent corroboration: The frozen evidence defines Leakage Path Walkthrough as 'Walks the actual boundary of a container end to end, with the people who operate it, to name every path a constrained quantity can escape through — before any of them starts losing', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Process-safety and containment engineering developed physical walkthroughs tracing every potential release path across a boundary.
Related originating lineages:
- Disaster Management & Risk Reduction — Hazard inspection supplied multidisciplinary field review and escalation.
- Environmental Science & Climate Studies — Pollution-prevention practice materially shaped tracing fugitive losses and sinks.
- Organizational & Management Science — Gemba and process-walk practice contributed direct observation with the people operating the boundary.
Review resolution: Both independent reviews place the primary lineage in engineering_design. The queued differences (alternate_origin_disagreement) concern secondary metadata rather than primary provenance. The final retains disaster_management, environmental_climate, organizational_management only where a reviewer supplied a formative-lineage rationale; downstream application by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis records the relationship among origin traditions, while domain_reach=multi_domain records application breadth separately. encyclopedia_synthesis=true reflects whether either reviewer identified a corpus-specific synthesis, and confidence=high preserves the more cautious evidence assessment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The inventory this method produces is the archetype's shared substrate: alerts, budgets, seals, and recapture all aim at entries on it, so a path missing from the walkthrough is invisible to everything downstream. That is why the walkthrough is worth repeating even when nothing has visibly gone wrong — the most expensive leak is the one on a path no one ever thought to name.
[n1] Non-revenue water is the water industry's standard term for water put into a distribution system but not billed, conventionally split into physical (real) losses and commercial (apparent) losses — the same physical-versus-bookkeeping distinction a leakage inventory records for any constrained quantity. ↩