One quality contract
Version a closed signal vocabulary in .ayni.toml, with truthful adapter-specific capability tiers.
Commit policy, run repository tools in a locked environment, and give humans and agents the same scoped evidence.
Ayni keeps these responsibilities separate and reviewable:
.ayni.toml selects languages, signals, thresholds, structural rules, and optional runtime capabilities..ayni.lock records exact tools, native dependency inputs, preparation state, and an immutable base image.check, verify, and impact run measure the current workspace and produce normalized evidence.Installing the CLI is separate from provisioning a repository environment. Ayni never silently creates a lock or rebuilds an image during a quality run.
After installing Ayni, configure the environment certificate signing variables used by env build:
ayni init --dry-run
ayni init --write
ayni env show
ayni env lock
ayni env build
ayni checkinit proposes a minimal test-only policy from adapter-owned project discovery; it never guesses thresholds and --write refuses to overwrite existing policy.
Commit .ayni.toml, .ayni.lock, and your native dependency/tool locks. Keep .ayni/ and the generated OCI image local.
Follow the complete quickstart →
Use a focused command while developing:
ayni verify test
ayni impact run --base origin/mainThen run the complete repository contract before integration:
ayni checkThese commands run in the current workspace. A built Ayni image supplies locked tools when a platform starts it with an attached checkout.
| Language | Managed project shape | Adapter guide |
|---|---|---|
| Rust | Cargo projects and workspaces | Rust |
| Node | npm and pnpm projects and workspaces | Node |
| Go | Go modules and workspaces | Go |
| Python | uv projects and workspaces | Python |
| Kotlin | Supported Gradle projects and workspaces | Kotlin |
Unsupported project variants fail explicitly. Signal depth also varies: consult the adapter capability matrix.