For Prometheus7, that means preventing the corpus from being publicly reduced to any of the following weak summaries: weird mushroom coder builds AI art project; outsider genius beats labs; crypto cult object; chatbot wrapper with mystical language; one man with too many projects; elegant prose compensating for missing proof. The correct task is to preserve the actual shape of the work: a substrate-first research institute, a candidate primitive with multiple ports, a growing archive of proofs, proposals, plans, and deployments, a system in which algebra, routing, and domain engines do substantive work while language remains the final membrane.
Layer 1: Threat Model
The system should maintain a living table of bad frames and corrective frames. Bad frame: "just another local model project." Corrective: a vector-native articulation layer for an existing substrate architecture. Bad frame: "one founder, many side projects." Corrective: one program, many ports of the same primitive. Bad frame: "mysticism over engineering." Corrective: symbolic language used as routing and structural vocabulary, tied to executable systems. Bad frame: "hype beyond evidence." Corrective: clear distinction between shipped, observed, proposed, and conjectural.
Layer 2: Canonical Explanation Hierarchy
The same object must be expressible consistently at the following levels: one sentence, three sentences, one paragraph, one page, one flagship essay, one technical brief, one live demo script. These are not separate stories. They are nested resolutions of the same story.
Layer 3: Proof Ledger
Every public-facing layer should preserve four explicit statuses: shipped, observed, in active build, and conjectural / horizon. This distinction is mandatory. The archive must never allow the poetry of the horizon to overwrite the discipline of the ledger.
Layer 4: Archive Architecture
The archive should remain divided into legible districts. Foundations: primitive, foldtoys, structural papers. Systems: SporeOS, HERMES, Ensouled, SporeDec. Deployment: build plans, cooler branch, server branch, witness materials. Public Essays: institute, tongue, constraint manifold, dead objects, reply to billions. Press / Culture: front pages, interview features, magazine-style explainers. A stranger should be able to arrive and immediately understand that this is a world with districts, not a heap of files.
Layer 5: Glossary / Ontology Guardrail
The following terms require canonical definitions, anti-definitions, and common-misreading notes: substrate, fold, fixed point, letter basis, expert mode, coordinate, tongue, manifold, vessel, digital life, reality engine, returned fire, institute, and reclaiming dead objects. This glossary should eventually be a public page.
Layer 6: Audience Routing
Different audiences need different entrances. The object does not change; the doorway does. Primary audiences: technical researchers, systems builders, operators / small business owners, cultural / press readers, potential collaborators, and skeptics. Each audience should have a first page designed for them.
Layer 7: Response Layer
Maintain ready responses to common reductions. This includes: FAQ, common misreadings page, skeptical reviewer page, hostile-frame red-team notes, and short public replies for social compression events.
Layer 8: Witness Layer
The archive becomes much harder to distort once third-party reality enters it. Needed over time: second-machine install reports, screenshots and photos from real deployments, measured before/after deltas, collaborator notes, operator testimonials, replication attempts, and independent walkthroughs.
Layer 9: Asset Bank
A full defense system also needs a visual and evidentiary asset bank: canonical screenshots, installer photos, deployment photos, front-page archive art, diagrams, issue covers, and short clips or demos. Without this, outside media will select poor visuals and frame the object incorrectly.
Layer 10: Search / Discovery Layer
The corpus should be discoverable under its true categories. Needed: metadata and page titles that preserve ontology, stable descriptions for search and snippets, cross-links between technical papers and public essays, and an explicit archive map for humans and agents.
Layer 11: Editorial Constitution
The public voice must obey these rules: no claiming proof where only observation exists; no shrinking the work to a startup slogan; no letting biography outrank artifact; no letting artifact outrank evidence; no making the founder look larger by making the architecture look vaguer; no using style to hide status ambiguity.
Layer 12: Crisis Playbook
If a weak frame begins to dominate publicly, the response order should be: identify the compression error, route to the shortest truthful corrective artifact, reinforce with archive links, add witness material if available, and update the threat model for future repeats.