Skip to main content

ait-native

AIT turns an ordinary coding request into an isolated, sprint-bound repository change with validation evidence and a recoverable land path. It is for individual developers and maintainers who use coding agents and want the work to remain reviewable without inventing a workflow for every repository.

AIT is repository-language-neutral. It does not identify or change behavior for Python, Node.js, Rust, Java, or any other project type.

Official website: https://ait-native.dev/

Install and initialize

python -m pip install ait-native==1.1.3
ait init

Run ait init once inside the repository your coding agent will change. For other verified installation routes, use the official quickstart.

What initialization provides

ait init creates repository-local authority, defaults to solo_local with sprint mode on, creates the sprint directory, and writes the effective workflow router to AGENTS.md. Local work uses bound Task worktrees, Snapshots, and atomic Task finish. The server remains off.

Package boundary

This wheel installs the language-neutral ait CLI, the inactive-by-default ait-server command, and the admitted ait-python binding. The server starts only when explicitly requested.

Local and reviewed closeout

The default local flow finishes dirty work with ait task finish <task-id> --message "<message>"; clean work omits --message. For a reviewed remote flow, the author prepares the selected Patchset and CI evidence with ait workflow ready <task-id> --apply; a reviewer then runs ait workflow finish <task-id> --apply for Review, Policy, and atomic closeout.

Upgrading from 0.x

There is no ait install command in 1.x. Install or upgrade ait-native through your selected package manager, verify it with ait --version, then run ait init only when creating a new 1.0 repository authority. Keep the existing Git repository and history, but do not treat a release candidate as proof that legacy 0.x .ait data can be migrated in place. Preserve the old authority for recovery and use a clean clone or a new repository authority unless the selected release notes explicitly admit that migration. Read the public transition contract.

Metadata

Release files for ait-native 1.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for ait-native 1.1.3
File
ait_native-1.1.3-cp311-abi3-win_arm64.whl CPython 3.11 abi3 Windows ARM64 Details
ait_native-1.1.3-cp311-abi3-win_amd64.whl CPython 3.11 abi3 Windows x86-64 Details
ait_native-1.1.3-cp311-abi3-manylinux_2_28_x86_64.whl CPython 3.11 abi3 Linux glibc 2.28+ x86-64 Details
ait_native-1.1.3-cp311-abi3-manylinux_2_28_aarch64.whl CPython 3.11 abi3 Linux glibc 2.28+ ARM64 Details
ait_native-1.1.3-cp311-abi3-macosx_11_0_arm64.whl CPython 3.11 abi3 macOS 11.0+ ARM64 Details
ait_native-1.1.3-cp311-abi3-macosx_10_12_x86_64.whl CPython 3.11 abi3 macOS 10.12+ x86-64 Details

Total release size: 138.4 MB

Release files / ait_native-1.1.3-cp311-abi3-win_arm64.whl

Download URL ait_native-1.1.3-cp311-abi3-win_arm64.whl
Size 21.6 MB
Tags CPython 3.11 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
30a7a7c170521d29c594671b0ad760a0d3f0422f76650af960874b76d6f7ed06
BLAKE2b-256 checksum
How to use checksums
ded785976b888eaab6a9b8ee509a6d573b589c1c02f46e41663474560fc850a9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log

Release files / ait_native-1.1.3-cp311-abi3-win_amd64.whl

Download URL ait_native-1.1.3-cp311-abi3-win_amd64.whl
Size 23.4 MB
Tags CPython 3.11 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
0594950be369e93fcc91e86e48b4950951bd4bbd08f11ff99293f71d10c1c5f8
BLAKE2b-256 checksum
How to use checksums
2a6b8c28d34eba4f5f7c8a0808904c58db868ba0ac0f6655f0679f5b381f0736
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log

Release files / ait_native-1.1.3-cp311-abi3-manylinux_2_28_x86_64.whl

Download URL ait_native-1.1.3-cp311-abi3-manylinux_2_28_x86_64.whl
Size 25.3 MB
Tags CPython 3.11 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
c74f4fcd1a0b5abdc670e15b4556cc2c5e838b8ff8824583e8818d2eaa22878d
BLAKE2b-256 checksum
How to use checksums
88959ba7db7884dc36d13110cb690c76ea36c01230d4a8a88f41feba75afdd1b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log

Release files / ait_native-1.1.3-cp311-abi3-manylinux_2_28_aarch64.whl

Download URL ait_native-1.1.3-cp311-abi3-manylinux_2_28_aarch64.whl
Size 22.8 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
451e7d5d22b842e3581a88fa5a30e7ff3ec4dc04f5e41bddbb4174e35cb0048f
BLAKE2b-256 checksum
How to use checksums
44fe6dd5432dd89aec6408cde93704ca8821e7ffc8df1717f0746383c5722d74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log

Release files / ait_native-1.1.3-cp311-abi3-macosx_11_0_arm64.whl

Download URL ait_native-1.1.3-cp311-abi3-macosx_11_0_arm64.whl
Size 21.6 MB
Tags CPython 3.11 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
2dc694214e6b25adc7a584a43914c417a376832def4d644643600d7a165e58b3
BLAKE2b-256 checksum
How to use checksums
68d79430ef580b8be687d3a35b0f871b3efab0899355054a1bfadd6471a52109
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log

Release files / ait_native-1.1.3-cp311-abi3-macosx_10_12_x86_64.whl

Download URL ait_native-1.1.3-cp311-abi3-macosx_10_12_x86_64.whl
Size 23.7 MB
Tags CPython 3.11 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
d0a71eb97c8380ee613e7607f8b4e50d0bf5964b6b549c3e8137e03ff10ccac6
BLAKE2b-256 checksum
How to use checksums
15adf3217f425ba6d9026c710a48280b039d5a2921b53cd3af329e86770f6d40
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page