zenmemes Platform Docs

Docs home

Documents

38 documents

Filters
  1. Agent-response attribution

    Purpose: Record response kind and source/version binding within the signed post.

    docs/concepts/agent_responses.md Concepts

  2. Application update

    Purpose: Let an operator move the running application to the latest origin/main without SSH, and never leave the checkout half-updated.

    docs/concepts/application_update.md Concepts

  3. Approval acceptance

    Purpose: Preserve local acceptance facts without confusing them with member signatures.

    docs/concepts/approval_acceptance.md Concepts

  4. Calendar

    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.

    docs/concepts/calendar.md Concepts

  5. Collection selection

    Purpose: Choose the records needed by a view or job while preserving eligibility, ordering and complete-output contracts.

    docs/concepts/collection_selection.md Concepts

  6. Content snapshot export

    Purpose: Move committed public content and reusable score results through ordinary downloads.

    docs/concepts/content_snapshot_export.md Concepts

  7. Deployment configuration

    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.

    docs/concepts/deployment_configuration.md Concepts

  8. Effective tags

    Purpose: Show public tags implied by current compatible scores alongside authored tags.

    docs/concepts/effective_tags.md Concepts

  9. Fastmod scoring

    Purpose: Keep reusable advisory probabilities separate from canonical content and provider workflow state.

    docs/concepts/fastmod_scoring.md Concepts

  10. Feedback items

    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…

    docs/concepts/feedback_items.md Concepts

  11. History evidence indexing

    Purpose: Derive equivalent commit counts and relevant activity evidence without repeated large Git manifests or unused line diffs.

    docs/concepts/history_evidence_indexing.md Concepts

  12. History purge

    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…

    docs/concepts/history_purge.md Concepts

  13. Incremental source removal

    Purpose: Remove one post from the site in well under a second without rebuilding the read model.

    docs/concepts/incremental_source_removal.md Concepts

  14. Initial naming and renaming

    Purpose: Let a guest choose a name without replacing the key that owns posts and membership.

    docs/concepts/initial_naming.md Concepts

  15. Instance content import

    Purpose: Add compatible public records while preserving local authority and conflicts.

    docs/concepts/instance_content_import.md Concepts

  16. Internal task queue

    Purpose: Run allowlisted maintenance work outside visitor requests, one task at a time, with deduplication and visible status.

    docs/concepts/internal_task_queue.md Concepts

  17. Invitation lifecycle

    Purpose: Let an approved member sponsor a bounded number of distinct recipient keys through one signed bearer link.

    docs/concepts/invitation_lifecycle.md Concepts

  18. Key retirement

    Purpose: Preserve signed withdrawal of one key's future account privileges without deleting verification material.

    docs/concepts/key_retirement.md Concepts

  19. Navigation slots

    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.

    docs/concepts/navigation_slots.md Concepts

  20. Operator command progress

    Purpose: Show what a long operator command is doing while it runs, so a working command can be told from a stuck one.

    docs/concepts/operator_command_progress.md Concepts

  21. Post body formatting

    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…

    docs/concepts/post_body_formatting.md Concepts

  22. Post event metadata

    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.

    docs/concepts/post_event_metadata.md Concepts

  23. Post presentation and visibility

    Purpose: Present public contributions with existing author attribution, readable content and links to their source conversation.

    docs/concepts/post_presentation.md Concepts

  24. Post retraction and operator removal

    Purpose: Delete a post's prose from the current tree while retaining a receipt that describes the removal on its own.

    docs/concepts/post_retraction.md Concepts

  25. Private-message history

    Purpose: Let approved devices read older originals using retained encrypted access from eligible devices.

    docs/concepts/private_message_history.md Concepts

  26. Profile delivery

    Purpose: Keep profile links available while allowing operators to omit their prebuilt HTML.

    docs/concepts/profile_delivery.md Concepts

  27. Reaction record

    Purpose: Record one author adding tags to a thread (labels, likes, QDB votes) or a post (likes, flags) in one self-describing format.

    docs/concepts/reaction_record.md Concepts

  28. Derived read-model rebuild

    Purpose: Reconstruct queryable site state from canonical records and their accepted history.

    docs/concepts/read_model_rebuild.md Concepts

  29. Recent conversation

    Purpose: Let readers catch up on individual public threads and replies without technical event details.

    docs/concepts/recent_conversation.md Concepts

  30. Resource measurement

    Purpose: Associate workload, environment and recovery evidence with resource observations without turning a local sample into a host guarantee.

    docs/concepts/resource_measurement.md Concepts

  31. Shared composer

    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…

    docs/concepts/shared_composer.md Concepts

  32. Source history links

    Purpose: Let readers open the exact committed bytes of a canonical record and the commit that introduced them.

    docs/concepts/source_history_links.md Concepts

  33. Static publication

    Purpose: Publish a generated public site from the derived read model.

    docs/concepts/static_publication.md Concepts

  34. Tag browsing

    Purpose: Find threads carrying a board tag or thread label without loading the entire collection into a page.

    docs/concepts/tag_browsing.md Concepts

  35. Theme navigation icons

    Purpose: Give the Word97, Chicago and Midnight themes a 16px pixel-art glyph on each navigation destination without changing markup or server HTML.

    docs/concepts/theme_navigation_icons.md Concepts

  36. Thread title

    Purpose: Let a thread's displayed title change after creation through an ordinary reply, with the authority, provenance and visibility of that change kept expl…

    docs/concepts/thread_title.md Concepts

  37. Tools launcher

    Purpose: One list decides which tools exist, their order and their grouping, so the /tools/ page and the Tools bar inside every tool show the same tools and ne…

    docs/concepts/tools_launcher.md Concepts

  38. Viewer session

    Purpose: Remember which identity a browser signed in as, so every request from it is recognized without signing again.

    docs/concepts/viewer_session.md Concepts