Dependency-Tracing Workshop¶
Elicitation workshop — instantiates Latent Constraint Preservation Audit
A facilitated session that traces outward from a structure to map every system, workaround, and operator that silently touches it — including the couplings no diagram records.
The Dependency-Tracing Workshop starts from the structure and follows its threads outward. Given a specific artifact proposed for removal, a facilitated group walks the graph of everything that reads it, writes it, waits on it, or works around it — pulling in the informal couplings that never made it into an architecture diagram. Its defining move is tracing connectivity from the carrier: it is not a broadcast to find unknown users (that is the survey) and not an excavation of why the thing exists (that is reconstruction); it maps what is wired to what, right now. The output is a concrete inventory of the structure and a register of its live dependents, assembled in a room where the people who actually touch the system can say "wait — the billing job reads that too."
Example¶
A software team wants to drop a database column, legacy_customer_tier, that no current feature seems to use. The migration looks trivial. In the workshop, the column is put at the center of a whiteboard and the group traces every thread. A grep of the codebase finds three services that select it. The data team notes that the nightly analytics export joins on it. A support engineer remembers a manual runbook that keys off it during escalations. Someone from finance realizes a spreadsheet macro, pulled straight from a read replica, buckets revenue by that tier every quarter-end — a coupling that exists in no repository at all. By the end, the "unused" column has six live dependents, two of them completely outside the codebase. The workshop does not decide whether to keep the column; it converts "nothing uses it" into a precise map of exactly what does, so the removal (if it proceeds) knows what it must migrate first.
How it works¶
- Fix the structure at the center. Name the exact artifact and its boundaries precisely enough that "touching it" is unambiguous — this is the inventory step.
- Trace outward along every edge. Systematically follow reads, writes, triggers, and timing dependencies; use code search, logs, and schemas as evidence, not just recollection.
- Harvest the informal couplings. Explicitly ask the room for workarounds, shadow tooling, manual runbooks, and out-of-band consumers — the connections that formal diagrams omit.[n1]
- Register each dependent. Record every system and operator found, with how it touches the structure, producing a dependency map the loss model and migration plan can build on.
Tuning parameters¶
- Trace depth — how many hops out from the structure the group follows. Deeper tracing finds second-order couplings (the job that feeds the report that a regulator reads) but expands the session and can wander.
- Evidence bar — whether a claimed dependency must be confirmed in code or logs, or can be logged on a participant's say-so. A hard bar avoids phantom dependencies; a soft bar avoids missing real but undocumented ones.
- Room composition — which functions are in the room. Missing a discipline means missing its couplings, so breadth of attendance is the highest-leverage dial — and the easiest to under-invest in.
- Timebox — a single focused session versus an iterative trace over days. Iteration surfaces the couplings people remember later, at the cost of scheduling drag.
When it helps, and when it misleads¶
Its strength is that it finds the load-bearing coupling nobody documented before a removal snaps it — the export join, the quarter-end macro, the escalation runbook. Because it works from live evidence and a room of practitioners, it is especially good at the technical and operational dependencies that architecture diagrams flatten or omit.
Its failure mode is bounded by the room: the workshop can only trace the connections its attendees know or can look up, so a dependent whose owner was not invited stays invisible, and the map can feel complete while missing an entire quadrant. It is also prone to presence bias — vivid, well-represented systems get traced thoroughly while quiet, unglamorous consumers (a low-frequency batch job, a downstream partner) are under-explored. The classic misuse is treating the resulting map as exhaustive and green-lighting the cut, when the workshop only ever finds known-reachable dependents. The guarding discipline is to pair it with a broadcast discovery step for the dependents no attendee can name, and to treat any "no dependencies found" branch as an unexamined risk rather than a clearance.
How it implements the components¶
persistent_structure_inventory— it pins down the exact structure and its boundaries as the anchor of the trace, producing the concrete named object the whole audit needs.dependency_and_stakeholder_register— its core output: the mapped set of systems, jobs, and operators that touch the structure, each with how it depends.
It does NOT implement persistence_evidence_signal — that is its nearest twin, Silent Dependency Survey, which reads rare-but-critical usage across a whole population as a signal of hidden load-bearing. This workshop maps who is *connected to the structure; the survey discovers who silently relies on it without appearing in any trace. Reconstructing why the structure exists (original_function_hypothesis) belongs to the interview and reconstruction mechanisms.*
Related¶
- Instantiates: Latent Constraint Preservation Audit — the workshop is the archetype's "map what touches the structure" step.
- Sibling mechanisms: Silent Dependency Survey · Constraint-Loss FMEA · Chesterton's Fence Review Gate · Compensating Control Matrix · Deprecation with Rollback Window · Historical Rationale Reconstruction · Legacy Function Interview · Post-Removal Sentinel Dashboard · Removal Sandbox Trial
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Dependency-Tracing Workshop operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it a facilitated session that traces outward from a structure to map every system, workaround, and operator that silently touches it — including the couplings no diagram records.
Independent corroboration: The frozen evidence defines Dependency-Tracing Workshop as 'A facilitated session that traces outward from a structure to map every system, workaround, and operator that silently touches it — including the couplings no diagram records', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Operations management cohered practitioner workshops that trace current handoffs and shadow work outward from a structure under review.
Related originating lineages:
- Computer Science & Software Engineering — Architecture dependency tracing supplied the directed reference-graph logic.
- Ethnography & Qualitative Methods — Practice-centered elicitation supplied discovery of informal and undocumented couplings.
Review resolution: Operations management cohered practitioner workshops that trace current handoffs and shadow work outward from a structure under review. The retained alternate lineages materially shaped the mechanism's form.
Attribution caveat: The workshop uses technical tracing logic but relies on qualitative recovery of shadow dependencies.
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¶
[n1] Shadow IT — the tools, scripts, spreadsheets, and workarounds that staff build outside official systems — is the usual home of undocumented dependencies. Because it appears in no architecture diagram, it is exactly the coupling a codebase-only trace misses and a workshop with practitioners in the room can recover. ↩