ota

KO | EN

gitlite — search

#php #javascript #unmaintained #python #dotfiles #ruby #abandoned #theme #erlang #java #objective-c #opendata

★ 71 Open GitHub ↗

One contract for execution governance across every stack, every team, and every AI agent.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<div align="center">
  <img src="https://res.cloudinary.com/ota-run/image/upload/q_auto/dpr_auto/63eb48c4-6148-40a0-8164-34505504414e.png" alt="ota logo" width="110" height="110" />
  <h1>ota</h1>
  <p><strong>Built for humans, CI, and AI agents, containers, and multi-repo workspaces.</strong></p>
  <p><strong>DOCTOR FIRST. CONTRACT SECOND.</strong></p>




      <p>
        <img src="https://ota.run/brand/ota-github-social-card.png" alt="ota social card" width="100%" />
      </p>
  <p>
    <a href="https://github.com/ota-run/ota/actions/workflows/release-gate.yml"><img src="https://img.shields.io/github/actions/workflow/status/ota-run/ota/release-gate.yml?branch=main&style=for-the-badge&label=release%20gate&labelColor=111827&logo=githubactions" alt="Release gate status" /></a>
    <a href="https://github.com/ota-run/ota/actions/workflows/docs-quality.yml"><img src="https://img.shields.io/github/actions/workflow/status/ota-run/ota/docs-quality.yml?branch=main&style=for-the-badge&label=docs&labelColor=111827&logo=readthedocs" alt="Docs quality status" /></a>
    <a href="https://github.com/ota-run/ota/actions/workflows/codeql.yml"><img src="https://img.shields.io/github/actions/workflow/status/ota-run/ota/codeql.yml?branch=main&style=for-the-badge&label=codeql&labelColor=111827&logo=github" alt="CodeQL status" /></a>
    <a href="LICENSE"><img src="https://img.shields.io/github/license/ota-run/ota?style=for-the-badge&label=license&labelColor=111827&logo=apache" alt="License" /></a>

  </p>
  <p>
    <a href="https://github.com/ota-run/ota/releases"><img src="https://img.shields.io/github/v/release/ota-run/ota?style=for-the-badge&label=release&labelColor=111827&color=2563eb&logo=github" alt="Latest release" /></a>
  </p>
  <p>
    <a href="https://ota.run/docs/getting-started">Get Started</a> ·
    <a href="https://ota.run/docs">Docs</a> ·
    <a href="https://ota.run/docs/reference">Reference</a> ·
    <a href="https://ota.run/blogs">Blogs</a>
  </p>
  <p>
    <a href="https://ota.run/docs/install">Install</a> ·
    <a href="https://ota.run/docs/quickstart">Quickstart</a> ·
    <a href="docs/adoption/examples-by-goal.md">Examples by Goal</a> ·
    <a href="https://github.com/ota-run/examples">Examples</a> ·
    <a href="https://ota.run/docs/reference/governance">Governance</a> ·
    <a href="https://github.com/ota-run/ota/releases">Releases</a>
  </p>
  <p>
    <a href="https://discord.gg/45mBMzSkKC">Discord</a> ·
    <a href="https://x.com/otaready">X (Twitter)</a>
  </p>
</div>

---

## One explicit contract for execution governance

Most repos fail the same way:

- setup is split across README prose, shell scripts, manifests, and tribal knowledge
- contributors guess which runtimes, tools, versions, and task order the repo actually needs
- local, CI, and container workflows drift apart
- AI agents see partial guidance and make unsafe assumptions
- diagnosis starts after the repo already feels broken

ota is not another task runner or package manager. It gives every repo one explicit contract for
execution governance: what it needs, how it is diagnosed, how it is prepared, and how tasks run, so
humans and AI agents can answer why a repo is or is not runnable without guesswork.

ota fixes that by making readiness explicit and machine-readable:

- `ota doctor` shows what is missing and the next safe step
- `ota validate` keeps the contract honest before humans, CI, or agents rely on it
- `ota init` writes a starter contract when the repo needs one
- `ota up` prepares the repo from the contract instead of from guesswork
- `ota run` executes declared work through the same contract every time
- `ota detect` turns repo signals into a contract you can review when you are authoring or refining the file

The result is a repo that is easier to trust, easier to onboard, and easier to operate across
humans, CI, containers, and AI agents.

## Installation

Install the latest release binary:

```bash
curl -fsSL https://dist.ota.run/install.sh | sh
```

When the installer runs inside GitHub Actions, it now exports the resolved ota bin directory to
`GITHUB_PATH` automatically so later workflow steps can call `ota` without hand-written path glue.

Persist the install directory on `PATH` explicitly:

