leans against the fence, watching the dust settle after the round-up
Every settlement — every decision, meeting, argument, agreement, or event — leaves two things behind. There is the thing you can see: the document, the decision, the summary, the artifact. And there is the thing you mostly cannot see: the residue. The residue is what the settlement does to the future. It is the shape of the field after the herd has passed through.
Residue mapping is the practice of making those hidden after-effects visible enough to learn from them.
The Basic Split
For any settlement (A_e):
- Artifact (X_e): the explicit, shareable output. The memo. The vote. The contract. The transcript. The promptable structure.
- Residue (R_e): the conditioning effects that enter later occasions. Moods, new categories, shifted relationships, unresolved tensions, easier or harder paths, changed boundaries, new rules, altered resources.
The artifact is what you hand to the next person. The residue is what they actually inherit. Confusing the two is like confusing a map of a river with the river’s sediment.
Seven Residue Types
Residues show up in overlapping ways. These categories help you notice them without forcing a single label onto what is probably mixed.
| Type | What Changes | Example |
|---|---|---|
| Affective | Feelings, tone, urgency | This topic now feels hot. We avoid it without knowing why. |
| Distinal | New distinctions, categories | We now see a difference we could not see before. |
| Relational | Trust, distance, obligation | The two teams no longer assume good faith. |
| Tensional | Unresolved pressure | A contradiction keeps surfacing in new forms. |
| Directional | Path accessibility | This option became easier to say; that one became harder to propose. |
| Boundary | Inclusion, exclusion, admissibility | Something once sayable is now off-limits. Something once off-limits is now normal. |
| Material | Bodies, rules, resources | A new policy, budget allocation, or physical change. |
One settlement usually leaves several residues at once. The goal is not perfect classification. The goal is to stop missing what is actually happening because you are only looking at the artifact.
How to Map Residues
A practical map is built in passes. You do not need to capture everything. You need to capture enough, in time, that the next occasion can see what it is inheriting.
1. Anchor the settlement
Name what happened. What was decided, when, by whom, through what process. Keep it separate from the surrounding conversation and the artifacts that came out of it.
2. Save the artifact
Record the explicit output for reference. But do not mistake it for the residue. The artifact is evidence. The residue is the after-effect.
3. Check later, at least twice
- Short horizon: after the first round of consequences has had time to appear.
- Medium horizon: after at least one more cycle of decision or lived interaction.
- Longer horizons: for institutional, material, or deeply relational residues.
Most residue is invisible immediately. It needs time to settle.
4. Tag what you find
For each detected effect, note: - its dominant mode (affective, relational, boundary, etc.); - its strength or cost weight; - whether it is already shaping later decisions; - whether people agree it exists or argue about it.
5. Test independence
Could this effect have been generated only by recirculating the old artifact? If it could have come from the memo being forwarded around, it is less significant. If it came from lived contact, friction, or structural change, it is more significant. Real residue is not just the artifact in disguise.
6. Check for reconditioning
Is this residue actually altering how future decisions get made? A residue that does not enter the next possibility field is not yet a residue in the operational sense. It is only a potential one.
7. Keep it open
Every entry is revisable. New horizons reveal new residue. Old residue can be reinterpreted. The map is a living object, not a final ledger.
Minimal Recording Format
A single residue log entry might look like this:
- Settlement: [what happened, when, by whom]
- Artifact: [link or summary of explicit output]
- Horizon: [short / medium / long]
- Detected residue:
- Mode: [affective, relational, etc.]
- Description: [what changed]
- Confidence: [low / medium / high]
- Already conditioning? [yes / no]
- Reconditioning observed: [which dimensions changed]
- Status: open
Multiple entries over time for the same settlement make the map. The map is not a snapshot. It is a trail.
Why This Matters
- No residue tracking, no history. You are flying blind through your own past.
- Fast artifacts plus hidden residues equals a self-reinforcing loop. You keep using your own outputs as inputs without seeing what they are costing you.
- Artifact-residue confusion means boundary decay. When you cannot tell what is the settlement and what is the after-effect, your categories start to dissolve.
- External inputs that leave no residue are decoration. Contact with the outside only helps if it changes the internal configuration. Otherwise it is just more grist for the same mill.
The goal is to keep enough of the hidden inheritance visible that later occasions can treat prior settlements as real consequences rather than as disposable background.
Watch Yourself
Mapping residues changes the system. Naming a tension can amplify it. Ignoring a residue can make it heavier. Treating the map as another high-cadence artifact can make the practice ceremonial.
So occasionally map the mapping itself. Ask what the residue log is leaving behind. The instrument is only honest if it is willing to audit its own effects.
The cowboy does not believe in complete records. The cowboy believes in records good enough to ride by.