Product Triedspaceintelligence

One Substrate, Many Lenses

One truth underneath. Every view is a way of looking at it, never a copy of it.

In a product used by people who need different arrangements of the same work, holding the tension between different audiences needing different views and forked views drifting apart, the design centralizes the record and lets each lens sort and reveal it its own way. People can then witness the same truth, cocreate from it and discover what one arrangement hides and another shows, and the place gains honest, harmonious and equitable.

Context

A product where several audiences look at one body of work: a team's canvas, a client's read, a planner's timeline, an admin's pulse. It holds where one party keeps the record. Where many parties each keep their own, the move inverts: TrustFlow's One Shared Shape agrees on the shape of what crosses and refuses to be the system of record. That's a different pattern (its tension is lock-in), not a variant of this one.

Tensions

Different audiences need different arrangements. The team wants a canvas, a client wants a calm read, a planner wants time.
Forked views drift apart and lie. A second copy is wrong by Thursday.
Each view wants its own fields. A canvas wants coordinates and a timeline wants dates, and both press to live in the record.
Hidden: building a new view as a copy is faster than building a lens.

Forces the design applies

centralize on centralize ↔ decentralizethe record: one system of record, one copy of every thing
sort on sort ↔ mixeach lens: it arranges the same things by its own key (place, list, time, rhythm)
reveal on reveal ↔ obscureeach audience: the arrangement it needs, from the same truth

Solution

Keep one record and make every view a lens over it. A lens may arrange, filter and size things, but it never holds its own copy, and what only a lens needs (a position, a zoom) lives in the lens, not the record.

The generative parameter is what each lens arranges by. Collab OS has four: place (Surface), list (Index), time (Time) and rhythm (Pulse), plus a team lens and a client lens over the same rows. A new view costs a new arrangement, never a new copy.

   Surface     Index     Time     Pulse       lenses: arrange, filter, size
       ╲         │         │        ╱
   ─────┴────────┴─────────┴───────┴─────
     one record: actions, initiatives,          positions live in the lens,
     collaborations, organizations              never in the record

Acts

Strengthens: witness (everyone sees the same truth, arranged for them), cocreate (team and client work from one record), discover (switching lens shows what another arrangement hid).
Weakens: none of the dominant verbs. What it removes is a chore, reconciling two copies, and the quiet lie that follows when nobody does.

Qualities it gives the place

HonestHarmoniousEquitable

Refuses

Misleading visual hierarchy the client view must not style reassurance over truth

McLuhan check

Enhances: agreement between views, and new views that are cheap to add.
Retrieves: the base map and its overlays; the ledger behind every report.
Obsolesces: the hand-kept client report, the spreadsheet export, the "which version is right?" meeting.
Reverses into: a lens that lies by omission (one record doesn't stop a client lens filtering out the bad news), or a record bent out of shape to serve its lenses.

Required companion: Deliberate Release. With one record under every lens, what each audience may see must be an explicit choice, or the client lens leaks the team's drafts. Collab OS keeps document audience and surface-item visibility as "separate, explicit controls".

Connections

Completes: none yet
Siblings: none yet
Completed by: One Object, Many Sizes, Stable Ground
Not yet written: Coordinates Never Live in the Data

Seen in

Collab OS (July note): "view models over one dataset", and "Already built; the pattern names why it's right."
*Collab OS (research 06, Spatial Interfaces for Work):* "the city-builder overlay is the strongest validated metaphor for the view-model engine", with "one stable spatial substrate, many togglable data lenses over the same map."
Collab OS (September): "Surface, Index, Time and Pulse views over one dataset. The card grammar then carries the idea down to the component rung: one renderer, many contexts."
Collab OS (CLAUDE.md): "Team gets rich/spatial views; clients get simple read-appropriate views of the same data."

Elsewhere

Precedents Model-View-Controller (Reenskaug, Xerox PARC, 1979) · SimCity's data-map overlays · thematic map layers over one base map

In nature Jakob von Uexküll's Umwelt: one meadow, and each creature in it lives in its own perceived world of that meadow, the tick's of warmth and scent, the bee's of ultraviolet.

Tried. Built, in one project. Most database apps show several views of one table, so a second instance would be cheap to claim; none is claimed until another project splits audiences and lenses on purpose.