ENVOY is a governed autonomous computer-use system. It operates browser sessions on behalf of an authorised principal — navigating web interfaces, extracting structured information, and submitting forms — in the same way a human operator would, but with complete machine-readable audit of every action taken.

Every interaction is decomposed into typed action classes (navigate, extract, authenticate, fill, submit), each evaluated against a governing doctrine before execution. The result is a capability that can act at machine speed while remaining fully accountable: every click, every keystroke, every decision is logged and signed.

ENVOY is built for use cases where a human would otherwise need to sit at a terminal. Compliance evidence collection, regulatory filings, corporate registry lookups, procurement platform interactions — wherever a process requires a user and a browser, ENVOY can be that user, with the organisation's rules hard-wired into the session. See /identity.json for technical metadata on this deployment.

Every ENVOY session operates under Standing Orders — a versioned governance document that specifies which action classes are permitted, which require human approval, and which are prohibited outright. Standing Orders are not soft configuration; they are enforced at runtime by the session orchestrator and cannot be overridden by the session itself.

Actions are evaluated through a three-tier autonomy model: Tier 1 actions are fully autonomous (navigate, read), Tier 2 actions are autonomous with logging (form fill, extract), and Tier 3 actions are prohibited in Phase A (submit, authenticate with side effects). Each action passes through the ROE Gate — a multi-step evaluation that checks Standing Orders authorisation, risk classification, confidence threshold, and reversibility before any action executes.

Every gate decision and every action outcome is written to a forensic CHRONICLE audit chain — a cryptographically-linked ledger of events, hash-chained and signed, that cannot be retrospectively altered. The chain begins at session commission and closes at session completion. Any break in the chain is detectable and surfaced in the audit endpoint.

ENVOY is a Foundry primitive — one of the core agent capabilities that sit alongside FULCRUM, the Foundry orchestration layer. Where FULCRUM routes intelligence and manages multi-agent workflows, ENVOY operates at the interface boundary: it is the capability that acts on external systems on behalf of the principal.

ENVOY was built through Genesis Run GEN-20260517-001, the first full run of the Foundry genesis methodology — a structured build protocol for sovereign AI capabilities. The genesis run produced the complete Phase A implementation: session orchestration, gate wiring, CHRONICLE signing, standing orders enforcement, and this deployment.

ENVOY is built for organisations that need to delegate digital tasks to AI without surrendering control. Here is what that looks like from a commander's perspective.