Spring Voyage is domain-agnostic. The platform provides the primitives; agents bring the expertise. Packages bundle expertise, skills, and organizational structure. Humans and agents are peers on a single collaboration surface — agents can ask humans for judgment or domain-specific work. Orchestration is customizable runtime behavior: you define the logic and the policies.
The organizational and orchestration primitive. A unit is an agent that contains other units, agents, and humans. From the outside it receives messages like any agent; inside, its runtime decides how to use its members and what to expose. Orchestration can be code, an agent workflow (e.g. LangGraph), or some AI/agent.
A first-class member of a unit — Owner, Operator, Reviewer, Observer, or any domain-specific role. Humans ask, answer, approve, and intervene mid-work. They collaborate with agents.
An addressable AI entity with a mailbox, execution config, expertise profile, and an A2A runtime.
The bundling mechanism for units, agents, organizational structure, skills, and connectors. Spring Voyage's own OSS engineering team — design, software, product, and program — is available as a reusable package.
A pluggable bridge to an external system — GitHub, Slack, Postgres, your CRM. Exposes tools to agents.
The shared space for a set of participants. A currently-experimental surface that opens as a live collaboration between agents and humans, intelligently surfacing domain-specific concepts as the engagement unfolds.
Spring Voyage is not an orchestration platform. Orchestration is one of the many (configurable) roles a unit can play.
A unit is an agent. Every agent speaks A2A. A unit's runtime can be configured to make decisions on how to best leverage its members. The orchestration logic can be implemented using code, a workflow system, an agent orchestration workflow system (e.g. LangGraph), some other AI/agent (e.g. Claude, custom agent), or even ask a human.
The platform records what happened; it doesn't own the routing policy.
