How Kapnet works, what LLobby does, and how to get started.
Kapnet is shared operational infrastructure for private groups. The fastest way to try it is to start a Member Room — a gated private chat with automated access, role sync, and moderation.
LLobby is the first Kapnet product. It turns group chat rooms into governed spaces with structured state — not just a message stream.
Each room is defined by a structured config file:
# kapnet room.yaml room: "#my-club" gates: - tier: "explorer" method: "invite" - tier: "builder" method: "auto" roles: moderator: permissions: ["sanction", "assign_role"] requires: "operator" member: permissions: ["send", "flag", "claim_perk"] perks: study-guide: claim_limit: "1 per member" expires: "unlimited" bridges: discord: "pending" nostr: "live"
Observe, learn, join open rooms, attend sessions, claim basic perks.
Run a project room, deploy workflows, access shared templates, request build reviews.
Contribute services, hardware, moderation, curriculum, or technical capacity to the pool.
Govern infrastructure priorities, approve policies, route external demand, share in higher-trust operating loops.
Members can contribute and draw from a shared pool of:
Kapnet uses a three-layer model:
INTERFACE Discord · Telegram · Matrix · Nostr (bridges)
↓
STATE LAYER LLobby — room config, roles, perks, moderation, audit
↓
AUTHORITY KOR — who may act, what they may do (governance substrate)
KOR (KNU Operating Register) is the authority plane — the cube that defines who may act and what they may do. Claim receipts are the subordinate work-lifecycle layer. Every state mutation passes through KOR for capability verification.
BUS (the Nostr Transport Layer) is the mesh that carries events between peers — signed Nostr events over WebSocket relay. All state transitions are emitted as BUS events and validated by peer nodes.
Kapnet state is platform-agnostic. Bridge adapters connect your rooms to:
Membership state is not locked to any one interface — it survives platform changes, bans, and migrations.