AetherMoore
Work / agent runtime / public overview

Bounded agents moving through a visible route.

A model can propose work. The runtime decides whether that work has authority, gives it a narrow place to run, and records what happened. The route stays inspectable from the first task packet to the final receipt.

Route a request with Polly Read measured evidence
Route 01 / effect boundary

From request to receipt.

Each handoff narrows ambiguity. The model remains useful for planning and language; ordinary software owns identity, scope, execution, and the durable record.

Agent Bus path proposal ≠ permission
  1. 1

    Task packet

    The request becomes explicit work, inputs, and expected output.

    named intent + bounded context
  2. 2

    Capability check

    Identity, allowed tools, limits, and replay state are checked.

    allow / deny / quarantine / re-plan
  3. 3

    Leased worker

    Approved work enters a worker with a fixed scope and lifetime.

    no ambient authority
  4. 4

    Verified effect

    The host checks the result against the declared action and boundary.

    output + policy result
  5. 5

    Durable receipt

    The decision, action, result, and unresolved human work remain inspectable.

    traceable outcome
Route 02 / system surfaces

Different jobs, one contract.

The public pages describe the contract shared by the tools. Deeper repositories keep the implementation, tests, and operator details beside the code that produced them.

A / coordinate

Agent Bus

Coordinates task packets, workers, handoffs, and receipts across agent tools.

Open operator proof
B / command

GeoSeal CLI

Wraps commands in named scope, policy decisions, and evidence that can be reviewed.

Inspect source
C / learning

Clay research

Keeps training claims tied to controls, retention checks, and preserved checkpoints.

Open training lab
Route 03 / claim boundary

Proof travels with its limit.

Passing tests show the behavior exercised by those tests on that version. They do not create a general security guarantee or certify every surrounding component.

Patent status U.S. Application 19/691,526 was filed May 28, 2026, claiming priority to provisional 63/961,403. Filed; not examined.

Scoped campaigns

Named local test campaigns and the conclusions they support.

Evidence ledger

Operations snapshot

Publication-safe records with timestamps, boundaries, and required proof.

Operations evidence

Implementation

Public source remains the place to inspect code, tests, and change history.

GitHub