* fix(postgres): scope OpenPRs to the caller's org A principal-carrying caller read every org's pr_open tasks. The query now honours the request scope; the daemon's unscoped review scan still sees all orgs. Issue: archie-core-kgxw.23 * fix(statestore): serve task logs only to the task's org ReadTaskLog and StreamTaskLogContent took a task ID and read the file with no org check. The State Store's task-log reader now confirms the task is visible under the caller's scope first; unscoped services read as before. Issue: archie-core-kgxw.24 * fix(postgres): scope ListPolicies to the caller's org Every org's policy text reached any principal-carrying caller. A scoped read now sees its own org's policies, plus instance policies when scoped to the system org. The engines and the lockout guard decide for every org, so they read the full chain unscoped: the dashboard engine loads without the request's principal and the guard lifts the caller's scope. Issue: archie-core-kgxw.25 * fix(postgres): scope identity reads to the caller's org ListIdentities and GetIdentity (and its alias fallback) returned every identity to any caller. A caller scoped to an org now sees only that org's members and assigned agents; the system org and unscoped services still see the whole instance. Issue: archie-core-kgxw.26 * fix(postgres): hide instance status from other orgs ListPresence, ListChannelStatus, ListApplyStatus and GetConfigSnapshot answered any org principal with instance-wide state. They now return nothing unless the request is unscoped or scoped to the system org. The dashboard reads the published config as itself, since its handlers project it for callers of every org. Issue: archie-core-kgxw.27 * feat(postgres): assign new agents an org and role at creation A bot or service account created through the API served no org until the next State Store boot granted it one. Create now assigns it to the org the request acts in with the developer role in the same transaction, so it is authorized immediately. Issue: archie-core-kgxw.14 * feat(edastore): create event records in a chosen workspace Sources are created in a workspace of the caller's org, the default one when none is named; event types and bindings take their source's workspace and mappings their event type's, the same rule the org backfill applied. The binding, mapping and event type contracts carry the workspace, the four list endpoints accept ?workspace=, and the Events page has a workspace selector that filters every step and picks where a new source goes. Issue: archie-core-kgxw.11 * feat(webui): authorize a record in its workspace The API built every access request with no workspace, so workspace policies and per-workspace roles never applied. A request naming a source, binding, mapping, event type or task now reads the record's workspace under the caller's scope and authorizes in it; tasks carry their workspace on the State Store contract for this. Issue: archie-core-kgxw.9 * feat(access): expose workspace environment to policies Policies can test resource.workspace.environment. The workspace attribute is the workspace entity, which carries its environment; the principal brings its org's workspaces from the State Store, so the dashboard and the daemon's run checks describe a resource's workspace without another lookup, and the daemon now authorizes runs in the task's or binding's workspace. Issue: archie-core-kgxw.10 * fix(webui): ask read_secret when a source secret is read Rotating a source's secret returns its value, but the route asked update, which every developer holds, so no policy could narrow who reads a secret. It now asks read_secret on the secret, which the shipped roles give admins and an object policy can narrow further. Issue: archie-core-kgxw.17 * refactor(org): delete the unused upgrade-incomplete sentinel Nothing returns org.ErrUpgradeIncomplete: the State Store finishes the org upgrade before it serves. Issue: archie-core-kgxw.18
Archie
Event-driven Agentic Automation
Archie connects events from your systems to agents that can investigate, reason, and act. Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
The aim is to automate work across system administration, incident response, network operations, service management, and software delivery. You define the process and the access it requires; agents work through its stages, using the context of each event to decide how to accomplish the task.
Archie is under active development and not every capability below is finished.
From an event to an outcome
Event source → Event type → Mapping → Binding → Workflow → Agent
| Concept | Purpose |
|---|---|
| Source | Receive events from a system such as a firewall, monitoring stack, service desk, or forge. Configure its endpoint and signing requirements. |
| Event type | Identify which kind of event arrived from its headers and payload. Infer a schema from captured events or a pasted example. |
| Mapping | Extract named, typed parameters from the event. Reuse a mapping across bindings and see how often it matches. |
| Binding | Select a workflow, filter the events that should trigger it, and supply its inputs from mapped values or constants. |
| Workflow | Define the stages of work, their inputs and outputs, and the agent profile to use. Call other workflows when work needs another specialist or process. |
| Agent | Execute the work in a container with the tools for its purpose, acting under its own identity and granted permissions. |
A single source can produce several event types. An event type can feed several bindings, and each binding can apply its own conditions. This lets the same incoming data drive different responses without building a custom integration for every workflow.
For example, a firewall sends a blocked-connection event. Archie identifies the event type and maps the source address and severity into an investigation workflow. A network investigator gathers evidence, assesses the activity, and returns its findings. The workflow could then call a separate containment workflow, subject to the permissions and approvals configured for that action.
The same model supports other processes:
- Infrastructure operations: A monitoring alert starts a diagnostic workflow to inspect a service, collect evidence, and propose or perform an authorised recovery action.
- Service management: An incoming request supplies the parameters for a triage, investigation, or fulfilment workflow.
- Software delivery: A forge event starts a review or implementation workflow with the repository's toolchain, validation steps, and pull request as its output.
These are examples of workflows you can build. Their behaviour comes from the workflow, tools, and access you configure.
Agents equipped for their work
An agent profile selects the container image and available tools. You can supply images with the software needed for a particular environment: network utilities for an investigator, operational tooling for a systems agent, or a language runtime and test framework for repository work.
Workflows declare structured inputs and can return structured outputs. They can run with a scratch workspace, require a repository, or accept one optionally. An investigation can finish with a report; a maintenance workflow can finish with an operational result; a coding workflow can finish with a pull request.
Workflows can also call other workflows and pass data between them. Each called workflow has its own run and agent profile. A caller can wait for the result or continue while the called workflow runs independently.
The archipelago marketplace's workflows/firewall package is an example of a
workflow that uses typed inputs, a network investigator profile, and no
repository.
Identities and controlled execution
Agents act as their own identities, with secrets and permissions granted to that identity. Runs receive credentials scoped to their task; event data supplies inputs and cannot grant access. Organisations, workspaces and policy-based access control are in progress.
Building and operating automations
The dashboard brings together event inspection, mappings, bindings, workflows, and task activity. The intended authoring path starts with a real payload or an example: identify its structure, map the fields you need, select a workflow, and approve the binding.
Sources default to signed delivery; an unsigned source must be explicitly approved. Binding changes require re-approval before they can dispatch work.
Run it on a server
You need x86_64 Linux with curl and unzip, Docker (agents and the bundled PostgreSQL run in containers) and a model: local Ollama or a hosted provider API key.
-
Install.
curl -fsSL https://raw.githubusercontent.com/samcharles93/archie-core/main/install.sh | bashIt downloads the latest release, verifies its checksum, installs the five services into
~/.local/binand runsarchied setup. Setup asks for the PostgreSQL URL (leave it blank for a bundled database with a generated password), a model provider and key, and a forge (choose none for event-driven automation only). Answers go to~/.config/archie/config.tomland secrets to~/.config/archie/env. The installer then starts the bundled PostgreSQL with Docker Compose and installs and starts systemd user units. Pass options with| bash -s -- --help;--from-sourcebuilds a checkout instead. Re-runarchied setupat any time to change the answers.Extensions run in an unprivileged user namespace. Ubuntu 23.10 and later block these by default; on such a host the installer prints an AppArmor profile that allows them for the Archie binaries only, to install with
sudo. -
Check it is up.
systemctl --user status archied archie-state-store archie-gateway archie-ui archie-messaging curl -s http://127.0.0.1:8485/health/detailed -
Open the dashboard at http://127.0.0.1:8484. It binds loopback by default; tunnel to it (
ssh -L 8484:127.0.0.1:8484 server) or see deployments to expose it with a token. -
Automate your first event with Your first playbook: send a webhook, map its fields, bind it to a workflow and watch the task run.
To write the config by hand instead, start from
deployments/standalone.toml (no forge) or
another deployment template.
Develop
task dev starts every service with Vite hot reload at
http://localhost:5173, using deployments/dev.toml.
task check is the quality gate; AGENTS.md lists its tools.
Documentation
Contributions follow AGENTS.md.
License
Copyright 2026 Sam Catlow. Licensed under the Apache License, Version 2.0. Third-party attributions are in NOTICE.