Release License Summary

Read the current release license boundaries.

This page summarizes the current release-facing posture for the main ait surfaces. It follows the repository's legal drafts and release guidance, and it is explicit about where rights are permissive, reciprocal, commercial, or still intentionally bounded.

Release-facing summary
Not final legal advice
Updated May 19, 2026

Current surface summary

`ait` CLI and local trust layer

Release-facing posture: Apache-2.0. This is the inspectable local trust layer for plans, tasks, snapshots, and local workflow state.

`aitk` and `ait-agent`

Release-facing posture: Apache-2.0. The local read-only companion and baseline transport/runtime layer stay in the permissive public surface.

`ait-server` and `ait-worker`

Release-facing posture: AGPL-3.0-only OR LicenseRef-AIT-Commercial. Shared control-plane software is not treated as part of the permissive local trust layer.

`ait-web`

Release-facing posture: LicenseRef-AIT-Commercial by default. The main authenticated browser workflow surface is not currently described as a blanket public Apache grant.

Official website source and generated pages

site/** does not carry a blanket public software-license grant by default. Release-facing website copy may later receive a more explicit documentation/content grant when deliberately published as such.

Brand assets and logos

Brand assets are governed by trademark boundaries, not by source-code licenses alone. Software or content access does not automatically grant rights in the marks.

Important boundary rules

The repository root LICENSE is intentionally narrow; do not read it as a whole-repository Apache grant.
A monorepo build or one combined checkout does not create one uniform public license boundary.
If a package, file, or release-facing surface does not clearly state a public grant, do not assume broad reuse rights by default.
The official website domain is https://ait-native.dev, but domain control does not replace trademark policy or clearance work.

What is still intentionally explicit

The project is still careful about separating public local trust-layer software, reciprocal shared-control-plane software, commercial browser/admin surfaces, and official brand assets. This summary exists to make those boundaries legible instead of letting the repository layout imply more than has actually been granted.

Status note

This is a release-facing summary, not a final commercial agreement and not legal advice. Counsel-reviewed license instruments, notices, and trademark policy may refine these boundaries later without changing the current honesty rule: explicit grants should stay explicit.