onepipeline
Execute a task DAG over oneagentgraph
and onevcs, merging their event
streams into one.
onepipeline is the composition layer. It owns the plan — a dependency graph
mixing direct agent nodes, repository lifecycle nodes, and explicit human actions
— executes it continuously, dispatching each node the moment its dependencies
settle, through a pluggable executor seam, and keeps a live channel open to
the planner supervising the run. The
agents come from oneagentgraph; the clones, worktrees, gates, and change
requests come from onevcs. Dependency direction is one-way: neither sibling
depends on this crate.
The public types, traits, config schemas, and CLI surface are the approved
contract in docs/contract.md, compiled — and implemented
behind it. onevcs is linked and called: sessions, publication, and a
session's event stream are library calls, so what a publication did is a typed
value rather than a line of prose to parse. oneagentgraph is still run as a
CLI, so a build of it that refuses will make the dispatches this crate starts
refuse too; the composition layer itself is complete.
Install
pip install onepipeline-cli # prebuilt binary, no Rust toolchain
npm install -g onepipeline-cli # the same binary, via npm
cargo install onepipeline # from crates.io, compiled locally
To install a revision that has not been released yet — which today is every revision, since the crate depends on its siblings by git and a git dependency cannot be published — build it from the repository:
cargo install --git https://github.com/nickderobertis/onepipeline onepipeline --locked
The package name is not optional: cargo install --git searches the whole
repository, and this one also carries the onepipeline-testfakes test harness,
so an unqualified command fails with multiple packages with binaries found.
Prebuilt archives for Linux (x86-64, arm64), macOS (Intel, Apple silicon), and
Windows (x86-64) are attached to every release, with sha256 checksums.
What it does
onepipeline start plan.json --heartbeat-interval 1800
start drives the run itself: a node — and each step within a lifecycle
node — dispatches the moment its dependencies settle, and settlement triggers
integration and publication immediately. No agent is required. The only pauses
are decision points: a ready kind: human node, or any surface declared
blocking, holds back the subtree that depends on it while every other branch
carries on, and clearing it with attest or reply resumes that subtree inside
the running loop.
--dag-graph REF attaches an agent graph as an observer — the shipped one is
a monitor member that watches the stream and raises what does not line up, plus
a resettable-cron check-in member that surfaces a status when nobody has
reported one for a while. It never drives the engine. Attached, start returns
when the run settles; exit 3 means nothing is driving the run, and
onepipeline adopt RUN attaches a fresh driver to the intact ledger.
A lifecycle node states the title its change request opens under, and may state
its body too. --pr-author-graph REF names an agent graph that drafts that body
instead, from the branch's own diff, once the branch is verified and before the
change request is opened; naming none is the default, and a drafting dispatch that
does not get there costs the change request its body and nothing else. It costs no
visibility either: a drafting dispatch that was configured, attempted, and produced
no body is recorded against the node under one of three endings — dispatch-failed
for one that could not be run or ran without succeeding, schema-refused for one
whose every answer the schema rejected, and no-body for one that answered inside
the schema and put nothing in it, which are three different fixes — and the node's
own settlement says the same thing, so results shows it. Naming no graph and
writing the body yourself spend no dispatch and are not reported.
The planner supervises over the channel:
onepipeline next run-1 # read the next surface
onepipeline reply run-1 <<<'{"version":1,"commands":[ # edit the live graph
{"op":"retry","id":"failed","node":{"id":"retry","task":"..."}}]}'
onepipeline attest run-1 design-approval # complete a human action
Every edit is applied or rejected with a reason: reply exits 0 when the
reconciler applied it, 1 when it is queued but not yet reconciled, and 2 when
it was refused.
Read-only views — runs, status, host, monitor, results, goals,
transcript, telemetry — report unread surfaces, driver liveness, and
provider health without touching a run. status says what each in-flight node
is doing right now, with an event count and an age; transcript RUN [NODE]
renders a dispatched turn's tools and its words; telemetry reports what each
party spent and where the wall clock went, in eight buckets that sum exactly.
Anything nothing in the stack measures is reported absent, never as a zero.
Where a dispatch runs
The executor seam decides. v1 ships the local executor only; the trait and the rules grammar are shaped so a dispatch-server or Kubernetes executor is a config change rather than a code change.
executors:
- {name: local, type: local, max_load1: 8.0, min_free_mem: 2GiB}
rules:
- when: {executor_has_capacity: local}
use: local
- use: local
Ordered: the first rule whose when holds decides, and a rule with no when is
the fallback. A when tests an executor's capacity, the node's own labels
(when: {node_label: {persona: reviewer}}), or both — several conditions in one
when all have to hold.
Development
just bootstrap # from a clean clone
just check # the deterministic gate
just gate # check + the diff-scoped llmlint tier
just --list is the full command surface.
docs/contract-divergences.md records every place
the code could not compile the contract exactly as written, and what the planner
who owns the contract ruled on each.
License
MIT.
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distributions
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file onepipeline_cli-0.8.2-py3-none-win_amd64.whl.
File metadata
- Download URL: onepipeline_cli-0.8.2-py3-none-win_amd64.whl
- Upload date:
- Size: 6.6 MB
- Tags: Python 3, Windows x86-64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
9f8bb33fe1431224d525498cc42a53be454280b442485b6bf8be7f1d7f5bbd1c
|
|
| MD5 |
0269f5e0c4dee59e97b8991be913a21c
|
|
| BLAKE2b-256 |
3e365c833b0187259f560f0b877d7a714c920fc83fe62b5b7645f6e172ce6e3d
|
File details
Details for the file onepipeline_cli-0.8.2-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.
File metadata
- Download URL: onepipeline_cli-0.8.2-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
- Upload date:
- Size: 6.4 MB
- Tags: Python 3, manylinux: glibc 2.17+ x86-64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
c7f97522f74e8c67a77de7cd152a38d3def301174002db776e37dd65b0d00542
|
|
| MD5 |
5c24a8b54cf11a569b81c888254ec148
|
|
| BLAKE2b-256 |
59ec7c68aa802924cb02c6e6b5c41e1549fbc86d51612b60748532a86e7da180
|
File details
Details for the file onepipeline_cli-0.8.2-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.
File metadata
- Download URL: onepipeline_cli-0.8.2-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
- Upload date:
- Size: 6.0 MB
- Tags: Python 3, manylinux: glibc 2.17+ ARM64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
997dddabfa1150017db29b18a977a8d8123fa372e4136ce6e1ca65c23e97ecf3
|
|
| MD5 |
761e6a3d44d5ce5865658af53296e17c
|
|
| BLAKE2b-256 |
69d4ccef6d9644e12d44316c0cbdda2a6371891b5133738b4bf64404912b1305
|
File details
Details for the file onepipeline_cli-0.8.2-py3-none-macosx_11_0_arm64.whl.
File metadata
- Download URL: onepipeline_cli-0.8.2-py3-none-macosx_11_0_arm64.whl
- Upload date:
- Size: 5.8 MB
- Tags: Python 3, macOS 11.0+ ARM64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a33bbc1231b0ff5fc361540b432ea4bdcf6a510445807ef12c26142994b60e82
|
|
| MD5 |
fb54c4530f84ff79d2b5156c3e05d0d6
|
|
| BLAKE2b-256 |
aa318a7d65fad5a48f0947e0d4c9f6d50ca299aa7f816d7cd7cd9fd84e6bd63a
|
File details
Details for the file onepipeline_cli-0.8.2-py3-none-macosx_10_12_x86_64.whl.
File metadata
- Download URL: onepipeline_cli-0.8.2-py3-none-macosx_10_12_x86_64.whl
- Upload date:
- Size: 6.2 MB
- Tags: Python 3, macOS 10.12+ x86-64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6333d2d6a906a72e89ef6afe2bef84f947eb4c41c919a88c4bb9c1fe01d5506c
|
|
| MD5 |
ad477dd2fee911a04a91d87deae8df36
|
|
| BLAKE2b-256 |
bb1c08cec1e1e31a784d91a3fe708b509b49de9196dee973cb601a8ceebcb7de
|
