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.
2,515 documents
Search unavailable. or refresh the library.
Turn new site feedback into proposed changes to feedback items, show them for review, then write the accepted ones.
Procedures for agents working on this project: follow the one that matches the task.
Take a ZenMemes thread that asks for a change, build it, open a pull request, and reply in the thread with the result.
Use this guide to propose a new site profile before implementation.
Private messaging provides encrypted, signed text conversations between approved forum users.
How the Git records, the views built from them, OpenPGP identity, and private data relate.
Purpose: Record response kind and source/version binding within the signed post.
Purpose: Let an operator move the running application to the latest origin/main without SSH, and never leave the checkout half-updated.
Purpose: Preserve local acceptance facts without confusing them with member signatures.
Purpose: Show event threads by day so members can see what is on, offer a day, and tell which days are settled, without a record family of its own.
Purpose: Choose the records needed by a view or job while preserving eligibility, ordering and complete-output contracts.
Purpose: Move committed public content and reusable score results through ordinary downloads.
Purpose: Give one deployment a single, persistent answer to "which site is this and where is its data" for the web app, CLI, cron and cache workers.
Purpose: Show public tags implied by current compatible scores alongside authored tags.
Purpose: Keep reusable advisory probabilities separate from canonical content and provider workflow state.
Purpose: Keep each requested outcome from site feedback as one file with a permanent ID, kind, workflow state and sources, so its status can change and be refe…
Purpose: Derive equivalent commit counts and relevant activity evidence without repeated large Git manifests or unused line diffs.
Purpose: Remove retracted or operator-deleted prose from the repository's Git history on the server, deliberately and in batches, while keeping receipts and ol…
Purpose: Remove one post from the site in well under a second without rebuilding the read model.
Purpose: Let a guest choose a name without replacing the key that owns posts and membership.
Purpose: Add compatible public records while preserving local authority and conflicts.
Purpose: Run allowlisted maintenance work outside visitor requests, one task at a time, with deduplication and visible status.
Purpose: Let an approved member sponsor a bounded number of distinct recipient keys through one signed bearer link.
Purpose: Preserve signed withdrawal of one key's future account privileges without deleting verification material.
Purpose: Keep the phone tab bar short while giving each reader one-tap access to the destinations they use most, without the server knowing anything about them.
Purpose: Show what a long operator command is doing while it runs, so a working command can be told from a stuck one.
Purpose: Let each post say whether its body is Markdown or plain text, so structured posts read well while text written without Markdown in mind is never reint…
Purpose: Let a thread root describe an event (when, until, where, link) in its own record, so event pages, the event block and the calendar all read one source.
Purpose: Present public contributions with existing author attribution, readable content and links to their source conversation.
Purpose: Delete a post's prose from the current tree while retaining a receipt that describes the removal on its own.
Purpose: Let approved devices read older originals using retained encrypted access from eligible devices.
Purpose: Keep profile links available while allowing operators to omit their prebuilt HTML.
Purpose: Record one author adding tags to a thread (labels, likes, QDB votes) or a post (likes, flags) in one self-describing format.
Purpose: Reconstruct queryable site state from canonical records and their accepted history.
Purpose: Let readers catch up on individual public threads and replies without technical event details.
Purpose: Associate workload, environment and recovery evidence with resource observations without turning a local sample into a host guarantee.
Purpose: One partial renders every writing form (new post, compact board and QDB add, reply) so field names, signing, drafts, Outbox and attachments behave the…
Purpose: Let readers open the exact committed bytes of a canonical record and the commit that introduced them.
Purpose: Publish a generated public site from the derived read model.
Purpose: Find threads carrying a board tag or thread label without loading the entire collection into a page.
No documents found.