untaped-orchestration 0.1.0

Git-native typed orchestration for repository tasks and decisions.

untaped-orchestration

untaped-orchestration is a standalone Python 3.14 CLI for Git-native, typed repository tasks and decisions. Canonical state is reviewable text under .untaped/orchestration/; agents use bounded queries and guarded mutations instead of loading or rewriting the store directly.

Status: the 0.1.0 implementation is complete. Package-index availability is the source of truth for installable releases; this document does not infer publication state from the repository contents.

Install

For the released package:

uv tool install untaped-orchestration

To evaluate the current source directly:

uv tool install 'git+https://github.com/alexisbeaulieu97/untaped-orchestration.git'

Run untaped-orchestration --help for the command tree. The safest agent entry point in an existing store is:

untaped-orchestration brief --format json

Allocate a caller-stable ID before an initialization or create operation, and reuse it on every retry:

STORE_ID="$(untaped-orchestration id new store --format raw)"
untaped-orchestration init . --store-id "$STORE_ID" --name Example --timezone UTC

Source package acceptance

The default local suite stays offline: it builds a fresh wheel and sdist in a temporary artifact directory outside dist/, audits their metadata and contents, and reports exactly one explicit dependency-resolving install skip. PR CI sets UNTAPED_ISOLATED_WHEEL_TEST=1 so that skipped test installs the exact fresh wheel with its real dependencies into a clean external virtual environment and runs the console/store smoke. No checkout or development site-packages path is injected into that environment.

Documentation

• CLI and output contracts
• Canonical file format
• Diagnostics and recovery
• Authoritative v1 design
• SDK plugin guide
• Contributing and security reporting

Privacy and federation

Public stores are decision-only in v1. Tasks remain in a private task-capable store. The explicit federation registry is registry.toml; the tool never discovers nearby repositories implicitly. Partial-tolerant reads report incompleteness, while readiness, delivery, and structural mutations fail closed.

Release and self-adoption gate

Release publication and self-adoption are separate gates. Self-adoption may begin only after untaped-orchestration==0.1.0 is published, its fresh uvx smoke passes, and Alexis gives separate approval. Adoption uses the exact released pin in its own reviewed PR.

Fleet rollout is staged: dry-run pilot, content cohort, empty-store cohort, and the private hub last. Every repository receives one separately reviewed adoption PR. See CLI and output contracts for the exact gates.