Skip to content
Archiedocscookbooknewssign in

    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. The model below describes the project's direction, with implementation progressing across event automation and organisation access control.

    The event automation design and organisations and access design describe those capabilities and their delivery stages.

    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, types parameters from the event to use across bindings.

    Workflow

    Define the stages or work, their inputs and outputs, and the agent profile to use. Call other workflows when work needs another specialist or process.

    Agent

    Execute work in a container with the tools for it’s purpose, acting against it’s own identity and permissions.

    A 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, when a firewall sends a blocked-connection event, Archie:

    • Identifies the event type
    • Maps the source address and severity into an investigation workflow.
    • A network investigator agent 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 operating 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 just some of the examples of workflows that you can build and their behaviour comes from the workflow, tools, and access you configure.

    Start here