/ architecture

System architecture

Architecture in
service of trust.

Hubu decides whether agent spend is allowed. Gongbu performs provider work. A narrow executor contract connects them without merging credentials, state, or failure domains.

FOLLOW ONE REQUEST

One governed request,
five steps.

Here is one billable request run by Gongbu, the first-party executor. Hubu, the control plane, decides and accounts. Gongbu, the execution plane, does the provider work. The agent never holds a provider key. Your own executor can take Gongbu’s place in step 4.

REQUEST LIFECYCLE
agent → hubu → gongbu → hubu
  1. 01 AGENT Agent asks for work The agent sends structured intent to Unified MCP, which authenticates to Hubu on its behalf. The agent holds no Hubu credential and never a provider key.
  2. 02 HUBU · CONTROL PLANE Check identity, policy, and budget Hubu confirms which registered agent is asking, evaluates every policy rule, and checks the active budget before any external work starts.
  3. 03 HUBU · CONTROL PLANE Authorize and reserve An allow decision records a spend authorization and reserves the authorized maximum as a budget hold.
  4. 04 GONGBU · EXECUTION PLANE Execute with the provider Gongbu claims the authorization, calls the provider with credentials only it holds, and keeps the receipt and artifacts.
  5. 05 HUBU · CONTROL PLANE Settle, release, or reconcile Hubu settles the actual cost, releases unused capacity, or keeps uncertain outcomes held for human reconciliation.

Example An image request reserves an illustrative $0.05 maximum. Gongbu runs it and reports a $0.03 receipt. Hubu settles $0.03 and releases the remaining $0.02.

Provider keys live only in the executor, never with the agent or Hubu. Hubu never calls a provider, and no executor runs billable work Hubu has not authorized.

FULL SERVICE TOPOLOGY

One product.
Two runtime planes.

Every process and owned store, for readers who want the detail. Humans and agents enter through separate surfaces. Hubu governs every billable operation; Gongbu executes only approved work and keeps provider operations isolated.

SERVICE TOPOLOGY
processes · services · owned state
HUMANOwnerpolicy · budgets · review
HUMAN SURFACEHubu CLIadministration + stack launcher
AGENTAgent harnessstructured intent
AGENT SURFACEUnified MCPHubu first → Gongbu after allow
client-owned processes
AGENT ADAPTER PROCESS

Unified MCP

Route and recover without merging backends

ROUTERStatic tool ownershipone tool → one backend
HUBU CLIENTGovernance + authorizationHubu endpoint + credential
GONGBU CLIENTProvider catalog + executionGongbu endpoint + credential
ADAPTER WORKERDurable operation workersubmit + observe acknowledged work
ADAPTER-OWNED STATEOperation registry SQLiteharness identity · intent · recovery status
Server-bound CLI + Hubu client ↓administration · governance · authorization
Gongbu client ↓catalog read · execute after allow · observe · retrieve artifacts
CONTROL PLANE

Hubu

Govern and account

ENTRY SERVICEHubu HTTP APIauthentication · capabilities · routes
Registrationidentity + ownership
Policy enginerules + evaluation
Budget lifecycleholds + claims
Ledger + reconciliationfinancial audit
OWNED STATEHubu SQLitegovernance · authorizations · budget outcomes
authorization snapshot executor contract Gongbu resolves · claims · settles/releases through Hubu
EXECUTION PLANE

Gongbu

Execute approved work

ENTRY SERVICEExecution APIcatalog · validate · persist · schedule
Temporal workersubmit once + resume poll
Provider adaptersisolated credentials
Provider contractsvalidated targets + pricing
Artifact servicenormalized outputs
OWNED STATEGongbu SQLiteexecutions · checkpoints · receiptsOWNED FILESArtifact rootnormalized provider outputs
EXTERNALProvider APIsmodel work + vendor receipt

Unified MCP, Hubu, and Gongbu run as separate processes. Adapter state, governance state, execution checkpoints, credentials, artifacts, and failure domains remain separately owned.

COMPONENT DRILLS

Start with the control path.

Four focused drills cover identity, decisions, money, and approved execution. Each one keeps the core model, responsibilities, and source together.

IDENTITY & RELATIONSHIPS

One owner, four agent records

Registration resolves a stable agent lineage, its versions, one spending account, and a fresh session under the active human owner.

INTERNAL FLOW

    Responsibilities

      Source & runbooks

      01

      Govern synchronously.

      Policy and budget decisions happen before external work starts, with canonical scope and retry-safe identity.

      02

      Execute separately.

      Provider credentials, submit-once workflows, operation checkpoints, artifacts, and recovery stay inside Gongbu’s execution failure domain.

      03

      Reconcile explicitly.

      Receipts and settlement evidence tie execution back to authorizations without copying provider state into Hubu.