Appendix: Configuration Files
Map every public RC.6 AIT configuration file to its purpose, owner, mutation boundary, and detailed schema reference.
Audience: Developers, operators, integrators, and release engineers
Configuration-file map#
RC.6 uses a small set of repository files for durable user configuration. The files are independent contracts: a value in one file does not silently replace the authority owned by another file.
| File | Purpose | Normal owner |
|---|---|---|
.ait/config.json | Repository identity, Line and remote routing, workflow defaults, Task-worktree placement, and bounded runtime hints. | ait init, ait config, ait remote, and the owning AIT lifecycle. |
.ait/policy.yaml | Admission requirements selected by the Repository policy profile. | ait init; review changes together with .ait/config.json.policy_profile. |
.aitignore | Repository-relative visibility rules for workspace, status, Snapshot, and Plan filesystem discovery. | Repository author. |
ci/patch_ci.json | Patchset CI suite catalog used for remote readiness. | Repository author; ait remote add can create a starter file without overwriting an existing one. |
ci/config.contract.json | Optional local locator for a non-default CI suite catalog. | Repository author. This is not a replacement for the canonical catalog required at remote registration. |
ait-external.toml | Direct external-Repository declarations and language bindings. | Repository author. |
ait-external.lock | Exact resolved external graph and Snapshot pins. | ait external update; commit the generated result. |
ait-external.links.toml | Local development overrides for external materialization. | ait external link and ait external unlink; do not use for release-ready materialization. |
.ait/agent-workers.json | Named Telegram, LINE, Discord, and Slack agent-worker instances. | ait agent worker commands or an operator following the schema. |
ait-release.json | Generic command-adapter release package, components, commands, and artifacts. | Release author. |
ait-release-family.json | Coordinated AIT native-family release matrix. | AIT release-family maintainer; this is a specialized AIT-family contract. |
.ait-worktree.json | One managed worktree's overlay and binding metadata. | AIT only. |
The server has no separate public ait-server.json, ait-server.toml, or .ait/server.* configuration file in RC.6. Its supported operator inputs are command-line options and the documented environment contract.
Which file should I edit?#
- Prefer the command that owns a field. It can validate the value and preserve lifecycle invariants.
- Hand-edit only author-owned manifests such as
.aitignore,ci/patch_ci.json,ait-external.toml, and the release manifests. - Treat
ait-external.lock,ait-external.links.toml, and.ait-worktree.jsonas generated or command-managed outputs. - Keep credentials out of versioned files when a documented process or worker environment-file input is available.
- Verify JSON, YAML, or TOML syntax before starting a Task or remote registration. Unknown-field behavior differs by contract and is stated on each reference page.
What is intentionally outside this map?#
Runtime state, caches, Binary DB authorities, activation receipts, generated artifacts, package-manager manifests, build-tool configuration, and agent instruction files are not user configuration for AIT itself. They have their own owners and must not be inferred from this appendix.