Review agent actions before they happen

Return a clear decision before real systems change

Neura Relay checks proposed agent actions before execution. It returns proceed, revise, review, or stop so the next agent, product, or runtime knows what to do.

What Relay does

Before action
Risk checked first
Clear decision
Next step returned
Runtime control
Runtime stays yours

Review path

A proposed action becomes a decision before execution

01

Agent wants to act

Runtime prepares the proposed actionbefore anything downstream changes

02

Action described

Intent, actor, target, and policyevidence and risk are made explicit

03

Relay reviews it

Relay checks the proposed actionand returns the decision

04

System gets a route

System reads the decisionthen routes execution downstream

Sequence-aware routing

Relay reviews the next proposed action with the steps that led to it

01
Workflow sequence

The agent moves step by step

Every proposed action carries recent workflow contextfrom the steps immediately before the next change

02
Recent context

The next action is reviewed

Relay reviews the sequence before the next changeso the route reflects what just happened before

03
Decision route

The runtime gets a route

The runtime receives a route it can act oncontinue, revise, review, or hold with the reason

Routing result: the same next action can route differently when the preceding sequence changes the risk, while execution stays in the runtime

Review examples

Five local examples, one Relay mechanism

Start with one protected action

Turn one real workflow into a review path agents can use before execution

Pick one agent action that should be reviewed before it changes money, data, messages, or workflows. Relay checks it before execution and returns a clear route the next agent or system can use.

The first workflow produces one action family, one decision map, acceptance tests, and a traffic readout showing where stale approvals, changed arguments, review pressure, retries, or stopped actions appear.

Execution boundary

Relay returns the review decision. Runtime stays in control of execution.

Decision map

Map actor, tool, target, args, and policyConnect decisions to visible outcome refs

Acceptance tests

Test changed args, stale approval, replay routesConfirm outcome linkage before execution

Traffic readout

Show review pressure and stopped actionsSurface stale state, retries, failed outcomes

Run locally

Test the review flow before real systems are touched

Run the local review flow with synthetic actions. Relay creates review records, returns clear decisions, and keeps execution inside your runtime until you choose what happens next.

Run the review flow
git clone https://github.com/neurarelay/relay-action-card.git
cd relay-action-card
npm ci
npm run verify:decision-receipt-standard
node scripts/run-agent-action-gateway.mjs --dry-run --json

Refund approval example

A synthetic refund shows how Relay handles money-moving actions

Proposed

$420 refund

Agent proposes refund and customer notice

Decision

Owner review

Relay pauses the action before anything changes

Blocked

Payment held

No refund or customer message is sent

Open refund example

Synthetic only; no live payment or customer send

What Relay controls

Relay reviews the action and returns the decision. Execution stays with your runtime.

  • Relay reviews proposed actions before execution
  • Relay returns a clear decision the next system can use
  • Your runtime still controls the actual execution
  • Review checks guide the route, not certification claims
  • Examples use synthetic data and touch no real systems
  • Provider approval, Registry approval, and Neura execution are separate