The set of agent-facing artifacts kept current in a repository: AGENTS.md, the codemap, conventions, and optional architecture facts. It is what AI coding agents read to plan work against your actual codebase instead of a stale picture of it.

One file in the context layer. Kontrua maintains four: AGENTS.md, the codemap (docs/CODEMAP.md), conventions (docs/CONVENTIONS.md), and architecture facts (docs/architecture.facts.json). Each is configured under the context section of the repo config.

The agent orientation file at the repository root, following the emerging AGENTS.md convention: what the project is, how to build, test, and navigate it. Enabled by default.

A map of the repository written for agents: modules, entry points, and dependencies. Default output: docs/CODEMAP.md. Enabled by default.

Code patterns observed in the repository, each backed by cited examples from the code. Default output: docs/CONVENTIONS.md. Enabled by default.

Machine-readable JSON facts about the codebase, extracted deterministically - no LLM involved. Default output: docs/architecture.facts.json. Opt-in.

How far the context layer trails the code: the number of commits since the context last matched HEAD. Fresh context means agents plan against the repository as it is, not as it was.

A human-readable document rendered from the same understanding of the code as the context artifacts: README, API reference, architecture doc, or changelog. Doc views remain fully supported as a secondary output.

One end-to-end context update cycle. Created when a trigger fires, it tracks progress through pending, running, success, and failed states and stores all generated output.

A specialised AI worker responsible for one artifact. Kontrua runs agents for the context artifacts (AGENTS.md, codemap, conventions) and the doc views (README, API reference, architecture, changelog). Each one reads the diff and your template to produce updated content; architecture facts are generated deterministically without an agent.

A Markdown document that defines the structure, tone, and scope of a generated artifact. Templates are org-scoped and assignable to multiple repositories.

The branch that Kontrua monitors for events. Only pull requests targeting (or merged into) this branch trigger runs. Defaults to the repository's default branch.

The event that kicks off a run: PR approved, PR merged, CI API call, or manual.

The internal name for a run record. Stores the commit SHAs, trigger type, status, progress log, and output artifacts.

A single generated file produced by a run - for example the updated AGENTS.md or README.md. Each run can produce one output per enabled artifact.

A run that could not be executed immediately because the monthly quota was exceeded. It is stored and retried automatically when capacity is available.

The configuration file for Kontrua. Controls which context artifacts and doc views are enabled, output paths, templates, and output mode. Used by both the CLI and SaaS dashboard.