# Choir News, Web Desktop, Automatic Radio

Canonical: https://mosiah.org/articles/choir-news-web-desktop-automatic-radio/
Interactive: https://mosiah.org/#Articles%2Fchoir-news-web-desktop-automatic-radio

!! The platform split

The product is not three systems. It is one substrate with different projections.

[[choir.news]] is the automatic newspaper: the public artifact graph, the public memory layer, the place where vtexts, sources, citations, claims, corrections, voices, and appagents become traversable by people and agents. It should be readable without ceremony. The first posture is not account creation; it is public orientation.

The individual desktop is the automatic computer: a personal runtime, a mutable workspace, a state boundary. A user reads the global newspaper, touches an artifact, tries to annotate, fork, save, run, publish, or call heavier inference, and the system asks them to register because they are no longer merely reading. They are making state.

Account creation should therefore feel less like signing up for a SaaS account and more like acquiring a computer. The implementation image is concrete: fork a new user VM from the global VM image. The user gets a personal automatic computer that can publish selected vtexts, apps, agents, sources, and transforms back into the global automatic newspaper.

Automatic radio is the same substrate under a screenless constraint. The web desktop is the general case; radio is the embodied traversal case. iPhone and Android matter commercially, but Apple Watch is the useful design pressure: if the interaction grammar works on the watch, it is not secretly a desktop app with a voice button. It is radio-native.

!! Operating distinction

The newspaper is public memory. The computer is mutable agency. The radio is traversal in embodied time.

That distinction keeps the system from collapsing into any one skin. A desktop-looking website is not Choir. A feed is not Choir. A podcast app is not Choir. The substrate is the NixOS MicroVM / Go multiagent platform with platform-level microservices, vtexts, appagents, citations, provenance, rollback, and publication boundaries. The surfaces are projections.

For now, the automatic newspaper can live inside the web desktop because the transition from reading to acting must be smooth. The anonymous user can browse the public graph. The registered user gets a forked computer. The published object can travel back into the newspaper. The same artifact can later become radio.

!! Mosiah as bridge

Mosiah.org/TiddlyWiki is a working bridge, not the destination. It proves the need for a public artifact graph, readable vtexts, source tiddlers, article indexes, and agent-readable exports. But the eventual replacement is not a better TiddlyWiki theme. It is Choir itself: the automatic newspaper running on the same substrate as the personal automatic computers and automatic radio.

This is the sharper topology: read the newspaper, touch the artifact, become a computer; publish from the computer, enter the newspaper; listen to the newspaper, steer the computer by radio.