@getarbiter/cli 0.5.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,31 @@
+arbiter
+Copyright 2024-2026 Luca Dominici and the arbiter contributors
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+---
+
+This product includes software developed by third parties.
+Third-party license information is available in THIRD_PARTY_LICENSES.md,
+which is generated automatically (see scripts/gen-third-party-licenses.mjs)
+and shipped in each release artifact.
+
+---
+
+Companion plugins (detected at runtime, never bundled): arbiter's skill-detector
+recognises external Claude Code skill suites already installed in the user's
+environment -- Superpowers (https://github.com/obra/superpowers, MIT) and
+ponytail (https://github.com/DietrichGebert/ponytail, MIT) among them -- and
+references them instead of duplicating equivalent content. arbiter ships no
+third-party skill text. See the "Companion plugins" section of
+THIRD_PARTY_LICENSES.md for the full, generated list.

package/PRIVACY.md

@@ -0,0 +1,111 @@
+---
+title: 'Privacy Policy'
+doc_version: '1.0.1'
+status: active
+last_review: '2026-09-10'
+owner: ''
+canonical_id: ''
+tags: ['audience/dev', 'kind/security']
+related: []
+---
+
+# Privacy Policy
+
+**Arbiter collects zero telemetry and makes zero unsolicited network calls.**
+
+---
+
+## What Arbiter Does NOT Collect
+
+- Usage statistics or analytics
+- Error reports or crash data
+- Machine identifiers or IP addresses
+- Project structure, file names, or code content (unless you explicitly enable cross-model review,
+  which sends the change diff to the selected provider CLI)
+- Command-line arguments or flags you pass
+- Timing data or performance metrics
+
+There is no opt-out because there is nothing to opt out of.
+
+---
+
+## What Arbiter Does Over the Network
+
+Arbiter is offline by default. The only network activity is explicit and user-initiated:
+
+| Action                                   | When                                                                    | Why                                                                                                                                 |
+| ---------------------------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `arbiter init` (GitHub-backend projects) | Repo setup step touches branch protection, labels, or the project board | Shells out to your local `gh` CLI, which uses its own auth — arbiter never receives or transmits a token itself                     |
+| `arbiter init --recipe <https://…>`      | You pass an `https://` recipe URL                                       | Fetches the recipe JSON you pointed it at                                                                                           |
+| Cross-model review                       | You explicitly enable it and consent to diff egress                     | Sends the change diff through your local provider CLI, which uses its own auth — arbiter never receives or transmits a token itself |
+
+In every case, the network call is a direct consequence of a command (and, for recipes, a URL) you explicitly ran. Arbiter does not call home in the background, on startup, or at any other time.
+
+---
+
+## How to Verify
+
+**Offline use:**
+
+Arbiter's core commands (`init`, `update`, `diff`, `doctor`, `validate`) work without any network access. You can run them with your firewall fully blocking outbound connections.
+
+**Packet capture:**
+
+```bash
+# macOS / Linux — watch for unexpected outbound connections
+sudo tcpdump -i any -n "host not 127.0.0.1 and not ::1" &
+arbiter init --yes
+kill %1
+```
+
+Any connection you see will be from npm (package resolution) or your own toolchain, not from arbiter itself.
+
+**Code audit:**
+
+The full source is at `src/`. Network-capable code paths are limited to:
+
+- `src/utils/plugin-loader.ts` — loads an already npm-installed plugin from local `node_modules`; arbiter itself makes no registry call (you run `npm install <pkg>` yourself first)
+- `src/github/` — branch protection, labels, and project-board setup during `arbiter init`, shelled out to your local `gh` CLI (its own auth, not a token passed to arbiter)
+- `src/recipes/loader.ts` — fetches a recipe JSON, only when you pass an `https://` URL to `arbiter init --recipe` (size-capped, 10s timeout, redirects not followed)
+
+---
+
+## Anti-Telemetry CI Enforcement (#642)
+
+Every pull request runs an automated scan of `dist/` and `src/templates/` for network call patterns. Any match not present in [`suppressions/telemetry-allowlist.json`](suppressions/telemetry-allowlist.json) fails the build.
+
+**Scanned patterns:** `fetch(`, `http.request(`, `https.request(`, `axios`, `segment.`, `amplitude.`, `mixpanel`, `posthog`, `sentry`, `bugsnag`
+
+Each allowlist entry explains the file/pattern and its intended use.
+
+Manual npm-library `workflow_dispatch` smoke sends fixed registry.npmjs.org
+identity/scope GETs: token authentication, no redirects, 15s timeout. It never
+logs tokens, uploads repository data or builds/signs/publishes. Identity/scope
+visibility proves neither publication permission nor OIDC configuration.
+
+---
+
+## Local Observability Artifacts (#635-#640)
+
+Arbiter writes two categories of local-only files for debugging and bug reports:
+
+| Location                                 | Written by                   | Default lifecycle                         |
+| ---------------------------------------- | ---------------------------- | ----------------------------------------- |
+| `~/.arbiter/logs/<runId>/`               | Every invocation (default)   | LRU-rotated; only the 10 most recent kept |
+| `~/.arbiter/profiles/<runId>.cpuprofile` | `arbiter --profile` (opt-in) | Kept until you delete it                  |
+
+**Both are local. Neither is uploaded anywhere.** They exist for you to inspect or attach to a bug report at your discretion.
+
+**Redaction.** Environment variables captured in `env.json` are redacted by name match: any variable whose name (case-insensitive, underscore-segment-aware) contains `TOKEN`, `SECRET`, `KEY`, `PASSWORD`, `PASS`, `AUTH`, `CREDENTIAL`, `PRIVATE`, or `API`, or starts with `GH_`, `GITHUB_`, or `NPM_`, has its value replaced with `***REDACTED***`. Patterns and behavior are tested in `__tests__/utils/replay.test.ts`.
+
+**Opt-out.** Pass `--no-replay` to skip writing any replay log for an invocation. The flag is also recognized via `ARBITER_NO_REPLAY=1`.
+
+---
+
+## Reporting Privacy Concerns
+
+If you discover unexpected network activity, please report it via [SECURITY.md](SECURITY.md).
+
+---
+
+_Last reviewed: 2026-09-10_

package/README.md

@@ -0,0 +1,237 @@
+---
+title: 'Arbiter — AI governance that installs itself.'
+doc_version: '1.0.2'
+status: active
+last_review: '2026-09-08'
+owner: ''
+canonical_id: ''
+tags: ['audience/dev', 'kind/spine']
+related: []
+---
+
+# Arbiter
+
+**AI governance that installs itself — and can't be faked.**
+
+[![No Telemetry](https://img.shields.io/badge/telemetry-none-brightgreen)](PRIVACY.md)
+[![npm version](https://img.shields.io/npm/v/@getarbiter/cli)](https://www.npmjs.com/package/@getarbiter/cli)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue)](LICENSE)
+[![Node](https://img.shields.io/badge/node-%E2%89%A522-brightgreen)](https://nodejs.org/)
+
+```bash
+npx @getarbiter/cli init
+```
+
+Run init in a repository that already contains a supported language marker. In a new empty
+directory, pass it explicitly (for example, `npx @getarbiter/cli init --language typescript`):
+arbiter exits non-zero when the language is unknown because the naming and test-pyramid checks
+cannot be configured honestly.
+
+![Terminal demo: arbiter init scaffolds governance for a TypeScript project, then the L1 gate runs clean](docs/assets/demo.svg)
+
+Coding agents are great at writing code and even better at claiming it works.
+Arbiter makes "done means tested" mechanical: `npx @getarbiter/cli init` gives your
+repo a single canonical rulebook, gates that fail loudly, and evidence checks
+anchored to git history. If the test never failed first, the task doesn't
+advance. No telemetry, no server, no lock-in — delete the generated files and
+it's gone.
+
+---
+
+## Three primitives
+
+Arbiter is built on three ideas. Everything else — hooks, gates, generators,
+CLI flags — is plumbing in service of them. (Full treatment: [docs/CONCEPTS.md](docs/CONCEPTS.md).)
+
+### Evidence-gated "done"
+
+A task isn't done because someone says it's done — it's done because the
+artifacts prove it. Arbiter's TDD-evidence checks and `stop-evidence-guard`
+hook (INV-114) require a test that failed before the fix and passes after it,
+correlated to the current branch and commit SHA, before a completion claim is
+accepted. A claim with no matching evidence is rejected like a failing gate —
+agents can't fake green.
+
+### Governance that installs itself
+
+One `arbiter init` emits `AGENTS.md` (the canonical governance file every
+supported AI tool reads), thin per-tool pointer files, hooks, gates, and a
+matching CI workflow — all ordinary, version-controlled files. Re-running
+`arbiter init` — or `arbiter update` / `arbiter diff` to preview what would
+change — refreshes what arbiter manages and leaves your customizations alone.
+For a declared `language` and `databaseEngine`, the emitted stack-conformity
+gate reads only root evidence: Node dependency keys from `package.json`, or
+Go module imports from `go.mod`/`go.sum` with module-segment boundaries; a
+lockfile occurrence alone never proves a database driver.
+
+### Task lifecycle with teeth
+
+Work moves through a fixed, machine-checked phase sequence — plan → red (a
+failing test written first) → green (the fix makes it pass) → verify → ship —
+and each advance is gate-blocked: `arbiter task advance` runs that phase's gate
+and refuses to move forward on red. Any agent (human-directed or autonomous)
+can drive it; the phase machine enforces the order regardless of who's behind
+the wheel.
+
+---
+
+## Quickstart
+
+```bash
+npx @getarbiter/cli init
+```
+
+1. Ask your coding agent to implement a change and report done.
+2. It can't — the `stop-evidence-guard` hook blocks the completion claim
+   because there's no correlated evidence yet (INV-114).
+3. Write a failing test first, then record it: `arbiter task record-red --test-path <file>`.
+4. Implement until the test passes.
+5. `node scripts/check-all.mjs L1` goes green — now "done" is accepted, because
+   it's backed by a test that failed before the fix and passes after it.
+
+That's the whole loop. For the full ten-minute walkthrough — install options,
+what lands in your repo, uninstalling — see [docs/QUICKSTART.md](docs/QUICKSTART.md).
+
+The full gate supports 4-core development machines. Step timeouts preserve the
+measured 10-minute budget of the 24-core reference runner by scaling it with
+available cores (`10 minutes × 24 / cores`, with a 10-minute floor). A killed
+step is reported as `TIMEOUT`, separately from a command or assertion failure.
+
+---
+
+## Stack support
+
+**Supported:** TypeScript, Java, Go, Python, Rust · Claude Code, Codex.
+**Experimental:** Kotlin. (No experimental AI tools — the Cursor, Aider, Copilot,
+Gemini and Windsurf generators were retired in ADR-119; `--tools` accepts exactly
+`claude` and `codex`.)
+
+> Tier rule: a language is **Supported** iff all of its _required cells_ —
+> `static_analysis`, `coverage`, `architecture`, `security` in
+> [`src/compatibility/cross-language-matrix.json`](src/compatibility/cross-language-matrix.json)
+> — are `proven`; otherwise **Experimental**. Kotlin is `beta` on all four, so
+> it is the sole Experimental language today.
+
+| Language   | Detected from              | Build tool   | Lint          | Format   | Status       |
+| ---------- | -------------------------- | ------------ | ------------- | -------- | ------------ |
+| TypeScript | `package.json`             | npm          | eslint        | prettier | Supported    |
+| Java       | `pom.xml` / `build.gradle` | gradle/maven | checkstyle    | spotless | Supported    |
+| Rust       | `Cargo.toml`               | cargo        | clippy        | rustfmt  | Supported    |
+| Go         | `go.mod`                   | go           | golangci-lint | gofmt    | Supported    |
+| Python     | `pyproject.toml`           | pip/uv       | ruff          | ruff     | Supported    |
+| Kotlin     | `build.gradle.kts`         | gradle       | detekt        | —        | Experimental |
+
+---
+
+## See it for real
+
+[`examples/ts-library/`](examples/ts-library/), [`examples/python-library/`](examples/python-library/),
+and [`examples/go-library/`](examples/go-library/) are exactly what `arbiter init` generates today for
+each of these three stacks (TypeScript, Python, Go) — not a hand-curated demo. A dedicated CI cell in the
+[Generator Matrix workflow](.github/workflows/generator-matrix.yml) regenerates all three on a
+weekly cadence and before every pre-release, and fails the build on any drift, so these
+directories can't go stale. See
+[`examples/README.md`](examples/README.md) for how to regenerate them yourself and for the
+hand-written walkthroughs covering the other archetypes (frontend-spa, backend-web-db, cli,
+data-pipeline).
+
+---
+
+## What gets generated
+
+### Always generated
+
+| Path                    | Purpose                                                       |
+| ----------------------- | ------------------------------------------------------------- |
+| `AGENTS.md`             | Canonical governance doc every AI tool reads                  |
+| `arbiter.json`          | The stored config every later `update`/`diff` reads           |
+| `.claude/` / `.agents/` | Tool-specific hooks, rules, and pointer files (per `--tools`) |
+| `scripts/check-all.mjs` | The local gate runner (`L1`/`L2`/`L3`/`L4`)                   |
+| `.githooks/`            | pre-commit (`L1`), pre-push (`L2`), commit-msg                |
+| `SECURITY.md`           | Vulnerability-reporting policy                                |
+| `CONTRIBUTING.md`       | Contribution + gate expectations for the repo                 |
+| `.editorconfig`         | Baseline whitespace/charset hygiene                           |
+| `.nvmrc`                | Node version the emitted governance tooling runs on           |
+| `commitlint.config.js`  | Conventional-commit config the `commit-msg` hook reads        |
+
+### Generated only with `--github`
+
+Without `--github` (or `permitGitHub: true` in `arbiter.json`) no `.github/` directory
+is created at all — `examples/ts-library/` above is exactly that case.
+
+| Path                                   | Purpose                                                        |
+| -------------------------------------- | -------------------------------------------------------------- |
+| `.github/workflows/01-pr-fast.yml`     | The PR gate mirroring the local `L1` check                     |
+| `.github/workflows/02-pr-extended.yml` | The extended lane mirroring `L2` (more lanes at higher levels) |
+| `.github/PULL_REQUEST_TEMPLATE.md`     | PR template                                                    |
+| `.github/ISSUE_TEMPLATE/`              | Bug / feature / task-brief / epic forms                        |
+| `.github/labels.yml`                   | Label set the workflows apply                                  |
+| `.github/dependabot.yml`               | Dependency update schedule                                     |
+| `.github/CODEOWNERS`                   | Review routing — only when a GitHub owner is detected          |
+
+Everything arbiter generates is a normal, version-controlled file. Uninstalling
+is a file operation, not a service to tear down:
+
+```bash
+rm -rf .claude/ .agents/ scripts/check-all.mjs AGENTS.md
+git checkout -- .github/   # or remove hand-picked generated workflow files
+```
+
+See [docs/QUICKSTART.md](docs/QUICKSTART.md#4-uninstall) for the full uninstall
+walkthrough, including restoring backed-up files.
+
+The public CLI surface is 16 commands: `init`, `update`, `diff`, `configure`,
+`doctor`, `validate`, `task`, `ship`, `note`, `gold-audit`, `plugin`, `worktree`,
+`gate-exec`, `review`, `explain`, `obsidian`.
+Experimental commands are hidden from default `--help` but stay fully
+functional — list them with `arbiter help --all`. See the
+[CLI Reference](website/reference/cli.md) for full option documentation.
+
+For a document declared with `template: arc42` in the documentation standard,
+`arbiter doc-set --arc42` checks section completeness against its tier's skeleton.
+The matcher accepts English and explicit Italian section titles; translated headings
+do not waive missing sections or the hollow-section ratchet. Other translations
+are not inferred automatically.
+
+---
+
+## Privacy
+
+**No telemetry.** Arbiter collects zero usage data and makes zero unsolicited
+network calls. See [PRIVACY.md](PRIVACY.md).
+
+### How it compares
+
+| Capability                      | arbiter | BMAD | GSD2 | claude-flow | spec-kit |
+| ------------------------------- | ------- | ---- | ---- | ----------- | -------- |
+| Canonical governance file       | ✓       | —    | —    | —           | —        |
+| Evidence-gated completion       | ✓       | —    | —    | —           | —        |
+| Idempotent, re-runnable install | ✓       | —    | —    | —           | —        |
+| Zero telemetry                  | ✓       | —    | —    | —           | —        |
+| Specialized sub-agents¹         | ✓       | ✓    | ✓    | ✓           | —        |
+
+> ¹ Provided by arbiter's **optional orchestration layer** (`/ship`, `/drain`, and
+> sub-agents) — distinct from the installer **core** (rows above), which is
+> usable on its own. [Full comparison →](website/comparisons/index.md)
+
+---
+
+## Status
+
+Beta. TypeScript, Java, Go, Python, and Rust are supported; Kotlin is
+experimental (see [Stack support](#stack-support) for the tier rule). Issues and PRs welcome — no SLA.
+
+---
+
+## Learn more
+
+- [docs/QUICKSTART.md](docs/QUICKSTART.md) — the full ten-minute path
+- [docs/CONCEPTS.md](docs/CONCEPTS.md) — the three ideas, in depth
+- [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md) — contributing to arbiter itself
+- [SECURITY.md](SECURITY.md) — reporting a vulnerability
+
+---
+
+## Sponsoring
+
+arbiter is maintained by volunteers. If you find it useful, consider [sponsoring via GitHub Sponsors](https://github.com/sponsors/LucaDominici).