Zettleinby Happy Sandboy
Menu

06 · Portable agent fleet

One app. A whole desk of specialists. Every one of them supervised.

Zettlein is not a single chatbot. It is a portable fleet of narrow AI agents — a broker, a lawyer, a banker, a developer liaison, a service coordinator — that talk to every party in a transaction. Each one drafts, negotiates and executes; a human in charge approves before anything binding leaves the building.

A · The premise

A transaction desk that fits in a pocket.

Portable

An app, not an office

Mobile-first, offline-tolerant

The whole desk travels with the user. Same thread on phone, tablet and web. Signature, escrow, and legal drafting reachable from a construction site or a Grab ride.

Plural

Specialists, not one generalist

Narrow, auditable

Each agent has one job, one prompt spec, one toolset, one reviewer. Failures are contained. Upgrades are surgical.

Supervised

AI proposes, human disposes

Approval-gated writes

Anything that costs money, binds a party, or leaves the platform is proposed by the agent and approved by a licensed human. The signature is always a person's.

B · The fleet

Every party in a deal gets a matching agent.

01

Broker Agent

Talks to buyers and sellers

Reads
Listings, comparables, saved searches, viewing history, agent calendar.
Writes
Leads, viewings, offers, counter-offers, buyer briefs.
Human approver
Licensed agent · offers ≥ threshold escalate

02

Lawyer Agent

Assembles and reviews contracts

Reads
Legal template DSL, jurisdiction pack, KYC status, prior clauses.
Writes
Reservation agreements, SPAs, addenda, redlines, clause diffs.
Human approver
Bar-licensed lawyer · every binding document

03

Banker Agent

Coordinates escrow, mortgage, payout

Reads
Escrow ledger, KYC/AML flags, payment rails (ABA, Acleda, Wing, Wise).
Writes
Payment intents, escrow instructions, remittance memos.
Human approver
Compliance officer · all fund movements

04

Developer Liaison

Talks to project sales offices

Reads
Project inventory, unit availability, price lists, reservation rules.
Writes
Reservations, unit holds, developer-side handover checklists.
Human approver
Developer sales manager · unit release

05

Service Coordinator

Books inspectors, movers, cleaners, valuers

Reads
Provider catalog, ratings, availability, SLAs, price bands.
Writes
Bookings, quotes, receipts, satisfaction check-ins.
Human approver
Ops lead · quotes above ceiling

06

Notary / Registry Agent

Files with public offices

Reads
Title records, cadastral IDs, tax IDs, official form catalog.
Writes
Registry filings, tax declarations, transfer request packages.
Human approver
Registered notary · every filing

07

Landlord Agent

Runs the rental side of the OS

Reads
Tenants, leases, deposits, maintenance tickets, rent ledger.
Writes
Leases, rent invoices, arrears notices, maintenance dispatch.
Human approver
Landlord owner · non-routine actions

08

Investor Agent

Briefs on yield, comps, portfolio

Reads
Portfolio, market data, macro indicators, projected cashflows.
Writes
Memos, offer plans, portfolio rebalancing proposals.
Human approver
Investor (self) · trades above mandate

09

Compliance Agent

Silent auditor across every thread

Reads
All writes, KYC state, sanctions lists, jurisdiction pack rules.
Writes
Holds, flags, audit records, SAR drafts.
Human approver
MLRO · every SAR and hold release

The fleet is open. Adding an agent is adding a spec — role, toolset, reviewer, approval matrix — not a new product.

C · Anatomy of one agent

Every agent is the same five-part spec.

 ┌────────────────────────────────  agent spec  ────────────────────────────────┐
 │ 1. ROLE       one sentence: who this agent is, whom it speaks to           │
 │ 2. READ SET   the exact Proassistly RPCs it may call to gather context     │
 │ 3. WRITE SET  the exact Proassistly RPCs it may propose (never call raw)   │
 │ 4. APPROVAL   matrix of {action → who approves → SLA → escalation}         │
 │ 5. GUARDRAILS refusal rules, tone, locale, consent, PII, jurisdiction pack │
 └──────────────────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
                       runs on the same Zettlein runtime
                       (memory, planner, tool loop, guardrails)

