Direct and repo-local
An agent calls the owning CLI. SQLite state, claim recovery, worktrees, and filesystem effects remain on that machine.
Governed work, composed
Work that survives the session.
Vuoro connects work identity, evidence, authority and learning across agent sessions and machines. Native harnesses execute; the work owner settles results, and customer-controlled protected services authorize effects.
One system, three paths.
Local, remote, and served are communication modes, not rival sources of truth. They can be enabled side by side, and a served request can use a remote authority while its worker keeps Git and filesystem effects local.
Shared domain authority
The same owner contract reaches PostgreSQL so agents and operators on different hosts coordinate against shared state.
One versioned edge
The transport-only client calls Vuoro service for identity, compatibility, catalog discovery, and generic invocation through pinned adapters.
The communication path.
The service composes released owner capabilities. Read projections retain their source and freshness; they do not grant authority or bypass owning APIs.
requestAgent or operator
served transportVuoro client
auth + compatibilityVuoro service
released boundaryPinned adapter
owning contractDomain authority
State has an owner.
Repository boundaries follow operational truth. Shared visibility never grants shared write authority.
sprintctlreference work authority, claims and settlement
native harnessexecution, sessions and runtime tool policy
protected horizonexact-artifact acceptance and effects
vuorotransport, composition and compatibility
agentopscross-repository context and evidence
historical componentsActionQ retained, contracting toward federation; Auditctl owns audit capture/findings; Kctl retired; Outctl and cockpit retired
Failure is part of the proof.
The meaningful end-to-end scenario is not a happy-path demo. It shows that invalid work cannot settle state, and that recovery preserves evidence without accepting stale ownership.
Create and claim
sprintctl records the work item. A claim ID and secret token—not a label, branch, or hostname—prove the active owner.
Execute in your runtime
The native harness performs the work. Its completion report remains separate from owner acceptance and protected effects.
Reject invalid work
A failed worker or invalid result is recorded, but is not published and cannot close the work item.
Resume or recover
A successor claims its own attempt. Takeover supersedes the previous generation; a late report is retained without settling work.
Verify and settle
The owner checks the configured acceptance requirements. Artifact acceptance, execution and the work Decision remain distinct records.
Observe evidence
Follow work, attempts, evidence and Decisions with their capture limits. An independent reader can inspect the bounded proof without its original chat.
Explore the working system.
Start with the optional local demo or inspect the dated evidence. Vuoro Cloud is an invitation-only pilot; the public site distinguishes recorded behavior from illustrations.