```bash
curl -fsSL https://dist.ota.run/install.sh | sh -s -- --setup-path
```

Windows PowerShell:

```powershell
irm https://dist.ota.run/install.ps1 | iex
```

When the PowerShell installer runs inside GitHub Actions, it now appends the resolved ota bin
directory to `GITHUB_PATH` automatically, including the Windows `%LOCALAPPDATA%\\ota\\bin` path.

Persist the Windows install directory on `PATH` explicitly:

```powershell
& ([scriptblock]::Create((irm https://dist.ota.run/install.ps1))) -SetupPath
```

Install the optional Ota skill after `ota` is installed:

```bash
npx skills add ota-run/skills --full-depth
```

Windows Git Bash, MSYS, MinGW, or Cygwin:

```bash
curl -fsSL https://dist.ota.run/install.sh | sh
```

If the existing `ota.exe` is locked, the shell installer stages the replacement and reports it as pending instead of leaking a file-in-use error.

Prebuilt release binaries are published for:

- Linux `x86_64-unknown-linux-gnu`, `aarch64-unknown-linux-gnu`
- macOS `x86_64-apple-darwin`, `aarch64-apple-darwin`
- Windows `x86_64-pc-windows-msvc`, `aarch64-pc-windows-msvc`

Pin a release:

```bash
curl -fsSL https://dist.ota.run/install.sh | OTA_VERSION=vX.Y.Z sh
```

Track an unreleased branch tip during active pressure testing:

```bash
curl -fsSL https://dist.ota.run/install.sh | OTA_GIT_BRANCH=branch-name sh -s -- --from-git
```

When a repo contract declares `agent.bootstrap.ota.source`, the canonical installer mapping is:

- `kind: version` -> `OTA_VERSION=<version>` on the release installer lane
- `kind: git_rev` -> `OTA_GIT_REV=<rev>` plus `--from-git`
- `kind: branch` -> `OTA_GIT_BRANCH=<branch>` plus `--from-git`

That same mapping is what `ota-run/setup@v1` and `ota-run/action@v1` consume in
`source: contract` mode, and it is the mapping agents should follow when a contract is the first
thing they see.

Windows PowerShell:

```powershell
$env:OTA_VERSION = "vX.Y.Z"
irm https://dist.ota.run/install.ps1 | iex
```

Active pressure testing from a branch tip:

```powershell
$env:OTA_GIT_BRANCH = "branch-name"
& ([scriptblock]::Create((irm https://dist.ota.run/install.ps1))) -FromGit
```

Update an existing install:

```bash
ota upgrade
```

Install from a local checkout:

```bash
./scripts/install.sh --from-source
```

Persist the source-install binary directory on `PATH` explicitly:

```bash
./scripts/install.sh --from-source --setup-path
```

Windows PowerShell:

```powershell
powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1 -FromSource
```

Persist the source-install binary directory on `PATH` explicitly:

```powershell
powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1 -FromSource -SetupPath
```

