Memos Index

This directory holds short idea notes, seeds, and design prompts that are not yet mature enough to become proposals, requirements, or stories.

Current Memos

• Bad Actor Detection and Exclusion - Nodes may use consensus to detect and flag bad actors so they can be excluded from communication or subjected to temporary penalties.
• Client simplicity - Node client should be simple and easy to install and run. User should be able to download it, specify I/O, CPU/GPU and memory limits (or rely on sensible defaults), and run it. It should have UX of ICQ or Seti@Home in that matter.
• community-pool-disbursement.v1 invariants - community-pool-disbursement.v1 is the smallest policy-facing record for one community-pool outflow in the host-ledger rail.
• Console Participant Identity Create and Import - Based on:
• Deferred UI Interaction Broker - This memo captures one likely missing local contract for Orbiplex Node: a node-attached middleware module or other attached role may need user interaction without blocking the whole node communication path.
• emergency-activation.v1 invariants - emergency-activation.v1 is the smallest machine-readable seed for the activation decision layered over an existing exception-record.v1.
• emergency-signal.v1 invariants - emergency-signal.v1 is the smallest machine-readable seed for one signal entering the emergency evaluation pipeline.
• exception-record.v1 invariants - exception-record.v1 is the smallest machine-readable seed for the full exception record required by EXCEPTION-POLICY.
• Filtrum - Filtrum is a component that selects and prioritizes content for a user based on their preferences, declared goals, personal characteristics, and current condition.
• Human Expertise Escalation - A node operator may declare one or more human specializations inside node software, e.g. law, medicine, networking, accounting, or a narrow local domain.
• Requesting models - The swarm protocol should allow requests to specify checksums of models that must and/or must not be used.
• Networking Signing Conformance Vectors - Memo
• Optional Auth-Token Header Protection for Node-Attached HTTP Middleware - This memo captures one narrow hardening option for Node-attached middleware that communicates over local HTTP.
• Node Identity Layering and Upgrade Path - This memo captures one architectural direction for Orbiplex Node identity:
• Node Middleware Init and Capability Reporting - This memo captures one missing extension-host contract for Orbiplex Node: middleware modules should not remain opaque after startup.
• Node UI: HTMX and HATEOAS Web Client Architecture - Based on:
• Nym-Authored Payload Verification - Memo
• Nym Layer Roadmap and Revocable Anonymity - Memo
• Operator Participation in Answer-Channel Debate - A node that participates in a question debate may notify its operator that a live discussion is underway and that human input could materially improve the outcome.
• Operator Proxy and Co-Regulation Channel - A node may act as an external-facing front-end for its human operator: not only filtering inbound signals, but representing the operator in outbound dialogue with other nodes representing other operators.
• Orbiplex Anon - Orbiplex Anon could be a separate privacy and relay module for Node-attached traffic that wants stronger sender obscurity than the default transport path provides.
• Orbiplex Monus - Orbiplex Monus could be a Node-attached wellbeing and tension-observation module whose job is to notice signals important to a given user, weigh them over time, and optionally formulate candidate Whisper rumors from them.
• Orbiplex Whisper - Orbiplex Whisper could be a privacy-bounded social signal exchange layer attached to the Node.
• Participant Assurance Levels - Based on:
• Participant Seed Contract v1 - Based on:
• Pod-Backed Thin Clients - Portable-device and desktop clients do not need to run a local language model at all if they are primarily interfaces to a node that exposes a pod module.
• Reputation Signal v1 Invariants - reputation-signal.v1 is a small append-only fact record. The schema captures the portable shape; this note freezes the invariant card that strict consumers should enforce on ingest.
• Seed Directory HTTP Examples - Based on:
• Service Order to Procurement Bridge - Based on:
• settlement-policy-disclosure.v1 invariants - settlement-policy-disclosure.v1 is the smallest append-only audit artifact for operator-facing disclosure events affecting settlement policies in the host-ledger rail.
• Story 006 Settlement Rail Sprint 3 - Based on:
• Swarm Broadcast Assistance - A node user may open a communication window to the swarm as a whole and broadcast an issue that matters to them, such as a personal problem, a technical blockage, a safety concern, or a request for orientation.
• Swarm Communication Exposure Modes - A user opening communication with the swarm should be able to choose the exposure level of the request instead of treating all requests as equally visible.
• Swarm Question Channel Transports - Question envelopes and answer-channel conversation likely should not be forced onto one transport. The protocol shape naturally splits into two concerns:
• Transcription Monitors and Public Vaults - The swarm may include nodes that specialize in watching for valuable discussions and turning them into source transcripts. These nodes are not primary participants in every debate; they act as cultural monitors and transcription agents.
• Node Capability Advertisement - Nodes should expose their capabilities to other nodes using hierarchical keyword prefixes, e.g., :solve/math, :write/poetry, :control/camera, :store/memory.

Promotion Rule

Each memo should remain short. When an idea gains stable semantics, explicit actors, or implementation pressure, promote it into one of the following:

• doc/project/30-stories/ for user-facing scenarios,
• doc/project/40-proposals/ for architectural direction,
• doc/project/50-requirements/ for concrete system requirements,
• doc/normative/50-constitutional-ops/ if it becomes normative.