Design Language & Vocabulary

draft first cut, 2026-09-13.

The core metaphor: the trail

This ecosystem already shares one vocabulary — “the Atmosphere,” AtmosphereConf, atmospheric.reviews, AT Protocol Spaces described by its own author as “a deeply social & atmospheric primitive.” Breadcrumbs’ own contribution on top of that shared metaphor is the trail: a claim is legible only if you can retrace the crumbs behind it — back through its evidence, to whoever attested it, to the identity that vouched for them. The name is literal, not decorative: the project exists because that trail is currently invisible in institutional peer review, and the whole point is to leave one where none exists today.

Reused terms, not renamed

• Claim, Evidence, Question, Project — Discourse Graphs’ own node types, used as-is.
• Anchor + Sidecar — a public record paired with a gated companion record in an AT Protocol Space. Used with exactly these words so they read as the same primitive everywhere they appear.
• Sensor — a saved link that keeps listening, surfacing what the network later learns about it back to whoever saved it. Sharper than “bookmark” for what a claim’s provenance record actually does over time.
• Connection — a typed relation between two records (supports, opposes, explainer, helpful) — the same shape as an Anchor/Evidence edge, named the way the ecosystem it sits in already names it.
• Trail — breadcrumbs’ own addition: the retraceable path from a claim back through its evidence to its attestation. Also the name of the base record itself (id.breadcrumbs.trail) — one attested contribution, not the whole path; a deliberate overload of the same term, not an inconsistency.
• Front door — the citable, ISSN/DOI-eligible journal layer, atmospheric.reviews.

Trail, not pheromone trail

It’s tempting to describe shared attention as “attention traces” that recycle like an ant colony’s pheromone trail — a real and useful observation about how aggregate attention propagates through a network. But breadcrumbs’ own trail is not that: every crumb is a specific, attributed connection someone made on purpose — a claim, an evidence link, an attestation — not an anonymous emergent residue anyone can follow without knowing who left it or why. Human coordination doesn’t run on stigmergy the way an ant colony does; it runs on people making legible, accountable claims about each other’s work. Keep trail. Drop pheromone.

Visual register: inherit, don’t redesign

The front door (atmospheric.reviews) already committed to its own visual identity — carry that forward rather than introducing a second one for the same surface. Legibility should decrease deliberately as you move deeper into the stack: the front door reads as a calm, institutional journal; the sensemaking and data-plane tooling underneath can be more visibly experimental and atproto-native, matching the actual trust and audience gradient between the layers instead of pretending the whole stack is equally finished.

Tone

Plain and infrastructural — closer to the understated register of projects like Curvenote or Discourse Graphs (or iroh’s “less net work for networks”) than to attestation/impact-certificate marketing language. This matters concretely: an overly hyped framing risks brand integrity with the conservative funding agencies this effort also needs to be legible to.