See [Install](https://ota.run/docs/install) for the public install path and
[docs/installation.md](docs/installation.md) for repo-local mirror/CDN and source fallback details.

## Quickstart

Choose the path that matches the repo.

### Existing repo with `ota.yaml`

Start with the read path:

```bash
ota doctor
ota explain
ota up
ota run <task>
ota receipt
```

This path tells you what is wrong, turns the findings into an ordered plan, prepares the repo,
gives you one declared task path without guessing, and captures the resulting repo state as a
reviewable artifact.

If the repo is meant to run inside a container, use:

```bash
ota doctor --mode container
```

If you are not sure which task to run after `ota up`, use:

```bash
ota tasks --use
```

Keep workflow-local env inputs declarative. Use `tasks.<name>.env_files` for ordered dotenv
overlays owned by one task path, and use native `action` tasks such as `copy_if_missing` or
`ensure_env_file` when the workflow needs deterministic local env-file bootstrap before setup. When
the selected workflow itself owns the rendered artifact, prefer `env.profiles.<name>.render.dotenv`
and add `render.dotenv.template` if the file should keep baseline example entries.

If you want repo-local agent guidance from the same contract after the core loop is working, use:

```bash
ota agents
```

## Maintainer Note

The Linux native systemd proof workflow in
[`/.github/workflows/linux-systemd-native-proof.yml`](.github/workflows/linux-systemd-native-proof.yml)
is intended for an OrbStack-backed self-hosted Linux runner labeled `linux`, `orbstack`, and
`systemd`.

That proof lane exists because GitHub-hosted Ubuntu runners are not honest host-systemd runtime
truth for `manager.host.kind: systemd` plus `readiness.kind: systemd_active`.

### Repo without `ota.yaml`

Use the authoring path first:

```bash
ota doctor
ota detect --dry-run .
ota detect --contract .
ota init --dry-run
```

Then choose one explicit write path:

```bash
ota init
```

Then continue into preparation preview:

```bash
ota up --dry-run
```

Use `ota detect --write .` when you want the detector-led authoring path instead of the starter contract path.

If you want an explicit conventional starter instead of detector-led init, use a pack:

```bash
ota init --packs
# or:
ota init --pack node
# or:
ota init --pack node --package-manager npm --dry-run
# or:
ota init --pack python --dry-run
# or:
ota init --pack python --test-runner unittest --dry-run
# or:
ota init --pack ruby --dry-run
# or:
ota init --pack go --dry-run
# or:
ota init --pack rust --dry-run
# or:
ota init --pack dotnet --dry-run
# or:
ota init --pack php-composer --dry-run
# or:
ota init --pack java-maven --dry-run
# or:
ota init --pack java-gradle --dry-run
```

The Java packs prefer `./mvnw` or `./gradlew` when the repo already ships those wrappers. When no
wrapper is present, they seed the global Maven or Gradle prerequisite explicitly.
The Node pack accepts `--package-manager npm|pnpm|yarn|bun`, and the Python pack accepts
`--test-runner pytest|unittest`.
The `php-composer` pack stays on the explicit Composer boundary and does not pretend to infer
framework-specific entrypoints or whether the repo uses phpunit, pest, artisan, or another test
wrapper unless the repo already declares `scripts.test` in `composer.json`.
If you choose the wrong explicit pack, ota can surface an advisory note and JSON `pack_advisory`
field, but it keeps the selected pack authoritative and does not auto-switch starters.

### Existing repo with `ota.yaml`, but contract drift is suspected

Review the delta before writing:

```bash
ota detect --merge --dry-run .
ota detect --rewrite --dry-run .
```

### Policy boundary review

Use the conservative policy scaffold first when a team needs a starter org policy pack:

```bash
ota policy init --dry-run
ota policy init
ota policy init --preset required-sections --dry-run
ota policy init --preset provisioning --dry-run
ota policy init --preset agent --dry-run
```

### One repo rollout story

For one repo, the repeatable local path is:

```bash
ota doctor
ota up
ota run ci
ota receipt
```

For CI, keep the same contract boundary and archive the read-only receipt:

```bash
ota validate
ota doctor --json
ota receipt --json --archive
```

That keeps the local path and the CI artifact story on the same surface instead of inventing a
second readiness workflow.

When you want a repo-owned baseline for later compare gates:

```bash
ota receipt --json --archive --promote-baseline
ota receipt --json --baseline promoted
ota receipt --snapshot latest
```

Use `promoted` when a team wants an explicit accepted repo state, and use `latest` when the newest
archived receipt is enough for a local drift check.

When a repo declares more than one workflow, scope receipt history explicitly:

```bash
ota receipt --workflow frontend --json --archive
ota receipt --workflow frontend --json --baseline latest
```

That keeps one workflow's archived receipt/baseline lane from silently replacing another's.

Use `ota receipt --snapshot ...` when you want to read the archived semantic contract truth
directly instead of only consuming it through `ota diff` or receipt correlation.

Public architecture guide:
[Execution Governance Loop](https://ota.run/docs/reference/execution-governance-loop)

Public operator guide:
[Semantic Snapshots and Correlation](https://ota.run/docs/reference/semantic-snapshots-and-correlation)

Local core spec:
[semantic-snapshots-and-correlation.md](docs/spec/semantic-snapshots-and-correlation.md)

Use policy review when the contract and approved policy need to be reconciled:

```bash
ota policy review
```

### Agent guidance from the same contract

If you want repo-local agent guidance from the same contract:

```bash
ota agents
ota agents --write
```

### Workspace bootstrap

If you are setting up multiple repos together:

```bash
ota workspace detect --dry-run .
ota workspace init --dry-run .
ota workspace init .
ota workspace validate .
ota workspace up --dry-run .
ota workspace up .
```

If the contract declares agent guidance, `ota doctor --json` and `ota explain --json` surface the
same safe-task, verification, and writable-path hints that humans can review in `ota.yaml`.

If you want the fastest path to the right example by repo shape, use
[Examples by Goal](docs/adoption/examples-by-goal.md).

Example contracts:

- [basic-node](examples/basic-node/ota.yaml) - Node / TypeScript starter
- [basic-python](examples/basic-python/ota.yaml) - uv-backed Python starter
- [basic-go](examples/basic-go/ota.yaml) - Go toolchain starter
- [basic-ruby](examples/basic-ruby/ota.yaml) - Ruby + Bundler starter
- [basic-dotnet](examples/basic-dotnet/ota.yaml) - .NET toolchain starter
- [basic-java](examples/basic-java/ota.yaml) - SDKMAN-backed Maven starter
- [basic-rust](examples/basic-rust/ota.yaml) - Rustup-backed Cargo starter
- [basic-script](examples/basic-script/ota.yaml) - Script-only starter
- [basic-services](examples/basic-services/ota.yaml) - Service-backed repo starter
- [shared-local-topology](examples/shared-local-topology/ota.yaml) - Shared local backend topology
- [shared-remote-topology](examples/shared-remote-topology/README.md) - Shared remote topology dogfood
- [full-contract](examples/full-contract/ota.yaml) - Full contract surface
- [workspace-acquire](examples/workspace-acquire/ota.workspace.yaml) - Workspace acquisition flow
- [ota-run/examples](https://github.com/ota-run/examples) - advanced, production-adjacent examples and templates

## Why ota exists

Repo setup truth is usually fragmented across:

- language manifests
- runtime version files
- task scripts
- container config
- CI config
- README setup notes
- tribal knowledge

ota consolidates that into one canonical contract:

```yaml
ota.yaml
```

The goal is not hidden automation. The goal is deterministic, inspectable execution governance.

## Open Source and Governance

ota is maintainer-led open infrastructure for execution governance. The core CLI, contracts, JSON
output, and docs are public under Apache 2.0, while roadmap stewardship and future enterprise
offerings stay operated by Ota.

ota is open source, but it is not positioned as a community-governed codebase.

- governance is maintainer-led by Ota so the contract, diagnosis model, and machine-readable surfaces stay coherent
- issues, bug reports, docs feedback, and real-repo examples are welcome
- external code contributions are not currently accepted

See [docs/policy/governance.md](docs/policy/governance.md) for the governance model and
[CONTRIBUTING.md](CONTRIBUTING.md) for the current contribution policy.

## What ota does today

The public command surface is in [docs/spec/command-reference.md](docs/spec/command-reference.md).
Start with `ota doctor`, then `ota validate`, `ota up`, and `ota run <task>`.

Near-term policy and provisioning direction:

- [Environment variables](docs/spec/env-resolution-and-policy.md)
- [Policy-backed provisioning sources](docs/spec/policy-backed-provisioning.md)
- [Policy inspection](docs/spec/command-reference.md#ota-policy)
- [Uninstall](docs/spec/command-reference.md#ota-uninstall)

Global flag:

```bash
ota --debug <command>
ota --plain <command>
```

`--debug` emits command-phase tracing to stderr without changing normal stdout.
`--plain` emits ASCII-first output without emoji, icons, or ANSI color.

Use `--debug` when you want command traces for `ota up`, `ota run <task>`, `ota workspace up`,
`ota workspace refresh`, `ota workspace diff`, `ota workspace status`, `ota workspace run <task>`, `ota doctor`, `ota detect`, `ota diff`, and
`ota explain`.
Commands like `ota validate`, `ota tasks`, `ota workspace validate`, `ota workspace tasks`, and
`ota workspace list` should usually stay quiet unless you are actively debugging.

Current behavior:

| Surface | Current behavior |
| --- | --- |
| `ota validate` | Parses and semantically validates `ota.yaml`. |
| `ota tasks` | Lists validated tasks and execution form. |
| `ota run <task>` | Resolves dependencies, executes deterministically, and honors `after_success` / `after_failure` / `after_always`. |
| `ota run <task> --agent`, `ota up --agent` | Enforce declared agent-safe boundaries; refuse unsafe requested/closure tasks; emit refusal receipts. |
| `ota diff` | Semantic contract diff with deterministic added/missing/changed reporting. |
| `ota explain` | Turns readiness findings into an ordered remediation plan. |
| `ota doctor` | Reports env/runtime/tool/service/check findings with severity, explanation, and next action; works even without `ota.yaml`; supports `--mode container`; and `--fix` applies only shipped deterministic repo-hygiene and native command-tool activation fixes before re-diagnosing. |
| `ota init` | Creates starter contracts (detector-led or pack-led), includes starter task descriptions, can carry repo dotenv sources into `env.sources`, supports advisory `--pack` mismatch notes, and ships packs for `node`, `python`, `ruby`, `go`, `rust`, `dotnet`, `php-composer`, `java-maven`, `java-gradle`. |
| `ota agents` | Exports/syncs repo-local `AGENTS.md`, preserves user-authored content with an ota-managed block, skips no-op writes, labels that section explicitly, and emits the contract-owned `ota run ...` form for listed tasks. |
| `ota check` | Runs declared checks without runtime/tool/env/task execution. |
| `ota up` | Validates, selects default workflow, runs setup early on precondition failures, starts workflow services in dependency order, activates workflow run task runtime when present, then re-checks readiness. |
| `ota detect` | Default mode infers a candidate contract with provenance/confidence without writing. |
| `ota detect --write` | Writes only conservative `high` confidence fields. |
| `ota detect --merge --dry-run` | Compares detected signals with existing `ota.yaml` and surfaces stale fields without writing. |
| `ota detect --merge` | Applies additive missing fields at `high` confidence. |
| Drift posture | No standalone `ota drift` command yet; use `ota detect --merge --dry-run` for contract drift and `ota doctor` for trust/readiness drift. |
| `ota completion ...` | Managed completion install/remove/check, raw script output, and command/task/input/member/workspace-aware completions across `run`, `env`, `extensions`, `receipt`, and workspace commands. |
| `ota workspace validate` | Validates `ota.workspace.yaml` separately from repo contracts. |
| `ota workspace tasks` | Lists workspace repo tasks in dependency order (including post-outcome hooks and repo task bindings). |
| `ota workspace run <task>` | Executes one task across workspace repos in dependency order with deterministic reporting and per-repo task-name mapping via `repos.<name>.tasks.<task>.task`. |
| `ota workspace run/up/refresh --json --progress-json` | Streams live progress NDJSON on stderr while preserving final JSON report on stdout, with explicit `phase` and `stage_family`. |
| `ota workspace explain` | Turns workspace readiness findings into ordered remediation steps. |
| `ota workspace check` | Runs checks across repos; honors workflow pinning via `repos.<name>.workflow`. |
| `ota workspace doctor` | Aggregates readiness across workspace repos (including not-yet-acquired repos) without merging repo/workspace truth; respects per-repo workflow selection. |
| `ota workspace up` | Can acquire missing repos from declared sources and orchestrates repo-level `up` across workspace workflows. |
| `ota workspace refresh` | Re-syncs existing repos only; supports `--dry-run`, `--force`, `--prune`, and a branch, tag, or SHA `--ref` override. |
| `ota workspace diff` | Read-only comparison of local workspace repo state vs declared source. |
| `ota workspace status` | Combines readiness and drift in one read-only summary using workflow-selected repo paths when declared. |
| `ota workspace receipt` | Captures workspace state as a read-only receipt artifact for CI/archiving. |
| Integrations | Editors/CI should consume `--json` surfaces (`ota doctor --json`, `ota workspace doctor --json`, `ota workspace list --json`, `ota up --json`) instead of scraping text output. |

### Shell completion quickstart

Use the managed shell hook first:

```bash
ota completion --setup
ota completion --remove
ota completion check
```

If auto-detection is not available or you want one explicit shell:

```bash
ota completion zsh --setup
ota completion zsh --remove
ota completion bash --setup
ota completion fish --setup
ota completion powershell --setup
ota completion elvish --setup
```

Once the shell has sourced that hook, ota keeps completion contract-aware instead of static: repo commands complete member names, task names, and task inputs from the active contract, while workspace commands complete declared repo names and only suggest workspace task names that remain runnable across the selected repo set.
Receipt compare flows also complete `latest`, `promoted`, and archived receipt JSON files from `.ota/receipts` so baseline selection stays discoverable at the shell.

## Execution Modes and Provisioning

ota supports three execution backends for task-oriented commands:

- `native` runs tasks on the host machine.
- `container` runs tasks in an OCI-compatible container using the image defined by the repo contract.
- `remote` runs tasks on a separate machine or workspace through a remote provider.

### Why the three modes exist

- `native` is the simplest path when the host already has the right toolchain and you want to debug against the real machine.
- `container` is the reproducible path when you want a fixed toolchain, deterministic setup, and CI-like behavior.
- `remote` is the off-host path when execution needs to happen somewhere else entirely, such as a dev box, cluster, or managed workspace.

### What ota does today

- `ota run` and `ota up` can execute through the configured backend path.
- `ota up` can run the `setup` task through the same backend selection as `ota run`.
- policy-backed provisioning adapters follow the same backend selection, so container-backed `ota up` provisions inside the container instead of on the host and stops before host provisioning when the selected container engine is unavailable.
- `ota doctor` checks the prerequisites for the preferred backend and reports missing tools or suspicious remote target shape early.
- `ota clean` can remove persistent container state for container-backed repos.
- `ota clean --stale` can remove exited ota-managed containers across repos without requiring an `ota.yaml`, and it surfaces container-engine query failures instead of silently treating them as empty.

### What ota does not do today

- ota does not automatically install every missing host tool or language runtime.
- ota does not turn a laptop into a fully managed workstation.
- ota does not invent remote provisioning or remote workspace selection beyond the configured provider path.

### Container backend

Container execution is useful when you want ota to run repo tasks in a known environment instead of relying on whatever happens to be installed locally.

Benefits:

- removes drift in Java, Maven, shell, and other repo tool versions
- makes local execution closer to CI
- gives agents a stable execution surface
- supports persistent or ephemeral lifecycle behavior where the contract and command support it

Requirements:

- at least one supported container engine CLI must be installed and running
- the contract must declare `execution.backends.container.image`
- the image must be pullable and runnable by the selected engine

In this repository, the container image is:

```yaml
execution:
  preferred: container
  lifecycle: persistent
  supported:
    - native
    - container
  backends:
    container:
      image: rust:1.94-bookworm
```

### Native backend

Native execution is useful when:

- you want to debug against the exact host environment
- the repo already has the required toolchain installed
- you want the fewest moving parts and no container boundary

Native execution does not require a container engine, but it does require the host tools that the task depends on.

### Remote backend

Remote execution is useful when the work should happen outside the local machine:

- `ssh` for a team dev box or dedicated host
- `kubectl` for execution inside a Kubernetes-backed environment
- `tsh` for Teleport-managed infrastructure
- `daytona` for a managed remote development workspace

Remote execution is only available when the contract declares the provider and target fields required by the backend.

### Which commands use the backend

These commands execute repo tasks and therefore respect the backend selection:

- `ota run <task>`
- `ota up`

These commands do not run repo tasks and therefore do not use the execution backend:

- `ota validate`
- `ota doctor`
- `ota detect`
- `ota init`
- `ota tasks`

### Override syntax

Use `--mode` to force one invocation to use a specific execution mode:

```bash
ota run test --mode native
ota run test --mode container
ota up --mode native
ota up --mode container
```

Use `--lifecycle` when you need to override container reuse for one invocation:

```bash
ota run test --mode container --lifecycle persistent
ota run test --mode container --ephemeral
```

Use `ota tasks --use` to see the exact runnable task surface for the current contract. Each task
shows its `Human Run` commands, `Agent Run` commands only when the full dependency closure is
agent-callable, the closure-aware `Agent Policy`, and modes in stable `Container`, `Native`, then
`Remote` order with the selected lane marked `(Default)`, plus command preview, effect surface,
required inputs, and matching dry-run / receipt follow-up commands. Use plain `ota tasks` for the
full declaration view, including dependencies, hooks, and notes. Unsupported Container or Native
planes are marked explicitly instead of being silently omitted. Automation should consume
`ota tasks --json` and use `tasks[].use.modes[]` as the canonical human/agent mode matrix;
`use.human` and `use.agent` remain selected-mode compatibility projections:

```bash
ota tasks --use
```

Use task-surface filters when you need a narrower view:

```bash
ota tasks --safe
ota tasks --unsafe
ota tasks --via native
ota tasks --via container
```

## Hosted validation and service provisioning

In CI, the runner still owns the job. ota owns the repo contract and can provision declared
services such as Postgres through `ota up`, so the workflow stays thin and the service intent lives
with the repo instead of being duplicated in pipeline YAML.

If the runner is GitHub Actions and you want the official wrapper for step summaries, annotations,
pull-request comments, and receipt artifacts, use
[ota-run/action](https://github.com/ota-run/action) and see
[docs/spec/github-action-workflow.md](docs/spec/github-action-workflow.md).
If you need a repo-local summary renderer outside that wrapper, `ota annotations --format markdown`
emits a compact step-summary or PR-comment block from the same canonical doctor JSON, and
`ota annotations --mode receipt-diff --format markdown` does the same for
`ota receipt --json --baseline ...` compare output.

That is different from host provisioning. ota can provision declared services and run tasks in a
container or remote backend, but it does not replace the OS package manager, language installer,
or workstation bootstrap process.

```yaml
name: ci

on:
  push:
  pull_request:

jobs:
  ci:
    runs-on: ubuntu-latest

steps:
      - uses: actions/checkout@v4
      - name: Install ota
        run: curl -fsSL https://dist.ota.run/install.sh | sh
      - name: Validate contract
        run: ota validate
      - name: Prepare repo
        run: ota up
      - name: Run lint
        run: ota run lint
      - name: Run tests
        run: ota run test
```

## Detect trust model

ota treats detection as trust-sensitive.

- `ota detect --dry-run` is the review path
- `ota detect --contract` is the exact detected starter text path
- `ota detect --merge --dry-run` is the review path for existing contracts
- every inferred field includes provenance
- every inferred field includes confidence
- write mode uses only `high` confidence fields
- write mode validates before writing
- write mode refuses to overwrite an existing `ota.yaml`
- merge write is additive only in the current implementation
- lower-confidence or conflicting changes stay review-only

This is intentional. The project prefers conservative correctness over aggressive generation.

## Open standard intent

ota is being built as open infrastructure, not as a vendor-specific workflow.

The long-term aim is:

- one canonical readiness contract per repo
- one canonical bootstrap contract per workspace
- deterministic behavior without LLM dependency in the core path
- human and agent symmetry
- interoperability with the existing tool ecosystem

## Current status

V1 is complete and the release gate is green.

The current shipped foundation includes:

- contract validation
- task listing
- deterministic task execution
- readiness diagnosis
- onboarding via `up`
- detection with dry-run, conservative first write, and conservative additive merge
- separate workspace contract validation, diagnosis, and bootstrap
- generic git-based workspace acquisition for missing repos
- monorepo root/member loading for repo commands via `--member`
- fixture-backed coverage for Java detection, container-heavy, container-only, conflict-heavy Node, mixed Node/Python, legacy Python, and ugly/polyglot mixed-reality repo shapes

Current planning state:

- V1 archive: [docs/planning/v1/phases.md](docs/planning/v1/phases.md)
- V1 release gate: [docs/planning/v1/release-gate.md](docs/planning/v1/release-gate.md)
- V2 archive: [docs/planning/v2/plan.md](docs/planning/v2/plan.md)
- V2.1 archive: [docs/planning/v2.1/plan.md](docs/planning/v2.1/plan.md)
- V6 archive: [docs/planning/v6/plan.md](docs/planning/v6/plan.md)
- Active branch and implementation handoff: [docs/ai/current-state.md](docs/ai/current-state.md)
- Next planned, inactive slice: [docs/planning/v11.21/plan.md](docs/planning/v11.21/plan.md)
- Each version plan retains its own explicit status; version order does not imply completion.
- Archived local UX hardening slice: [docs/planning/v5-ux-hardening.md](docs/planning/v5-ux-hardening.md)
- V5 mutation controls and caching: [docs/spec/mutation-controls-and-caching.md](docs/spec/mutation-controls-and-caching.md)

## Enterprise Direction

Enterprise work is planned as a layer around the open core, not as a different contract truth.

- the open core remains the public CLI, repo/workspace schemas, JSON output, and documentation
- enterprise value should come from hosted policy, audit, fleet coordination, private adapters,
  onboarding, and support
- the public contract should stay usable on its own and should not become a thin wrapper around a paid control plane

See [docs/policy/support-and-enterprise.md](docs/policy/support-and-enterprise.md) for the current
enterprise boundary and likely future commercial surfaces.

## Contribution policy

ota is maintainer-led. External code contributions are not currently accepted.

Use the GitHub issue templates for bug reports, feature requests, docs feedback, and real-repo
reproductions.

Read:

- [CONTRIBUTING.md](CONTRIBUTING.md) for the current contribution workflow
- [docs/policy/governance.md](docs/policy/governance.md) for project governance
- [docs/policy/commercial-policy.md](docs/policy/commercial-policy.md) for the open-core and commercial boundary
- [docs/policy/support-and-enterprise.md](docs/policy/support-and-enterprise.md) for support and enterprise direction

Repo-level support entry point: [SUPPORT.md](SUPPORT.md)

## Documentation

### Start here

- [One-team rollout](docs/adoption/one-team-rollout.md)
- [Worked example: existing repo](docs/adoption/worked-example-existing-repo.md)
- [Command reference](docs/spec/command-reference.md)
- [GitHub Action workflow](docs/spec/github-action-workflow.md)
- [Contract reference](docs/spec/contract-reference.md)
- [Workflow model](docs/spec/workflows.md)
- [Workspace reference](docs/spec/workspace-reference.md)
- [Shell semantics](docs/spec/shell-semantics.md)
- [Service behavior](docs/spec/service-behavior.md)
- [JSON output reference](docs/spec/json-output-reference.md)
- [Audit and provenance](docs/spec/audit-and-provenance.md)
- [Policy packs](docs/spec/policy-packs.md)
- [Exit codes](docs/spec/exit-codes.md)
- [Docs clarity spec](docs/spec/docs-clarity-spec.md)

### Core concepts

- [Philosophy](docs/philosophy.md)
- [Governance](docs/policy/governance.md)
- [Compatibility policy](docs/spec/compatibility-policy.md)
- [Support policy](docs/spec/support-policy.md)

### Design and engineering

- [Security posture](docs/design/security-posture.md)
- [Performance budget](docs/design/performance-budget.md)
- [Doctor quality bar](docs/design/doctor-quality-bar.md)
- [UX review loop](docs/design/ux-review-loop.md)
- [Adoption readiness gate](docs/design/adoption-readiness-gate.md)
- [Detect write gate](docs/design/detect-write-gate.md)

### Planning and roadmap

- [V1 phases](docs/planning/v1/phases.md)
- [V1 release gate](docs/planning/v1/release-gate.md)
- [V2 plan](docs/planning/v2/plan.md)
- [V2.1 plan](docs/planning/v2.1/plan.md)
- [V3 plan](docs/planning/v3/plan.md)
- [V4 plan](docs/planning/v4/plan.md)
- [V5 plan](docs/planning/v5/plan.md)
- [V6 plan](docs/planning/v6/plan.md)
- [V7 plan](docs/planning/v7/plan.md)
- [V8 plan](docs/planning/v8/plan.md)
- [V9 plan](docs/planning/v9/plan.md)
- [V10 plan](docs/planning/v10/plan.md)
- [V5 UX hardening completion slice](docs/planning/v5-ux-hardening.md)
- [Hosted validation workflow](docs/spec/hosted-validation-workflow.md)
- [Fixture repo plan](docs/planning/fixture-repo-plan.md)
- [Roadmap](ROADMAP.md)

### Contributing

- [Contributing guide](CONTRIBUTING.md)

## Examples

Choose by goal:

- first repo contract: [Basic Node](examples/basic-node/ota.yaml), [Basic Python](examples/basic-python/ota.yaml), [Basic Ruby](examples/basic-ruby/ota.yaml), [Basic Rust](examples/basic-rust/ota.yaml)
- existing app with services: [Basic Services](examples/basic-services/ota.yaml), [Mixed Node + Python](examples/mixed-node-python/ota.yaml)
- shared topology: [Shared Local Topology](examples/shared-local-topology/ota.yaml), [Shared Remote Topology](examples/shared-remote-topology/README.md)
- multi-repo bootstrap: [Basic Workspace](examples/workspace-basic/ota.workspace.yaml), [Acquisition Workspace](examples/workspace-acquire/ota.workspace.yaml)
- deterministic checkout materialization: [Single Checkout](examples/ensure-git-checkout/ota.yaml), [Multi Checkout](examples/ensure-git-checkouts/ota.yaml)
- realistic reference shape: [Fullstack Node + Go](examples/fullstack-node-go/ota.yaml), [Full contract example](examples/full-contract/ota.yaml), [ota-run/examples](https://github.com/ota-run/examples)

If you want the shortest “which example proves what?” guide, use
[Examples by Goal](docs/adoption/examples-by-goal.md).

### Minimal contracts

- [Basic Node](examples/basic-node/ota.yaml) - Node / TypeScript starter
- [Basic .NET](examples/basic-dotnet/ota.yaml) - .NET toolchain starter
- [Basic Java](examples/basic-java/ota.yaml) - SDKMAN-backed Maven starter
- [Basic Python](examples/basic-python/ota.yaml) - uv-backed Python starter
- [Basic Go](examples/basic-go/ota.yaml) - Go toolchain starter
- [Basic Ruby](examples/basic-ruby/ota.yaml) - Ruby + Bundler starter
- [Basic Rust](examples/basic-rust/ota.yaml) - Rustup-backed Cargo starter
- [Basic Script](examples/basic-script/ota.yaml) - Script-only starter

### Mixed and realistic repos

- [Mixed Node + Python](examples/mixed-node-python/ota.yaml) - Polyglot app example
- [Fullstack Node + Go](examples/fullstack-node-go/ota.yaml) - Frontend/backend split example
- [Full contract example](examples/full-contract/ota.yaml) - Exhaustive contract reference
- [ota-run/examples](https://github.com/ota-run/examples) - advanced, production-adjacent examples and templates

### Workspace

- [Basic Workspace](examples/workspace-basic/ota.workspace.yaml) - Multi-repo starter; compare `ota workspace detect --dry-run` with `ota workspace init --dry-run`, then use `ota workspace up --dry-run` before preparing the stack.
- [Acquisition Workspace](examples/workspace-acquire/ota.workspace.yaml) - Workspace acquisition flow; compare `ota workspace detect --dry-run` with `ota workspace init --dry-run`, then use `ota workspace up --dry-run` and `ota workspace up` to acquire and prepare repos.

---
<div align="center">
    Ota 🦦
    </div>

ota

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README