Collab OSCommons

← A Digital Pattern Language

Product Recurringintelligencespace

Show the Route

Every result can be followed back to what made it.

Wherever results arrive cut off from their causes, holding the tension between trust that depends on the route and explanation that costs space, the design connects each result to what produced it and reveals that route on demand, while contracting the explanation to a single line until someone asks. People can witness how a thing really came to be and discover its source for themselves, and the place gains honest, effective and generative.

Context

Any surface that shows the results of a process the person didn't watch: a meeting summary, things arriving from elsewhere, a generated animation. It grows more urgent as machines do more of the work, because machine output is the easiest thing to cut from its cause.

Tensions

  • Trust and understanding depend on seeing where a result came from ("Trust depends on who sent and who vouched").
  • Explanation costs space, and most of the time nobody needs it.
  • Results arrive cut off from their causes: a summary from its meeting, an item from its sender, an output from its graph.
  • Hidden: "Hidden routing is how platforms manipulate."

Forces the design applies

  • reveal on reveal ↔ obscurethe route behind every result: sender, rule, source moment or wire
  • connect on connect ↔ severeach claim or item, tied by a visible thread to the concrete thing that produced it
  • contract on expand ↔ contractthe explanation itself: a path line or a chip until someone asks

Solution

Every result keeps a visible thread back to what produced it: a sender and a rule, a spoken moment, a wire. Show the thread small by default, and let one gesture open the whole route.

The generative parameter is what kind of route: evidence in Collab OS (a claim back to the moment it was said), social in TrustFlow (who sent it, who passed it along, which bridge and rule let it through), causal in Weft (which inputs move the output). A second decision follows, how much shows by default. TrustFlow and Collab OS fold the route into a line or a chip; in Weft the route is the surface.

  item    ◀── rule ◀── bridge ◀── sender      TrustFlow
  claim   ◀── 00:14:32 in the recording        Collab OS
  output  ◀── node ◀── node ◀── slider        Weft
          one line by default · the whole route on demand

Acts

  • Strengthens: witness (seeing truthfully how a thing came to be), discover (following the thread to its source).
  • Weakens: react, the response to a thing that arrives with no context.
  • Gap this surfaced: verify or trace (TrustFlow lists "trust, understand"). There is no act for checking something for yourself, a perceptual verb the list still lacks.

Qualities it gives the place

HonestEffectiveGenerative

Refuses

  • Truth erosion The family that makes the surface say something other than what the system is doing.
  • The correct answer you can't read back a tool that permits the right result while withholding the understanding of it
  • The opaque baked animation Motion baked into a file nobody can read, so how it works can't be learned or changed.
  • AI slop Machine-made text passed off as considered work, filling the place where a person's words should be.

McLuhan check

  • Enhances: trust, and the ability to check.
  • Retrieves: the footnote and the provenance record.
  • Obsolesces: the "trust us" summary and the black-box ranking.
  • Reverses into: the route as noise. Shown in full, a route stops being readable: Weft's 108-node patch had every wire visible and correct, and its maker still could not read it back. "Every one of those bugs is a thing the editor could have shown him and didn't."

Required companion: the route must be legible at the size you meet it. Name the units, dim what leads nowhere, and lead with one line before the full trace (Name It or Build It Again).

Connections

Rolls up to
honest
Completes
none yet
Siblings
Intention Shown as Intention, It Left, but Still Has a Home, Machine Carries, Human Judges, Name It or Build It Again
Completed by
none yet
Not yet written
Every Claim Links to Its Moment, Why Am I Seeing This

Seen in

  • Collab OS (production): the July research asks for "claims linked to their spoken moments", so that "users validate the AI in one click instead of distrusting the whole summary" (Meeting Artifacts). On the artifact page every quote and decision carries a timestamp: "Click seeks the recording · right-click opens the transcript".
  • TrustFlow (v2 prototype): "Every crossing shows its path (sent, passed along, signaled) and opens a plain "why am I seeing this" that names the bridge and the rule." Even a bridge carries its origin: the call that opened it is "recorded as provenance".
  • Weft (live): with a wired graph, "you can see why the thing moves." Posed as a question ("Is "inspectable causation" a candidate pattern for the PAL?"); the legibility pass shipped in v0.16.

Elsewhere

Precedents the footnote and the citation · provenance records for artworks and archives; the legal chain of custody · Excel's Trace Precedents · Facebook's "Why am I seeing this post?" (2019) · Granola's link from each AI bullet to its transcript moment

In nature An ant trail: the route is laid down as it is walked, so others can follow a find back to its source.

Recurring. (three projects). Weft differs most: there the route is the medium itself, not a note attached to a result.