zenmemes
Zenmemes keeps its public state in Git and builds the site's pages from it. These docs are rendered from the same repository.
Each entry below shows the path of the file it is rendered from, so you can read the source and propose changes.
Posts, public keys, and identity events are stored as plain-text files under records/, one file per record, in Git. The SQLite database is built from those files and can be rebuilt with ./v3 rebuild. Static HTML is built and published with ./v3 build-static.
Each member who uses browser identity has an OpenPGP key pair. The private key stays in the member's browser. The public key and fingerprint are published, and a member's signed public writes can be verified against them.
The server does not generate or store member private keys. Operator credentials and private workflow state are kept outside public/ and outside Git.
Full details: Public Architecture and Trust Model
How the Git records, the views built from them, OpenPGP identity, and private data relate.
docs/architecture/public_architecture_and_trust.md
The file format for posts and replies: one text file per post, headers then body.
docs/specs/canonical_post_record_v1.md
How themes work and how to add one.
docs/runbooks/theme_development_guide.md
The file that records a new identity: its OpenPGP public key, fingerprint, and username.
docs/specs/identity_bootstrap_record_v1.md
Worked examples of extending the site, including with coding agents.
docs/examples/extension_improvement_cookbook.md
How POST /api/analyze_post stores a post's analysis and, when agent replies are enabled and the reply gates pass, posts the suggested reply as reply-agent.
docs/specs/agent_reply_one_step_analyze_publish_contract_v1.md
Commands, options, and error handling for the v3 CLI.
docs/reference/v3_cli.md
How to deploy to production, and what a shared host needs.
docs/runbooks/production_deploy.md
How to check and repair the production read model and workers.
docs/runbooks/operator_recovery.md