Audience: Contributor
The user’s request becomes steps. Code checks each step against the project. The model is asked only to break down the request, to fill a design, or to summarize a result. Everything is recorded.
The pipeline and working copies are the only path. Older ReAct / promote / draft flows are retired.
| Color | Who |
|---|---|
| Blue | Rules (deterministic code) |
| Amber | Model |
| Green | Person |
| Term | Meaning |
|---|---|
| Step | One unit of work in the run |
| Question / approval | Person input before a step continues |
| Run | One private change; page edits land as revisions, staged work may still offer Apply/Discard |
| Working copy | The user’s pending edits; Save shares them with teammates |
| Open draft | Caller’s private named page revision until Publish |
| Publish | Freezes the shared page tip from the caller’s open draft |
| Ability | What a plugin exposes to the assistant |
Built-in operations and plugin agent blocks are registered from the agent contract registry in the LokAkrt monorepo (common/server/src/agent-contract/tool-contract-registry.ts). The live built-in tool inventory is AI tools (AgentToolRegistry). Plugin authors declare abilities as described in Make a plugin usable by the assistant.
The full architecture — working copies, resolve, catalog, walk, verify, recording, model purposes, and acceptance goals — is server/ai/architecture-rules.md. Product loop and credits: server/ai/README.md.
The wiki does not host their full text. Former ng/*.md plan files were folded into architecture-rules.md and may be deleted.
$choose / $llmVariance)