sam 3014db85e7 Fix/workflow eda audit (#1627)
* fix(webui): accept the merge task action

The action whitelist omitted merge, so the dashboard's Merge button on a
pr_open task was refused with 400 unknown action.

Closes: archie-core-slpoz

* fix(workflow): give each parallel branch its own outputs

Branches shared the task's Outputs map, so concurrent declared-output
writes raced (or were lost when the map started nil). Each branch now
writes a copy; join merges new outputs in branch-name order and refuses
one written by two branches as a second write.

Closes: archie-core-3a7w2

* fix(postgres): dispatch captures oldest first and keep pending ones

ListUndispatchedCaptures ordered newest first and listed captures no
binding can match (failed HMAC), so sustained intake starved older work
and bad signatures held the batch. It is now oldest first and lists only
dispatchable captures. Count retention no longer evicts a capture that
is still pending for an armed binding. The daemon lists only sources
with an enabled workflow, so captures waiting on a disabled one do not
hold the oldest-first batch.

Closes: archie-core-2et4b, archie-core-o0s0z

* fix(ui): refuse renaming a workflow onto an existing id

Saving upserts by id, so editing a workflow's id to another workflow's
id removed the open one and overwrote the other. The editor now refuses
that save and says why.

Closes: archie-core-wpoz8

* fix(workflow): reject unknown step settings at save

Step factories decoded settings with yaml.Node.Decode, which drops keys
it does not know, and settings-less steps ignored settings entirely, so a
misspelt key (readOnly for read_only) saved and silently did nothing.
Every factory now decodes strictly and settings-less steps refuse
settings; ParseDefinition runs the factories, so the save refuses them.

Closes: archie-core-8b5nk

* fix(postgres): keep a stored capture when its prune fails

InsertCapture committed the capture, then returned the prune's error, so
intake answered 500 and a sender without a delivery header retried into
a duplicate capture and a duplicate dispatch. A failed prune is now
logged and the stored capture's id returned.

Closes: archie-core-3miuh

* fix(crondelivery): fail and advance a job no runner can deliver

Router.Run returned nil for a kind with no runner, so the engine reported
a successful run while the schedule never advanced and the job fired on
every tick. The run now fails with the refusal, which the engine reports,
and the schedule advances (a one-shot is removed). The router's own
refusal event is gone with it.

Closes: archie-core-s6ahh

* fix(taskactions): stop the runs of cancelled callees

CancelExecution cancelled a caller's waited-on callees in the store, but
only the caller's run was stopped, so callee containers ran to the end.
CancelExecution now returns the callees it cancelled (nested included)
in place of the step ids nobody read, and every cancelling action stops
their runs too.

Closes: archie-core-9labz

* fix(workflow): treat a zero json.Number as false in when

Task inputs and step results decode numbers as json.Number, which truthy
did not unpack, so when: inputs.count held for a count of 0.

Closes: archie-core-uv270

* fix(webui): read a workflow's runs with a workflow-filtered page

The workflows page and the canvas run picker filtered the newest 100
tasks of every workflow client-side, so on a busy instance a workflow's
older runs were invisible. GET /api/tasks takes a workflow filter, carried
through the State Store's Tasks request to the query, and both views ask
for the selected workflow's runs.

Closes: archie-core-tpiw1

* fix(ui): load the restored workflow into the editor

Restore Defaults saved the shipped definition but left the open draft in
the editor, still marked unsaved, so a later save re-applied it. The
editor now reloads the restored definition.

Closes: archie-core-85e7w
2026-10-12 03:20:00 +11:00
2026-10-11 04:23:10 +11:00
2026-10-12 03:20:00 +11:00
2026-10-12 03:20:00 +11:00
2026-10-12 03:20:00 +11:00
2026-10-11 04:23:10 +11:00
2026-10-11 12:17:31 +11:00

Quality

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.

  1. Install.

    curl -fsSL https://raw.githubusercontent.com/samcharles93/archie-core/main/install.sh | bash
    

    It downloads the latest release, verifies its checksum, installs the five services into ~/.local/bin and runs archied 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.toml and 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-source builds a checkout instead. Re-run archied setup at 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.

  2. 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
    
  3. 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.

  4. 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.

S
Description
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.
https://archie.catlow.cloud
Readme Apache-2.0
133 MiB
0 Stars 1 Watchers 0 Forks
2026-11-10 10:01:23 +00:00
Languages
Go 76.8%
Vue 13.1%
TypeScript 7.8%
JavaScript 1.2%
Shell 0.6%
Other 0.4%