Browse Docs pages
🏛️ Architecture & Philosophy
Welcome to the Bash-Native Necropolis.
Rotkeeper operates under a brutal, unapologetic philosophy: No frameworks. No hydration. Just bones. It is not a stepping stone to a modern Javascript framework. It is the final destination for content that must survive the test of time. It relies entirely on Unix philosophies, Bash orchestration, and Oliver compilation.
Rotkeeper is permanently composed of Four Core Pillars, all native to the system and designed to outlive the web as we know it.
The Four Pillars
1. The Vault (State & Assets)
The Vault manages the integrity and history of the project. It handles micro-version logging, state auditing, and asset tracking.
- Key Rituals:
rc-bump.sh,rc-scan.sh,rc-assets.sh - Purpose: Ensure that the project's history is perfectly committed and that every asset is checksum-verified.
2. The Forge (Render)
The Forge is the burning heart of Rotkeeper. It uses Oliver to convert Markdown tombs into static HTML.
- Key Rituals:
rc-render.sh - Purpose: Translate semantic, flat-file Markdown into reading-optimized web pages without a single byte of unnecessary JavaScript. Oliver is the primary native compiler golem. Do not attempt to replace the Forge with Node, NPM, Astro, or any other modern compiler framework.
3. The Courier (Archive)
The Courier guarantees that your words can travel securely through time and space. It packages both raw content and rendered outputs into highly portable .tar.gz tombs.
- Key Rituals:
rc-pack.sh,rc-release.sh - Purpose: Create versioned backups and shareable distribution zips that can be stored offline or handed to collaborators.
4. The Receiver (Ingest & Glue)
The Receiver allows Rotkeeper to act as a decentralized communications node. It unpacks payloads from external sources and dynamically weaves them into the site's navigation.
- Data Principle: All content is local Markdown chosen by user-configured layout. Rotkeeper does not operate as an ingestion channel for incoming data.