Dark Mode — Atlas, crystallized: the socialization & discovery layer (anti-algorithm public square + ballot intake) #95

Milestone: Dark Mode. Names what Atlas is now that it has shed its second big idea. It split Tell functionality once; #94 splits aggregation off too. What remains has proven to be a concrete layer all by itself — and it's the point of Atlas. Serializes intent; shape, not settled spec.

What's left after two splits

Atlas was housing several ideas at once, which is why it kept having to divide:

• it split Tell (the private answering room moved to poll.html/the Tell engine);
• now it splits aggregation (Dark Mode — the cascade tier: containment distillation is Antidote's, not Atlas's (COMMON CONSTITUTIONs, the placement ledger, the default-hold boundary) #94 — rollup is the Antidote cascade's, because only an Antidote can determine a COMMON CONSTITUTION).

And yet something is still unmistakably there: the discoverability infrastructure — which proved itself a concrete layer the moment it also served as intake for hand-carried ballots (#86). That residue is Atlas. Everything below describes it.

Atlas is the public square — socialization + discovery

Atlas is a socialization and discovery layer: a public square where you can plug in your own sources and talk about them in the open, with no owner-operator over anything except space they carved that you can fork. It is a more powerful discussion space than a Tell — but it holds no one's data hostage and delivers nothing by fiat.

Shape is a useful mask, not a requirement

Opening an Atlas is often a civic act — you want things discoverable on a shape (the containment world of #94, where a constituency is a polygon). That case stays first-class and important.

But plenty of atlases have nothing to do with shapes. Group a D&D scene; group any business by any higher label — relaxation → parks, spas, trailheads. Atlas lets you use powerful labels to group things with no shape at all. The shape is just a useful mask; when there's no need for the mask, it's implicitly the whole state. Discovery by label is the general case; discovery by shape is the civic special case.

What an owner-operator actually controls

The owner-operator is, at core, just someone willing to do the hosting for an Atlas connected to other topics. They pick an ideology — a constitution, maybe forked and edited — but their power is strictly bounded:

• they describe space for other Atlas data to flow into, as a connective hub;
• their constitution governs what's allowed to cross the wire to come IN — never what you can go OUT to see;
• they cannot stop you forking theirs, and no one can squat on a name;
• they cannot make you do anything.

Tell vs. Atlas — the room and the square

• A Tell is a room where the participants are definitely in it with you — they may not be speaking, but they're present. Polls distributed at the Tell level are private.
• The instant a Tell plugs into an Atlas, its polls become discoverable — but don't transit any wire. Discovery is a listing, not a delivery.
• A freshly-started Atlas might have only connective tissue to other atlases and deliver nothing to anyone unless Tells subscribe to it. It's public, so people may simply discover it — it's listed.

The anti-algorithm hypothesis

There is no ranking algorithm. To list things at all, Atlas must label-reduce them (#80/#79) and compare constitutions — and that's the whole of its "curation." Where traditional companies and law have decided an algorithm is not responsible for its decisions, our evidence should say we disagree: whatever algorithm exists consigns everything it touches, so it should sign everything — and if you're not signing, you're doing that on purpose.

So Atlas is an inert, signed, self-explaining categorization — an API for the community you query with the primitives it gave you, that just shows how it had to categorize things to be useful at all. The slimmest promise about curation we can offer. If you missed things, there are diffs to interpret — through an agent, if you like — to see what fractures happened. This anti-algorithm posture is a large part of why local matters at all: ideological groups (Tell servers) congregate around canonical subjects they know how to talk about, and no one can squat the name or coerce them.

Paying never buys infrastructure

You don't have to pay anyone to make something happen. Someone might wire a payment processor into their PR-completion — but that's not an infrastructure decision. Anyone who charges for PR completion is still on public discovery; they're merely gating who is discoverable to them from their manicured position — paying to be their friend, like a curated listing board (the Google-ish "we say this is valuable to be socialized within"). The public square underneath is unpriced and unstoppable.

Anti-flood — traffic is digested by its members

Atlas traffic has to be digested by its members so it can't be flooded over. There is more to spec here — how digestion works, how to unclog it — so that discoverability isn't an attack surface. (Flagged, not solved.)

The ballot-box promise binds Atlas to Antidote

This is the through-line. Because an Atlas is a public square that also catches hand-carried ballots, it will start getting traffic addressed to no one it hosts — lost mail. The binding promise:

You're going to start getting this traffic. An Antidote will take it from you. It's that simple.

It's the community Wi-Fi your ISP tries to sell you, inverted into a public good: you provide coverage for people who are lost by being on your network — and it's a genuine public good not because the Wi-Fi was free, but because you are literally carrying unanswered data. You were there to take it, so please be there to forward it. If your Atlas doesn't have what someone's looking for: tell your friends, put it in your archive, and let Antidote take it away to figure out what to do with it.

• A careless owner-operator is still backed by regular procedure — if they have anyone subscribed at all, that traffic was hopefully already flowing to an Antidote. That's what Antidotes are for.
• When a spontaneous Atlas makes data that no Antidote constitution asked for, it's free to sift down to the state tray as runoff — retained for future distillment by a useful asker. This is the runoff tray (Dark Mode — the cascade tier: containment distillation is Antidote's, not Atlas's (COMMON CONSTITUTIONs, the placement ledger, the default-hold boundary) #94, antidote/docs/cascade.md): how to know what you didn't ask. Antidote, by retaining records, promises you can ask about what you missed — and everything you can query carries a constitution expressly permitting that use. A public servant's search for what was even being spoken about before they started paying attention.

Guards / non-negotiables

• Atlas hosts no aggregation and no Tell — it is discovery + socialization + ballot intake, and the live coarse gauge of its own scope. Rollup is the Antidote cascade's (Dark Mode — the cascade tier: containment distillation is Antidote's, not Atlas's (COMMON CONSTITUTIONs, the placement ledger, the default-hold boundary) #94).
• Forkable, un-squattable, un-coercive — an owner describes space and an intake constitution; they cannot stop you going out, forking, or naming.
• Signed or it doesn't count — the anti-algorithm hypothesis: unsigned categorization is a choice against accountability; Atlas signs how it sorted.
• Discovery never delivers — a listing makes a Tell's polls findable; it transits no wire without a subscription.
• Backed by Antidote — a running Atlas with any subscriber is forwarding lost mail to an Antidote; the ballot-box promise is the binding.

Open questions

• The fork-and-backup apex policy. An owner can vanish. Should the apex domain's standing policy be to fork your Atlas and keep it current — "if you vanish, we're still here"? How do we survive an origin force-push that destroys data (the possessed/careless origin)? Partly answered by "if it was running, it was sending to Antidote," but the live-mirror policy wants specifying.
• Anti-flood mechanics — how member-digestion throttles, how to unclog, and the attack-surface analysis.
• Non-shape discovery — the label-only grouping (D&D, parks/spas) as a first-class Atlas mode, and how "no mask = the whole state" is represented.
• Payment-gated PR completion — confirming it stays strictly a who-can-reach-me curation, never an infrastructure toll.

Coupled / see also

• Dark Mode — the cascade tier: containment distillation is Antidote's, not Atlas's (COMMON CONSTITUTIONs, the placement ledger, the default-hold boundary) #94 (the cascade tier — where aggregation went), Dark Mode — the ballot drop door: hand-carried ballots arriving at an Atlas (forward-first, thresholded custody, mandatory fragmentability) #86/Dark Mode — the Atlas-fronted poll + network-addressed ballot: the transformed Tell-derivative, collectible on any lineage Atlas #87 (the ballot drop door + fronted polls — Atlas as intake), Dark Mode — the aggregation "place above": archive-merge across lineage wings, as a POSITION not an operator #88 (the place above → Antidote — where the lost mail lands), The Atlas-owned hearsay pile: provisioning, multi-tenant key management, lifecycle, and deflate-to-archive #91 (deflate-to-archive).
• Dark Mode 0 — the labeling commons: solve before the origin items (design round) #80 (the labeling commons), Dark Mode 9 — the label reducer reads documents: reverse digital form, TTL fetches, query-miss telemetry #79 (the reducer reads documents) — the label-reduce substrate under "no algorithm."
• OPEN-QUESTIONS.md §C (re-tiered: aggregation → Antidote; Atlas = the live coarse gauge + intake), §M/§N (neighbors-not-a-graph; claims-about-a-subject).
• atlas.anecdote.channel/notes/boundary-canon.md (structure is a position; conventions not authority), bin/drop.mjs (the intake door), bin/atlas-index.mjs (the signed, forkable directory).
• antidote/docs/cascade.md (the runoff tray; the cascade this Atlas feeds).