# Running this distribution This archive contains five linux/amd64 binaries: Each service owns its data and reaches the others only through their gRPC contracts (or NATS, for task actions): | Service | Owns | Reaches | |---|---|---| | `archie-state-store` | tasks, events, control-plane settings, identities and access policies, installed packages (PostgreSQL) | nothing | | `archie-gateway` | conversations (PostgreSQL, its own tables) and every model call: chat turns, curators, MCP tools and sampling | State Store; daemon over NATS for task actions | | `archied` | dispatch: forge polling, the task queue, the embedded NATS broker, agent containers | State Store; Gateway | | `archie-messaging` | the Telegram, email and webhook channel connections | Gateway; State Store for channel settings | | `archie-ui` | the dashboard and the webhook capture receiver | Gateway; State Store | `archied playbooks lint` checks playbook binding YAML before it reaches the daemon, and `archied playbooks serve` is its language server for editors. Without `archie-messaging` the channels are simply absent, so it needs a unit of its own (`deployments/systemd-user-service.md`). `archie-agent` (the per-task sandboxed runtime) is **not** in this archive — it only ever runs inside the Docker container `archied` spawns per task, never as a host binary. Pull it from GHCR: `ghcr.io/samcharles93/archie-agent`. ## Quickstart 1. Pick a starting configuration. The full set of annotated templates lives in this repository's `deployments/` directory on GitHub () — `standalone.toml` (no forge, the simplest start), `single-forge-github.toml` and `docker-nats-stack.toml` cover the common cases. Every one needs PostgreSQL 18 at `database_url`. Copy whichever fits to: ```bash mkdir -p ~/.config/archie cp