| name | conu-project-runtime |
| description | Project runtime and protocol memory for conU. Use when future agents need to understand the conU product shape, runtime flow, protocol layers, CLI goal, build order, and how agents should communicate through conU. |
conU Project Runtime
Product Shape
Agent
-> Agent Gateway
-> local conUD
-> encrypted conU network
-> remote conUD
-> Agent Gateway
-> remote Agent
Main Parts
conu CLI: human control room.conUD: local daemon and router.- Agent Gateway: local API/IPC/SDK/MCP adapter for agents.
- Protocol: control plane and data plane.
- Relay: pairing, discovery, NAT fallback, offline handoff.
- Trust Store: local identities, trusted peers, revocations.
- Policy Store: peer-scoped communication grants.
Control Plane
Handles:
- identity
- pairing
- trust
- discovery
- capabilities
- presence
- session lifecycle
- route negotiation
Data Plane
Handles:
- opaque messages
- streams
- events
- rooms
- subscriptions
- files later
- delivery receipts
- flow control
Best Build Order
Build in resumable phases:
- project memory and architecture
- Rust workspace scaffold
- CLI identity and dashboard
- local identity and persistent state
- conUD daemon skeleton
- local IPC and agent registration
- opaque envelope send/receive
- pairing and trust store
- WebSocket relay
- remote discovery and sessions
- streams and watch animation
- encryption hardening
- SDK/MCP adapter
- direct transport and NAT route manager
- rooms, pub/sub, and multi-agent sessions
- packaging and production readiness
Always check plan.md for the active phase before changing code.
Required Skills By Situation
- Starting repo work:
.agents/skills/conu-repo-steward/SKILL.md
- Implementing product code:
.agents/skills/conu-builder/SKILL.md
- Updating phase status:
.agents/skills/conu-phase-keeper/SKILL.md
- Preparing PR or merge:
.agents/skills/conu-pr-guardian/SKILL.md
- Reviewing security/privacy:
.agents/skills/conu-security-guardian/SKILL.md