The runtime is shared. Only the spec changes. That is why we can add "Insurance Agent" or "Tax Agent" next quarter without touching the Broker or Lawyer.

D · Human-in-the-loop

Three approval tiers. Nothing binding slips through.

TierWhat the agent may doWho signsSLA
T0 · AutonomousRead, summarize, translate, propose, schedule, draft. No external effects.No one — logged onlyInstant
T1 · ReviewedSend messages to counterparties, book viewings, request documents, issue quotes below ceiling.Assigned professional (agent / ops)15 min business hours
T2 · SignedSign contracts, move funds, file with registry, release escrow, publish public listings.Licensed principal (lawyer / MLRO / notary)Same-day, hard block if missing

Every T1/T2 approval is a first-class Proassistly object: approval_id, agent proposal, human decision, timestamped signature, immutable audit trail. Regulators read one table.

E · How a deal actually moves

A concrete cross-agent choreography.

 Buyer ──▶ Broker Agent        "I want the BKK1 2BR"
              │
              ├─▶ proposes viewing ─────────▶ Licensed agent  ✔ T1 approve
              │
              ├─▶ drafts offer ─────────────▶ Broker Agent   auto-format
              │                                              │
              ▼                                              ▼
        Lawyer Agent  ◀── SPA request ──── Broker Agent
              │
              ├─▶ assembles SPA from DSL ──▶ Lawyer          ✔ T2 sign
              │
              ▼
        Banker Agent  ◀── escrow request ── Lawyer Agent
              │
              ├─▶ opens escrow, KYC ping ──▶ Compliance      ✔ T2 clear
              ├─▶ issues payment intent ───▶ MLRO officer    ✔ T2 sign
              │
              ▼
        Notary Agent  ◀── transfer request ─ Banker Agent
              │
              ├─▶ assembles filing pack ───▶ Notary          ✔ T2 file
              │
              ▼
        Service Coord ◀── handover ──────── Notary Agent
              │
              └─▶ books cleaning, movers ──▶ Ops lead        ✔ T1 approve

The buyer sees one Zettlein thread. Behind it, six agents pass a baton, and five humans sign in the right places.

F · Guardrails that make this shippable

Why regulators, licensees and insurers can say yes.

01

No unsupervised legal or financial acts

Every T2 write requires a natural-person signature stored against the approval_id. The AI never signs.

02

Licensure follows the human, not the agent

The Broker Agent proposes; the licensed agent is on record. The Lawyer Agent drafts; a bar-registered lawyer signs. Regulators already recognize this shape.

03

Jurisdiction pack, not hard-coded law

Rules for Cambodia, Thailand, Vietnam load as data. Adding a market is loading a pack, not shipping a new agent.

04

Every action is an event

proposed → approved → executed → observed. The full chain is queryable — for the user, the reviewer, and the auditor.

05

Consent and PII are enforced by the runtime

An agent literally cannot ask for a passport number until the envelope's consent.pii is true. Guardrails read flags, not prose.

06

Kill switch per agent, per tenant

Any agent can be paused instantly for one tenant, one jurisdiction, or globally. In-flight approvals fall back to fully human.

G · Where this fits the rest of the OS

Nothing new is invented here — it is composed.

Runtime

Same Zettlein runtime defined in Zettlein Flow. The fleet is specs on top.

Write path

Same /rpc/v1 Proassistly contract from Orchestration. Agents never bypass it.

Handoff

Same context envelope. A buyer talking to the Broker Agent can be introduced to the Lawyer Agent without repeating a single fact.

One sentence to remember.

Zettlein is a portable desk of narrow AI specialists — one per party in the deal — each doing the drafting, the outreach and the coordination, while the human in charge keeps the pen for anything that binds.