ait Local
The trust layer for planning, local tasks, snapshots, and one honest local land loop.
Services
See how the services fit together.
Services at a glance
ait-agent
The runtime bridge for external channels and long-lived transport surfaces.
ait-server
The shared workflow authority for review, policy, and coordinated state.
ait-web
The authenticated browser workflow surface, not the official public learning site.
ait-worker
The async execution support layer for shared and queue-backed workflow work.
Three core capabilities
The surface map matters, but the capabilities matter more. This is the compact functional picture new visitors usually need next.
Markdown-first planning
Shape work in Markdown first, sync plan lineage, then derive the right task or compact DAG instead of jumping straight into untracked edits.
Review-ready workflow objects
Move from task and change to snapshots, patchsets, review, attestation, policy, and land with the execution record kept explicit.
Local-first, shared when needed
Start with the local trust layer, then expand into shared agent, server, worker, and web surfaces only when broader coordination adds real value.
Why the services page does not come first
The services page explains the wider surface map, but it is not the first learning path. New users should first learn the local loop and how to direct the agent.
Local trust layer
Start with the local workflow when the goal is to learn the rhythm, shape work into a clear first plan, open the honest local task, and land one slice without shared infrastructure.
Shared control plane
Move to `ait-agent`, `ait-server`, and `ait-worker` when the work needs shared review, shared policy, runtime delivery into outside channels, or a team-visible control plane.
Browser workflow surface
`ait-web` is the authenticated browser workflow surface for review, admin, and progress. It is not the official website, and it should not be confused with the first-run learning path.