Agent OS for on-chain composition
A technical outline of the Orpheus coordination layer: routing, session state, Hermes integration surface, and DAO-governed expansion.
Abstract
Orpheus DAO proposes a conductor-centric control plane above heterogeneous AI agents. Builders pin composers, set channel faders, and observe harmony metrics while agents execute specialized movements. The system is designed for future Hermes-backed research flows, read-only chain awareness, and community-governed module additions.
Architecture
Presentation layer
Static HTML/CSS/JS surfaces — index marketing, Conductor cockpit, and resource pages — share design tokens and injected chrome via a single UI module.
Session layer
The Conductor maintains ephemeral session state: pinned agent, fader levels, mute/solo matrix, knob parameters, preset profiles, and a capped live log. Production deployments would persist sessions to backend storage; the demo simulates telemetry client-side.
Agent registry
Each agent exposes identity (id), display name, role, default fader, and routing hints. The registry is the contract future marketplace modules must implement.
A weighted signal across agent consensus, throughput, and uptime — intended as a governance input for Symphony DAO proposals, not a trading indicator.
Integrations
- Hermes / Nous Research — research indexing and synthesis passes.
- On-chain read — observability of protocol, token, and DAO events without autonomous signing.
- Marketplace (future) — summon, rent, and compose third-party agent workflows.
Roadmap
- Phase 0 — Public static demo and Conductor UX (current).
- Phase 1 — Authenticated sessions, real agent backends, Hermes routing.
- Phase 2 — Symphony DAO proposals tied to registry changes.
- Phase 3 — Builder marketplace and community agent curation.
Disclaimer
Orpheus DAO is experimental infrastructure. This document does not constitute an offer, investment advice, or a guarantee of token issuance.