Docs

Process should survive memory, turnover, and sleep deprivation.

This section holds the operational side of GameCult: how publishing works, how the root site is structured, and how Bifrost is being built without turning studio governance into an occult spreadsheet ritual.

GameCult

Process should survive memory, turnover, and sleep deprivation.

Site Architecture

1 min read

The new root site is split in two:

  • GameCult/ holds the content
  • quartz-site/ holds the vendored Quartz implementation and site-specific code

That mirrors what already works in AetheriaLore, where the content and the presentation layer are clearly separated.

The root site is intentionally not the same thing as aetheria.gamecult.org. The root should explain the studio and point readers toward projects. The Aetheria subsite should remain the denser home for lore, stories, and Aetheria-specific publishing as its structure evolves.

Architecture Writing

Longer architecture notes belong in GameCult/Blog/ when they are public-facing essays, and in GameCult/Docs/ when they are operational documentation. Current daemon architecture doctrine is published as The Eve MultiVerse And The Daemon Architecture That Refuses To Lie: CultCache .cc state, CultMesh Verse visibility, Eve GUI/TUI DSL, and Odin discovery as the shared GameCult daemon contract.

Backlinks