These documents define agentic-kit's shared language, domain boundaries, and invariants. They describe the current system unless a section is explicitly marked as future work.
| Document | Purpose |
|---|---|
| Ubiquitous language | Canonical meanings used across code, CLI, ADRs, and documentation |
| Context map | Bounded contexts, ownership, and relationships |
| Integration management | Hosts, inference providers, bindings, capabilities, lifecycle, facts, and ownership |
| Routing and orchestration | Activities, routes, leadership, escalation, projections, and canonical ak run execution |
| Live Sessions | Evidence acquisition, live-session aggregates, replay, and dashboard delivery |
- Domain documents define stable terms, boundaries, state, and invariants.
- Architecture decision records explain why consequential decisions were made.
- User guides such as Providers and hosts explain how to operate the CLI.
- Source and tests enforce the model. When documentation and behavior disagree, treat that as drift to resolve rather than silently redefining a term.
A change that introduces or changes a domain concept should:
- name its owning bounded context;
- use or extend the ubiquitous language;
- preserve the context's invariants, or add an ADR explaining the change;
- add executable coverage for new invariants; and
- update operational documentation when user-visible behavior changes.
The GA model keeps host enablement under integrations.hosts, integration ownership under
integrations, and activity intent under top-level routing. These persisted locations do not
change the canonical distinction between a host and an inference provider.