# Running this distribution This archive contains six linux/amd64 binaries: - **`archied`** — the resident daemon: polls your forge for assigned issues and dispatches them into sandboxed `archie-agent` containers. It serves no dashboard: the web UI is `archie-ui`'s process (UI cutover, `archie-core-8cda.5.4`). - **`archie-ui`** — serves the operator dashboard and the webhook capture receiver, dialing the Gateway and State Store gRPC contracts. Reads only `[services.*]`, `[web]` and `[capture]` from the shared `config.toml`. - **`archie-gateway`** — serves the chat (`ChatContract`) surface `archied`, `archie-ui` and `archie-messaging` dial. Runs as its own process; `archied` never embeds a gateway. - **`archie-messaging`** — serves the Telegram, email and webhook channels, dialing the Gateway for the chat contract and the State Store for the stored channel settings. `archied` runs no gateway for those channels, so without this process they are simply absent — and nothing logs an error (`archie-core-1c01`), which is why it has a unit of its own in `deployments/systemd-user-service.md`. - **`archie-state-store`** — owns the single `archie.db` SQLite file behind a gRPC contract. `archied` and `archie-gateway` are gRPC clients of it, not owners of the database. - **`archie-playbooks`** — standalone CLI to lint playbook binding YAML before it reaches `archied`. `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 () — `single-forge-github.toml`, `multi-forge-github-gitea.toml`, `local-ollama-standalone.toml`, and `docker-nats-stack.toml` cover the common cases. Copy whichever fits to: ```bash mkdir -p ~/.config/archie cp