Trace Connections

## Setup: Track this exercise with Beads

```bash
bd create "Praxis: Trace connections for [module]" --type=research --labels=learn,foundations
bd create "Map upstream dependencies" --type=task --labels=learn
bd create "Map downstream dependents" --type=task --labels=learn
bd create "Evaluate system coherence—does it serve the whole?" --type=task --labels=learn
```

---

Help me trace connections for [MODULE] and evaluate its role in MY system.

I'm learning to think at the Heidegger level: "Does this serve the whole?"

Map [MODULE]'s connections:

1. **Upstream dependencies**: What does this module import/depend on?
2. **Downstream dependents**: What imports/uses this module?
3. **Data flow**: How does data enter and leave this module?
4. **System role**: What would break if this module didn't exist?

Create a dependency diagram (ASCII or mermaid).

Then evaluate:
- Does this module have a clear, singular purpose?
- Are its boundaries well-defined?
- Does it serve the larger system, or does it create coupling?

End with MY Heidegger principle: a one-sentence rule about system coherence.

The module I want to trace: [YOUR_MODULE_PATH]