APACHE 2.0 · SELF-HOSTED · EVENT-SOURCED

Your agents.
Your rules.
Every decision
on record.

AiOverload is the control plane between an agent’s intent and its actions — deterministic workflows, governed tools, human approvals, and a run log you can replay.

  • Go + NATS JetStream
  • Default-deny MCP
  • Replayable by design
AiOverload / operatorRUN 9C4E71A8
LIVE WORKFLOW

dev-review-loop-reflex

1 HELD
  1. run.started

    8 steps · definition hash pinned

  2. step.completed

    inspect · acceptance criteria attached

  3. step.held

    review_2 · risk 0.81

    Review approves a push the gate cannot vouch for.
  4. awaiting decision

    Execution remains stopped.

$aioctl replay 9c4e71a8
6engine binaries
34wire contracts
3allowlisted MCP servers
GENERATED FROM ENGINE9e1fba0 · 2026-10-16

02 / ONE GOVERNED RUN

From intent to evidence.
No invisible steps.

Scroll the run or select a stage. The console follows the decision trail.

Nothing dispatches anonymously.

A workflow names its purpose, acceptance criteria, runtime, and tool grants before the first action.

intent: review the change
acceptance: verdict = PASS

Risk becomes a held state.

A small, non-generative model scores typed questions inside deterministic rails. Above threshold, the run parks.

step.held · risk = 0.81
gate unreachable → fail closed

Approval joins the record.

Approve with constraints or reject the step. The operator’s words become input on the same event log.

approval: review only
constraint: do not push

History is executable evidence.

Re-run the decision logic against the ordered events and pinned definition — not a flattened after-action report.

aioctl replay <run-id>
definition: verified
RUN / 9C4E71A8DEFINED

WORKFLOW MANIFEST

workflow: dev-review-loop-reflex
goal: reviewed, verified change
acceptance:
  - tests: pass
  - reviewer: PASS
tools: declared-only
definition: sha256:84f2…c91a
01 A run begins with a contract, not a prompt alone.

ILLUSTRATIVE INTERFACE · NOT LIVE TELEMETRY

03 / SYSTEM ANATOMY

One bus. Clear boundaries.
No hidden control plane.

Separate control, decision, execution, and observation surfaces compose over NATS JetStream. Every wire payload has a schema; every action has an owner.

04 / THE HUMAN DOOR

A pause you can operate.
A decision you can audit.

Try the decision model. Approval resumes only the held step; rejection keeps it stopped. Both outcomes join the illustrative event trail.

Interactive illustration — no engine connection or real run is created.

APPROVAL REQUIRED

review_2

HELD
Risk
0.81 / threshold 0.70
Requested action
Review and push branch
Proposed constraint
Review only — do not push
step.heldAwaiting an operator decision.

05 / A DIFFERENT JOB

Not another agent framework.

Use the framework you prefer. AiOverload owns the governed execution around it.

QuestionTypical agent setupAiOverload
What may run?Whatever the session can reachDeclared workflows and default-deny tools
Who approved risk?A chat message or an external queueA held step and a recorded operator decision
Where are the rules?Configuration across machinesReviewed manifests and GitOps state
What happened?Application logs and tracesReplayable, event-sourced run state

OPEN SOURCE / APACHE 2.0

Read the code. Run the log.
Judge the governance.

No customer theatre, invented benchmarks, or black-box promises. The project is new, small, and built to be inspected.

git clone https://github.com/JohGirard/AiOverload.git