vivary-exo
Release status: root release status.
exo controlis unpublished development source.
exo is the optional outer coordination layer. It has two separate surfaces:
- Legacy graph coordination reads the Tropo graph.
exo claimremains the only legacy graph write. It updates an opted-in work item'sassignee. - Governed control dispatches one bounded Core lifecycle request over caller-supplied state. The caller persists the returned projection.
Most workspaces do not need Exo. Single-agent workspaces stop at tropo + strato.
Legacy graph coordination
exo conflicts --root <workspace>
exo board --root <workspace>
exo claim local-ci-baseline --agent connie --root <workspace>
exo roles
conflicts reports active work items that share an outbound target. board groups
work items by status and declared @assignee. roles prints the bounded worker
contracts.
To enable the legacy claim field, declare it in the workspace:
packs = ["repo-graph", "coordination"]
exo claim accepts an optional leading @ in an agent handle. It refuses malformed
frontmatter, undeclared fields, and symlinked or out-of-workspace work item targets. For
a hard-linked work item, it safely replaces the workspace path without mutating the
other linked file.
Governed control
exo control REQUEST --governed [--json] [--strict]
This command sends one complete request to Core. It does not persist the request, result, claim ledger, task list, or execution log. The command reference owns the exact request envelope, operation list, runnable examples, and strict exits. The Core control contract owns lifecycle semantics.
The adapter adds no scheduler, state store, agent runner, network or provider call, MCP server, repair write, or publishing path. It makes no Agent Relay compatibility or byte-parity claim.
Local --receipt records are separate from governed state and are not telemetry. See
the receipt policy.
Requirements
Python 3.11+. Packaged builds declare the Tropo and Core dependency floors in pyproject.toml.
Website and canonical docs: https://vivary.vercel.app/
Release files for vivary-exo 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vivary_exo-0.3.0.tar.gz | 22.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vivary_exo-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.5 kB
Release files / vivary_exo-0.3.0.tar.gz
| Download URL | vivary_exo-0.3.0.tar.gz |
|---|---|
| Size | 22.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
afe7613a962978a819b6481fcf8fd0dc56b9680af5ea9cee33355af9d9c4d73e
|
|
BLAKE2b-256 checksum How to use checksums |
7b240282d523d3722a294f0ba49a34163e5cc8df574f4654e43f45e29808e85e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / vivary_exo-0.3.0-py3-none-any.whl
| Download URL | vivary_exo-0.3.0-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd0f0891d40825762e027a338854f7383e4f976fb56b42e99b4505de8b3cb686
|
|
BLAKE2b-256 checksum How to use checksums |
b82b2543ee9b07eab8f754c590397fe5fc76f883113d30cd499c12a64b88329c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|