The honesty page, machine-stamped.

Every number on this site drifts the moment it is typed by hand. This page is different: its facts are generated from the engine repository at deploy time and stamped with the exact commit they came from. When this page and another page disagree, this page wins — and the other page is a bug.

Stamp

What this page was generated from.

Engine repositorythe AiOverload engine repository — private until the public release; the commit below is verifiable against it then
Commitb35a48f
Commit date2026-10-08
Measured95 Go packages with source (test files excluded from the count)

The generator runs at deploy time against the engine repository; until the engine is public, the data is regenerated from a maintainer-side checkout and committed — never typed.

Workflows

What actually ships.

Served from registry/workflows/ — these exist in the tree at the stamped commit:

  • code-review-cascade
  • dev-review-loop
  • dev-review-loop-reflex
  • live-probe
  • manager-epic
  • postmortem

In examples/ — demos, not served from the registry:

  • echo-demo
  • environments-demo
  • flow-demo
  • profiles-demo
  • research-fanout
  • runworkdir-demo
  • scripts-demo
  • slot-demo
  • subworkflow-demo

Fleet

Providers and agents at the stamped commit.

Providers (registry/providers/):

  • mistral — cloud: magistral-small-latest, mistral-large-latest
  • unsloth — self-hosted: qwen38-27b

Agents (registry/agents/):

  • claude
  • developer
  • manager
  • qwen3.8-27b
  • reviewer

Claim status

Available, in progress, or planned — the curated list.

Claim Status Evidence
Event-sourced runs, aioctl replay re-verifies against the definition hash Available aioctl replay in the README; e2e through real NATS
MCP tool gate (tool.decide) at the gateway Available gateway guardrails hook; precision measured per tool
Gate on harness-native tools (Bash/Edit/Write) Planned open gap, named in docs/threat-model.md
Per-run credentials, minted and revoked In progress gateway-backed provider runs; LLM plane opt-in; subscription sessions inherit
Per-run Docker containers as the containment boundary In progress docker runtime wired on main; the shipped fleet still opts into the cli tier; container default + hardening (resource limits, cap-drop) in progress
NATS accounts + bus TLS In progress hardened profile, opt-in; default is loopback, unauthenticated
Ad-hoc A2A send gating In progress sends become single-turn runs; reflex gate defaults to none
Forge ingestion (issues become governed tasks) Available forgetasks.go — inbound adopt/fold; ingestion never dispatches
Generic ingress port (external events start governed runs) Available docs/ingress-port.md — declared sources, POST /hooks/<source>, dedup, trigger-matched runs
Business-app operational agents (declared app + .aio/ overlay) Planned designed; events → governed runs, outbound actions held
Integration-engine boundary (business vs integration workflows) Planned ADR tracked; AiOverload owns judgment, engines own plumbing
Dev-of-flows (governed agents building integration flows) Planned designed; issue → run → PR → CI → deploy on merge
Lifecycle write-back to the forge issue Planned no write path on main; tracked work
Forge-event fleet convergence In progress boot-time convergence today; event-triggered convergence tracked
Acceptance enforcement on forge-ingested rows In progress tracked; empty acceptance must never fold to done
Session distillation into the knowledge plane Planned design document only
Kubernetes driver Planned the platform-profiles destination; cli + docker today
Codex / Kimi / Gemma harnesses Planned Claude Code is the wired, CI-qualified harness
Resident agent runtime (manager + assistant personas) Planned decision document; implementation slices next

Missing evidence for a row? That is a bug — email johannes.girard@gmail.com and it gets fixed or the claim gets downgraded.

Read next

About

The claims are stamped; the last question is who stands behind them — one engineer, on purpose, building in the open.