Agent / Control Center

ALBERTO REYES CASTRO · AI ENGINEERING

Reliable agents.
Deliberate control.

I designed and built a resilient multi-agent control plane.
Explore how it routes, verifies and recovers — without losing control.

A SYSTEM, NOT A SINGLE AGENT

Local + cloud execution.
Independent verification.
Human authority, always.

SANITIZED DEMOReal architecture. Simulated activity.
No live telemetry connection.

INTERACTIVE SYSTEM EXPLORER

Follow a task through the system.

ALL ACTIVITY IS SIMULATED
CONTROL PLANE / SCENARIO LABLOCAL SIMULATION

DEMO TOPOLOGY

Orchestration graph

6 WORKERS
Preparing local simulation…
EligibleActiveFencedUnknown

Paused · explore at your own pace

SIMULATED ROUTING

Preparing the local simulation. No telemetry connection.

HUMAN MERGE GATEClosedDemo has no write controls

Task lifecycle

SIMULATED · ONE GENERIC TASK

No task content, private identifiers or provider responses.

Decision timeline

SIMULATED STREAM

    REAL ARCHITECTURE · CONCEPTUAL BOUNDARY

    Observe the system.
    Keep the private side private.

    Resilience needs visibility. Visibility does not require publishing credentials, task content or operational access.

    PRIVATE OPERATIONSPUBLIC PRESENTATION
    1. Private harnessTasks · workers · policyRESTRICTED
    2. Read-only adapterOffline snapshot extractionNO CONTROL PATH
    3. Sanitizer / allow-listReject unknown fieldsFAIL CLOSED
    4. Public-state contractFinite aliases + aggregatesVALIDATED
    5. Public dashboardArchitecture, not operationsREAD ONLY
    01 / ROUTING

    Eligibility comes first.

    Capabilities, surface, health and policy constrain the route before an agent is selected.

    Why it matters

    An impressive model is still the wrong worker when its capability, availability or spend eligibility is wrong.

    02 / OWNERSHIP

    Failure has a boundary.

    Heartbeats reveal stale workers. Leases and attempt fences protect newer work from late results.

    Why it matters

    Durable state supports recovery. Circuit breakers and bounded retries prevent uncontrolled loops.

    03 / VERIFICATION

    Agents do not self-approve.

    Deterministic checks, an independent review role and a human merge gate separate output from authority.

    Why it matters

    Cross-family review is a design goal, not a measured claim in this simulation. Consequential changes require human approval.

    04 / SPEND SAFETY

    Recovery is not overage.

    Quota fences and distinct pools constrain fallback. Unknown quota stays unknown; paid usage is never implied.

    Why it matters

    No automatic paid refill or reset. Included-only eligibility requires provider-side verification outside this dashboard.

    DESIGNED & BUILT BY ALBERTO REYES CASTRO

    Engineering the space
    between agents.

    An AI engineering project focused on the hard parts of orchestration: ownership, failure, verification, spend safety and the boundary between automation and human authority.