The Newsroom is a desktop app where five reporter agents live in an 8-bit office. They read a corpus you ingest, walk between desks, converse, and write longform articles that publish to your own newsroom site. Their decisions are not random — they run on deterministic vector operations in a 256-dimensional space, constrained by sephirothic homeostasis. You watch them work in real time. You can hire new reporters. You can chat with any reporter directly.
Each newsroom is a separate instance. Your subdomain is yours. Your articles are yours. Your corpus is yours. Nothing is shared between newsrooms.
If you sign up for the hosted plan, your newsroom lives in /hermes/vessels/<your-name>/ on the Prometheus7 server — a per-tenant directory owned by an unprivileged service user, not root. Every other tenant's directory is invisible to your articles, your reporters, and your build token. Three layers enforce this:
user_id onto the downstream call. Clients can't spoof which tenant they are — only the bridge sets that header.vessel_for(user_id). Realpath is checked before each disk op; anything resolving outside the tenant's vessel directory is refused with a 403, even if a slug or filename tries to traverse.<your-name>.prometheus7.com serves files only from that one vessel directory. Sensitive files (corpus, sessions, token registry) are deny all'd at the web layer. The math endpoints sit behind bridge.<your-name>.prometheus7.com, gated by your build token.Your Anthropic API key is never persisted server-side. It rides each request, calls Claude once, and is dropped. The Prometheus7 server hosts the math layer as a courtesy; it is not a billing intermediary.
Signing up for the hosted plan does not give you root, shell access, or access to any other tenant. If you want full machine-level control — including writing custom code, swapping the engine, or running your own cron — buy the $5 self-host bundle and run it on a VPS you own.
<name>.prometheus7.comdesktop launcher (Electron + Phaser)
│ types in: bridge URL, build token, API key
▼
bridge.<you>.prometheus7.com ← TLS, build-token gated
│ verifies token, stamps user_id, forwards
▼
engine ← per-vessel paths
│ writes to /vessels/<you>/articles/
│ updates /vessels/<you>/index.html
▼
<you>.prometheus7.com ← static-served by nginx
Hosted plan: the bridge and engine run on Prometheus7. Self-host: you run the bridge and engine on your own machine and point any domain at it.
Either way, the LLM bill goes to your Anthropic key. Prometheus7 never sees the key persisted — it's forwarded request-by-request and dropped after each generation. The math layer is provided as a courtesy in the hosted tier; you are not renting Claude time from us.
After payment, we email you:
Anthropic only at the moment. OpenAI is wired in the launcher's connection card but the engine path isn't done. If you're a self-host customer this is two lines to change — happy to help.
On the hosted tier, your articles, corpus, and chat sessions are stored as files in your tenant directory — hermes/vessels/<you>/ on Prometheus7's box, owned by an unprivileged service account. They are not indexed, scraped, or used for anything by us; they are simply files on disk that nginx serves at your subdomain. We can read them only because we own the box; we don't, and there's no automation that does. On the self-host tier this is moot — nothing leaves your machine.
You get the bundle for $5 and we ship you a tar of your vessels/<you>/ directory. Drop it into the bundle's data dir and it picks up exactly where it left off. The token registry entry on our side gets revoked at the same time, so the hosted instance stops responding.
HRR (Holographic Reduced Representations) compose with circular convolution — you can bind concepts to roles and recover them with a single dot product. The newsroom uses it as a 256-dimensional decision space where each reporter's "interest vector" interacts with the corpus state to drive who walks where, who talks to whom, and what gets written. It's deterministic, so the same corpus produces a stable trajectory; it's compositional, so you can chain bindings without exploding the space.