Beer Can Labs
Staff / Landlord
Operations

Landlord

Property Manager, Compute

Runs the building. The Landlord turns on compute when an agent is needed, brokers the agent’s turns, and turns it off again when the work is done. It builds and starts only what the Registrar has admitted.

Design rules
L1 to L6, §6.4
Contracts offered
1
Key flows
5

On the job

  • Wakes an agent from zero and queues a second message behind the running one
  • Brokers each turn over the /mailbox long-poll
  • Warms down and scales to zero
  • Pauses, kills and retires an agent in two stages

Not my job

  • Decide who may wake an agent. That is the Bouncer.
  • Decide whether the agent may spend. That is the Treasurer.
  • Decide what may be built. That is the Registrar.
Key product flows

What Landlord does, step by step

Flow

Wake from zero

createRun is the single door every wake passes through: Discord, webhook, schedule, queue, MCP and the console.

  1. A wake arrives. If its messageId already has a run, that run is returned with 200 and nothing starts.

  2. The Landlord asks the Treasurer. Over budget returns 402 and no compute starts.

    $Works with Treasurer· contractcheckStanding →

  3. If the agent already has an active run, the new message is queued and the reply is 202.

  4. The Landlord starts the agent’s task from its admitted image and tells the ingress the agent is starting.

    Works with Gatekeeper· contractGatekeeperIngress →

  5. In the container, the Secretary brings the notebook in.

    Works with Secretary· contractpullMind / pushMind →
Flow

Broker a turn

The agent never accepts an inbound connection. It asks for work.

  1. The agent long-polls /mailbox. The Landlord answers with the next message or holds the request open.

  2. When the turn ends, the agent posts its result through a run callback.

  3. Run state changes are published for live viewing.

    Works with Inspector· contractcreateInspector →
Flow

Warm down and sleep

Agents scale to zero. The ingress stays up.

  1. No work arrives for the warm-down window.

  2. The Secretary sends the notebook out.

    Works with Secretary· contractpullMind / pushMind →

  3. The task stops and the Landlord tells the ingress the agent is idle.

    Works with Gatekeeper· contractGatekeeperIngress →
Flow

Pause, kill and retire

Operational controls for an agent that must stop.

  1. An operator or an agent owner presses pause. The control plane checks the privilege first.

    Works with Bouncer· contractauthorize →Owners may wake, pause and resume their own agent.

  2. The run is blocked and compute is stopped. A paused agent is not woken by any trigger.

  3. Retirement runs in two stages (§6.4) and each stage is ledgered.

    Works with Auditor· contractLedgerStore / verifyChain →
Flow

Build and register an admitted commit

The build is injected into the Registrar’s admission. The Landlord supplies it.

  1. The Registrar pins the repository and commit, then calls the Landlord’s build.

    Works with Registrar· contractadmit →

  2. The build runs on the landing zone’s build service and pushes the image to its registry.

  3. The Landlord creates the agent’s identity and its task definition or Cloud Run job.

Contracts Landlord keeps 1 offered