synthesis · syntheses/Legibility in the Lens, Not the Land.md
Legibility in the Lens, Not the Land
The founding principle for the wiki's front door. Organize the views freely; never reorganize the knowledge to suit a view. Wurman, Rao and Alexander look contradictory on legibility, and they reconcile once you separate the lens (how the reader sees) from the land (what is there).
The apparent conflict
- Wurman cures information anxiety by organizing: five hat racks make anything findable (LATCH).
- Rao/Scott warn that organizing driven by anxiety is the failure itself. Forests and cities flattened for the central eye die (Legibility).
- Alexander explains both. The mind can only hold a tree, while living things are semilattices (Tree vs Semilattice).
The reconciliation
Scott's states failed because they changed the land. They replanted forests and rebuilt cities so the map would be simple. Wurman's racks change only the lens. The hats stay the same; you rearrange how you look at them, and you can rearrange them again. So:
- The land (the wiki and
raw/) stays a semilattice. It keeps its overlaps, contradictions, seeds, tensions, and the mess Rao says is alive. The front door never "cleans up" content to fit a view. - The lens (the front door) offers several trees. The five LATCH views each make the wiki temporarily legible in one way, and you can always switch. No single view is canonical.
- The eye on the ground beats the eye in the sky. Show local neighbourhoods (a page and its 1–2 hop links) rather than the global hairball. Rao: "easier to comprehend the whole by walking among the trees."
- Grow it by unfolding. Build a thin whole, live in it, add the next differentiation where it's missing. Never a blank-slate master plan (Living Structure).
What this rules out
- A folder-tree sidebar as the main navigation. That makes the land's tree the lens.
- Hiding seeds, contradictions or unreviewed pages to look finished. That's legibility by demolition.
- A "perfect" upfront information architecture. That's high modernism.
Front-door patterns that follow (a sequence, per Pattern Language)
- Threshold: enter at what's alive now (latest ingest, an open question, a live tension), not at a menu.
- Five lenses: the LATCH views, each one step from the threshold.
- Page as center: content, backlinks, local neighbourhood.
- Glimpse: hover previews, so you can follow the overlap without leaving.
- Visible provenance: seeds, unsourced and auto-ingested pages look different.
- Frontier: open questions,
#to-readleads, and tensions, showing where to learn next.
Written out in full, with problem, instruction and examples per pattern, in Front Door Pattern Language (2026-11-08).
~~Open: Alexander's coherence test asks whether this sequence generates a whole front door. The way to find out is to build the thin slice and see.~~ Answered 2026-11-09: it did, in five unfoldings. Whether the door is alive is still to be judged by use. See the coherence-test verdict in Front Door Pattern Language.
Connections
- What's Scarce When Execution Is Cheap — the front door is a judgment-support surface; it should make the human's thinking easier, not replace it (T3).
- Method Reflection — T2 (the wiki as a semilattice) is this principle applied to storage.
- The Borges Map — a lens that tries to show everything is a 1:1 map.
- Navigation vs Search — Blumenfeld's graph index "never modif[ies] source files" and is "disposable cache you can rebuild": the same principle stated for a database.