Prometheus7 Research Press

Editorial Office Brief for Claude

Clone SporeOS into an inhabitable newsroom, not a newspaper-themed skin
Architecture · Handoff Document
This brief is for a Claude instance being asked to spin up the next public-facing substrate of the Prometheus7 corpus. The task is not to build "a website that looks like a newspaper." The task is to port the already-working inhabitation grammar of SporeOS from a forest into a newsroom.
By psiloceyeben · April 2026

That distinction is absolute and load-bearing. SporeOS proved that a local-first computational substrate can be rendered as a place: a world with a center, a population, walkable approach, waking semantics, persistent shapes, and a terminal grammar through which the user addresses an inhabitant. The editorial office should preserve that exact primitive while changing the substrate metaphor from botanical to civic-editorial. Where SporeOS grows a forest, the new system should operate a newspaper office. Where SporeOS has a central tree, the office should have a central editorial hub. Where SporeOS has foldtoy plants and feature agents, the office should have desks, bureaus, librarians, copy editors, witness clerks, columnists, night editors, and a press room. The core claim remains the same: computation becomes more powerful, not less, when it is made inhabitable.

The newspaper office is the correct next port because a newsroom is one of the classic human institutions for converting raw eventfulness into ordered intelligibility under time pressure. It is a routing structure for public truth. That makes it an unusually clean fit for the existing bridge and engine. The bridge already handles ingress, egress, background agents, file mutation, terminal presence, and deployable sessions. The engine already handles symbolic reduction, parameterization, compositional structure, waking, persistence, and local-first operation. A newsroom is therefore not an arbitrary theme. It is a structurally faithful public interface for what the system is already doing.


What You Are Building

You are building an inhabitable editorial office in which: the user enters a pixel newsroom rather than a pixel forest; each editorial function appears as a desk, room, bureau, or machine; walking up to an editorial organ and pressing E opens a terminal overlay; the organ speaks from its role, memory, and current state; the office can generate, revise, file, and publish articles; the office can issue daily editions, bulletins, corrections, and witness notices; and the office outputs into the existing gazette archive.

The first version does not need to solve everything. It must, however, establish the correct ontology. If the first version is treated as a generic site builder with a newspaper skin, the port has failed even if the code runs. If the first version preserves the SporeOS primitive while rendering it as a newsroom, the port has succeeded even if many desks are still hardcoded.


What This Is Not

It is not a reverse-chronological blog. It is not a CMS dashboard. It is not a glossy newspaper landing page. It is not a static site theme. It is not a "content agent" wrapper around an LLM. It is not a product-marketing shell that happens to use editorial language.

It is a civic substrate. An office with organs. A place where judgment becomes visible as workflow. An editorial metabolism built on top of the existing bridge and engine logic.


The SporeOS Mapping

The most important thing you can do is preserve the architecture while changing the skin at the correct level.

SporeOS central tree becomes the central editorial hub. The center should feel like the city desk, masthead desk, or editorial nucleus. It is the place where the office speaks as a whole.

Foldtoy plants become specialized desks, bureau stations, filing cabinets, and terminals. These are directly addressable local tools and specialist organs.

User-feature agents become rooms or desks with named editorial responsibilities. These are larger, more active organs built from multiple capabilities.

Ensouled agents become columnists, correspondents, and named staff. Optional, distinct, more character-like presences.

Forest floor becomes the newsroom floor plan. Corridors, room adjacency, telegraph lines, print room, archive stacks, copy desks.

Press E to wake becomes press E to address a desk. Do not lose this grammar.

SkinDescriptor becomes IssueDescriptor or OfficeDescriptor. A descriptor that themes the office as morning edition, late city edition, Sunday review, or special bulletin.

/grow becomes /assign, /open-desk, or /commission. New editorial organs can be created through commands.

The core rule is this: preserve the underlying primitive, but let every visible noun belong to the newsroom rather than the forest.


Minimum Viable Newsroom

The first working office should contain at least these spaces: Lobby / Newsstand (entry space, routes user inward), City Desk (the central desk, equivalent of the central tree), Witness Bureau (tracks deployment evidence, field notes), Ledger Room (classifies claims as shipped, observed, building, or horizon), Lexicon Office (guards terms and canonical definitions), Archive / Morgue (browse prior issues and article inventory), Copy Desk (turns notes into publishable copy), and Press Room (handles issue generation and export to the gazette archive).

Everything beyond these rooms is expansion, not foundation.


Daily Cadence

The newsroom should be designed from the start for recurrence, even if the first version publishes only on demand. Required edition types: Morning Edition, Late City Edition, Field Circular, Correction Notice, Sunday Review, and Special Bulletin. The office should understand that not every day deserves the same size of artifact. Some days produce a brief. Some produce a feature. Some produce a correction. Some produce only a witness note.


Relationship to the Existing Gazette

The newsroom is not replacing the gazette. It is becoming the operative backend-like public institution that writes into it. The gazette is the public paper. The office is the living institution that produces the paper.


Architectural Non-Negotiables

These should be treated as hard constraints: local-first bridge structure; walkable spatial UI; waking semantics (desks wake when approached, not as always-open menus); terminal grammar (the terminal is not optional); public spectator mode; output to files (articles become files in the archive, not transient chat); status discipline (shipped, observed, building, horizon); and no generic SaaS drift.


Success Criterion for Version One

Version one is successful if all of the following are true: there is a new editorial_office/ runtime cloned from SporeOS structure; the main scene is a newsroom, not a forest; at least six named desks or rooms exist and are addressable; terminal interaction works from the desks; one article can be generated and written into the gazette archive; one issue or bulletin can be emitted; and spectator/gallery mode still works.

The decisive public claim is not "we made a cool newspaper UI." It is "we ported the inhabitation primitive from a forest to a newsroom and made editorial cognition spatial, local, and operable."