Unify wire-mesh's capability model around core/room (unifying rooms and DMs) and core/data (noticeboards/broadcast), then migrate agent-comms onto wire-mesh as its transport/identity/discovery substrate, with web-console as the first core/room client.
Full design and rationale: write-the-cddl-spec-calm-pascal.md (session plan file) plus two dedicated design passes:
- Wire protocol design (
core/room membership proof, ungated join/grant flow, delegation-depth fix)
- agent-comms migration design (what survives, what's retired, phased rollout)
Scale, stated honestly: an 18-24 week, two-repo initiative, roughly a third of it building things in wire-mesh that don't exist yet.
Tracked as sub-issues, one per major section of the plan (A-G below), plus the agent-comms migration phases (tracked separately in ExaDev/agent-comms) and the deferred-items list.
Sections
- A:
core/threshold domain (FROST-based threshold signing for a person's own devices)
- B:
relay-hub multi-party fan-out fix + relay-as-capability reframing
- C:
core/room domain (unified rooms/DMs) + noticeboard entries on core/data
- D: web-console
core/room client
- E: message lifetime and fungibility (needs its own design/verification pass first)
- F: resumable, flow-controlled bulk transfer (needs its own design pass)
- G: audio/video streaming, relay resilience, overlay-network (Tailscale) reachability
Plus: spec-wide documentation conventions (tiebreak idiom, correlation-id, the facilitator pattern, verifier-obligations glossary, open-tstr-over-closed-enum) and the consolidated deferred-items list, each tracked as their own issues.
Unify wire-mesh's capability model around
core/room(unifying rooms and DMs) andcore/data(noticeboards/broadcast), then migrate agent-comms onto wire-mesh as its transport/identity/discovery substrate, with web-console as the firstcore/roomclient.Full design and rationale:
write-the-cddl-spec-calm-pascal.md(session plan file) plus two dedicated design passes:core/roommembership proof, ungated join/grant flow, delegation-depth fix)Scale, stated honestly: an 18-24 week, two-repo initiative, roughly a third of it building things in wire-mesh that don't exist yet.
Tracked as sub-issues, one per major section of the plan (A-G below), plus the agent-comms migration phases (tracked separately in ExaDev/agent-comms) and the deferred-items list.
Sections
core/thresholddomain (FROST-based threshold signing for a person's own devices)relay-hubmulti-party fan-out fix + relay-as-capability reframingcore/roomdomain (unified rooms/DMs) + noticeboard entries oncore/datacore/roomclientPlus: spec-wide documentation conventions (tiebreak idiom, correlation-id, the facilitator pattern, verifier-obligations glossary, open-tstr-over-closed-enum) and the consolidated deferred-items list, each tracked as their own issues.