onepipeline-cli 0.1.1__py3-none-win_amd64.whl

onepipeline_cli-0.1.1.dist-info/METADATA

@@ -0,0 +1,126 @@
+Metadata-Version: 2.4
+Name: onepipeline-cli
+Version: 0.1.1
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Rust
+Classifier: Topic :: Software Development :: Build Tools
+License-File: LICENSE
+Summary: Execute a task DAG over oneagentgraph and onevcs, merging their event streams into one.
+Keywords: orchestration,dag,agents,cli,ndjson
+Home-Page: https://github.com/nickderobertis/onepipeline
+Author: Nick DeRobertis
+License: MIT
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
+Project-URL: Homepage, https://github.com/nickderobertis/onepipeline
+Project-URL: Repository, https://github.com/nickderobertis/onepipeline
+
+# onepipeline
+
+Execute a task DAG over [`oneagentgraph`](https://github.com/nickderobertis/oneagentgraph)
+and [`onevcs`](https://github.com/nickderobertis/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
+— schedules it in rounds, dispatches each node 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`](docs/contract.md), compiled — and implemented
+behind it. `onepipeline` composes its two siblings by running their CLIs, so a
+build of either that still refuses will make the dispatches this crate starts
+refuse too; the composition layer itself is complete.
+
+## Install
+
+```bash
+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:
+
+```bash
+cargo install --git https://github.com/nickderobertis/onepipeline --locked
+```
+
+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
+
+```bash
+onepipeline start plan.json --round-budget 14400 --heartbeat-interval 1800
+```
+
+`start` launches the run's **dag-scope agent graph** — a shipped default of an
+`orchestrator` member driving the engine, and a resettable-cron `check-in` member
+that surfaces a status when nobody has reported one for a while. Attached, it
+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.
+
+The planner supervises over the channel:
+
+```bash
+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`,
+`telemetry` — report unread surfaces, driver liveness, and provider health
+without touching a run.
+
+## Where a dispatch runs
+
+The [executor seam](docs/contract.md) 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.
+
+```yaml
+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
+
+```bash
+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`](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.
+

onepipeline_cli-0.1.1.dist-info/RECORD

@@ -0,0 +1,6 @@
+onepipeline_cli-0.1.1.data/scripts/onepipeline.exe,sha256=TVpm5-_tEN5JfoFZ0o_Ovw04agwrmRpjuc_pVk-mEHM,2862592
+onepipeline_cli-0.1.1.dist-info/METADATA,sha256=J9FzHv_F18COLWDHIPW2pB37iT8XcAlmWRTZyw8yWw4,4930
+onepipeline_cli-0.1.1.dist-info/WHEEL,sha256=2zDlIYIdD4m4N3p5DVEG3iJhGLdhsBQgdH-FqVkAur8,94
+onepipeline_cli-0.1.1.dist-info/licenses/LICENSE,sha256=JeBGdcXIUkoTZEHhkKd-FmKgdgumkH509Ob1QWJomVE,1072
+onepipeline_cli-0.1.1.dist-info/sboms/onepipeline.cyclonedx.json,sha256=dtUhe1_vbj8ZwgQFWMV9pU8Uf1Ej-ipjoEXn6iU4c6c,80202
+onepipeline_cli-0.1.1.dist-info/RECORD,,

onepipeline_cli-0.1.1.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: maturin (1.14.1)
+Root-Is-Purelib: false
+Tag: py3-none-win_amd64

onepipeline_cli-0.1.1.dist-info/licenses/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Nick DeRobertis
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.