Files
archie/docs/index.md
T
sam 4fe3bc13ee docs(development): checklists for every kind of change
docs/development/ holds one page per kind of change (settings, State Store
and persistence, task lifecycle, workflows and steps, event automation,
dashboard, agent execution and containers, processes and wiring, merging
work), each naming every layer the change must reach and pointing at the
document that owns the design. The docs build puts them in the development
set; docs/index.md and CLAUDE.md link them.

Also adds the container-profile case to the validator agreement test, the
check the profiles work skipped.
2026-09-24 21:03:34 +10:00

2.1 KiB

Archie

Event Driven Agentic Automation.

Archie is an agent platform that reacts to events. A forge issue, a signed webhook from any app you run, a message in a chat channel: each arrives as an event, a playbook decides what a matching event sets off, and the work happens in an isolated git worktree. GitHub and Gitea issues were the first case. A forge is now one event source among several, and a pull request one outcome among several.

Nothing about that path is wired to a particular forge, channel, or sender. Sources, the fields they carry, and the workflows they reach are configuration you add without touching code or restarting anything.

Start here

  • First playbook points an external app's webhook at archie, maps the fields of a real payload, and binds them to a workflow.
  • Architecture is the authority for settled design: the domain boundaries, the workflow engine, the task lifecycle, and the invariants that hold the whole thing together.
  • Development guides list everything a change of each kind must reach: settings, persistence, tasks, workflows, bindings, the dashboard, containers and process wiring.

What runs where

A deployment is a set of services, each owning one typed contract. The Gateway serves conversation turns and sessions, the Messaging Service runs the channels, the State Store owns the database outright, the dashboard is its own process, and archied admits work and drives each task through its workflow. gRPC carries the synchronous calls between them; NATS carries asynchronous fan-out. Agents execute in containers that receive a task-scoped credential, issued per task and revoked when the worktree is handed back.

Configuration lives at ${XDG_CONFIG_HOME:-~/.config}/archie/config.toml. Nothing in a working tree is load-bearing at runtime.

A note on these docs

This site is generated from the docs/ directory of the archie-core repository on every change to main. The repository is the source; this site is a view of it. If the two ever disagree, the repository is right.