Skip to content
Sahil Swain
← All work
Personal projectPrototype / active engineering work

AI Agent Control Plane

Personal engineering project

A visual control surface for an agent framework that separates model reasoning from framework control: plan, verify, request human decisions where required, execute, and audit.

What problem existed?

AI agents that call tools and take actions are hard to trust when the model's reasoning and the system's control logic are tangled together. There is no clear place to see what the agent intends to do, whether it was verified, or why it was allowed to run.

Context / constraints

  • Personal engineering project informed by my broader AI Agent Framework work.
  • The AI Agent Framework itself is not published in this portfolio, so it is not publicly inspectable here.
  • Designed as a control surface for agentic systems rather than another chat interface.

What was built

  • A control-plane interface, demonstrated through the scripted prototype on this page, that surfaces agent/task state, planning, verification, human decision checkpoints, execution, and audit history as first-class objects.
  • In the prototype, a strict separation is demonstrated between model reasoning and framework control: the framework — not the model — decides what the model is allowed to do.

Architecture

  • The core principle: the model is not the framework. The framework controls the model.
  • Proposed operations flow through explicit states — planned, verified, approved or rejected at human checkpoints where required, executed, and recorded in an audit trail.
Modelreasoning onlyPlannerobjective → opsPolicy / Verifyscope · riskHuman checkpointapprove / rejectExecutorAudit trailproposalcandidate opverifiedapprovedrecordedrejectedThe model is not the framework. The framework controls the model.

Scroll horizontally to inspect the diagram at a readable size.

Key engineering decisions

  • Model output is treated as a proposal in the prototype workflow, never as an instruction.
  • Human decision points are explicit states in the workflow, not implicit prompts.
  • In the prototype, every operation is recorded so the demonstrated behavior is auditable after the fact.

Validation / tests

  • The prototype's scripted state cycle (operation proposed → verified → human checkpoint → executed → audited, or rejected at the checkpoint) is covered by deterministic unit tests in src/lib/control-plane.test.ts.

What is deliberately not claimed

  • Not a deployed commercial product.
  • No client usage, users, or business outcomes are claimed.

Interactive demo — runs directly on this page

AI Agent Control Plane deterministic prototype

Control plane status: Standby.
agent-control-plane
Standby
Deterministic personal prototype · scripted states · no live model, policy engine, or tool integration

Plan · task #4471

  1. Parse objective into operations
  2. Resolve tools & constraints
  3. Propose operation op-4471
  4. Verify against policy
  5. Request human decision
  6. Execute under supervision

Verification

Policy check
—
Scope check
—
Risk level
—

Human decision checkpoint

op-4471 requests: write report to workspace

Audit trail

  • op-4468 · read-only query · executed · verified
  • op-4469 · write outside scope · rejected by policy
  • op-4470 · approved by operator · executed

Source

  • Source repository — Not yet publicly available — no verified public repository exists.

Want this kind of system built for your workflow?

Start a project