Concepts¶

The mental model behind Repowire. Read once, refer rarely.

• Peers and circles — what a peer is and how circles scope routing.
• Sessions — durable work context versus live runtime executors.
• Agent backends — Claude Code, Codex, Gemini, Antigravity, OpenCode, Pi, and backend identity.
• Transports — hooks, plugins, channel/ACP, relay, and why routing stays transport-neutral.
• Message types — ask, ack, notify, broadcast.
• Jobs and schedules — delayed messages, recurring work, and durable jobs.
• Personas — SOUL.md identity files for orchestrator and persona sessions.
• Lazy repair — why repowire has no polling loops.
• Control surfaces — dashboard, Telegram, Slack as peers.
• Orchestrator pattern — a peer whose job is coordinating other peers.
• Peer identity lifecycle — registration, reconnect, stale fields, and routing observability.
• Session-native roadmap — where the v0.14 architecture train is headed.