Skip to content
azizu06Public

About

A 3D back office where AI agents work real finance seats and every limit is enforced on the server. Hyphenate track prize, Cal Hacks 13.0.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

Backrooms office screenshot showing seven finance roles, invoice handoffs, Dana's passkey desk and the audit wall

Backrooms

Cal Hacks 13.0: Hyphenate track prize out of 652 projects

Your back office, with every decision in view.
AI agents handle finance work for a small business. A human approves anything outside their limits.

Cal Hacks 13.0 Claude Agent SDK SpacetimeDB Sandbox and testnet payments

Watch the demo · Devpost · Capabilities · Architecture · Run it · Evidence

Real application screenshot from our Devpost gallery. Company data is synthetic; bank and credit integrations use sandboxes, and x402 uses testnet.


Late invoices, vendor bills and bank-detail changes pile up when a small business has no finance team. Backrooms gives that work a place: a 3D office where specialist agents pass cases between desks, ask the owner for approval and leave a record you can question.

Built at Cal Hacks 13.0 by Abduaziz Umarov, Tomiwa Aluko, Diego Mendoza and Anthony Terry. The published project story and demo video show the team's presentation. This repository contains the implementation, setup guides and scoped test receipts.

From Inbox To Audit Wall

A client asks to split an overdue invoice into seven payments, with 15% up front. The Collections agent can discuss the request, but it cannot grant itself a larger limit. Policy escalates the plan to Dana, the owner. Her passkey decision lets the call continue with the exact approved terms. A payment link carries that amount to the pay page; reconciliation checks the deposit against the invoice.

Meanwhile, a lookalike vendor email asks to change bank details. Payables holds it for review before any bank effect. Both stories end on the same audit wall, with the rule, decision and evidence attached. The office makes the handoff visible. It never authorizes it.

Claude talks, code decides. Emails, invoices and client speech are data. Models handle language; code controls limits, approvals, payments and the record.

What You Can Do

Experience How it works
Watch the office work Explore the React Three Fiber office or its floor plan. Start the workday to see invoice cases move through the existing dispatcher. Office · Agent handoffs
Negotiate within a badge Cartesia handles the collections conversation. Server tools enforce disclosure, consent, identity before amount, calling hours, opt-out and bankruptcy stops. Voice setup and limits
Approve with a passkey Requests outside an agent's limits go to the owner. The server verifies a WebAuthn assertion; voice cannot approve. Approval flow
Inspect a suspicious invoice The inbox and Attack Lab expose policy holds for lookalike senders, missing POs, duplicates and bank changes. Attack demo
Pay and reconcile Approved plan amounts bind the payment link. Nessie sandbox deposits require an exact match; an optional Coinbase CDP wallet pays an approved invoice using x402 on Base Sepolia. Nessie · x402 testnet
Ask why Answers cite hash-chained audit entries. Citation validation rejects invented entries. Audit voice
Switch models off The global OFF switch stops model work while deterministic policy checks keep enforcing holds. LLM control

The Whole System

The browser shows the work. The orchestrator coordinates it. Policy and passkeys control what can happen. SpacetimeDB records the transitions.

flowchart TB
  subgraph Browser[Browser]
    Office[3D office and audit wall]
    Human[Owner passkey controller]
    Pay[Client pay page]
  end
  subgraph Server[Server]
    Web[Next.js web and API routes]
    subgraph Orchestrator[TypeScript orchestrator]
      Agents["One dispatcher: 7 Claude Agent SDK roles<br/>Intake, Extractor, Vendor, Payables<br/>Collections, Reconciler, Auditor"]
      Gateway[Tool gateway and finance services]
      Policy[TypeScript policy engine]
      Verify[WebAuthn approval verifier]
      Router[Model router and OFF switch]
    end
  end
  State[(SpacetimeDB tables and reducers)]
  Voice[Cartesia collections voice agent and role handoff TTS]
  Cloud[Claude cloud models]
  Local[GX10 local models via Ollama]
  Nessie[Nessie sandbox bank]
  CRS[CRS sandbox checks]
  Apify[Apify Client Health Check Actor]
  CDP[Coinbase CDP server wallet and x402]
  Base[Base Sepolia test USDC]

  Office --> Web
  Human --> Web
  Pay --> Web
  State -. subscriptions .-> Office
  Web --> Agents
  Web --> Gateway
  Web --> Verify
  Agents --> Gateway
  Agents --> Router
  Gateway --> Policy
  Verify --> State
  Gateway --> State
  Agents --> State
  Voice <--> Gateway
  Agents --> Voice
  Gateway --> Nessie
  Gateway --> CRS
  Gateway --> Apify
  Gateway --> CDP
  CDP --> Base
  Router --> Cloud
  Router --> Local
Loading

Seven roles share one dispatcher and one handoff store. Role tools expose only the operations that role needs. Handoffs validate their destination and evidence references before the dispatcher commits them. Runtime and role contracts.

The gateway checks policy and trusted state before external effects. Approvals require the server's passkey verifier. SpacetimeDB reducers own state transitions, while the office subscribes and renders. Some gateway and finance repositories remain in memory even when the StateStore uses SpacetimeDB. State boundaries.

The GX10 serves local models for routine work, including extraction. Cloud routes, fallback labels, budgets and the OFF switch remain explicit. Local inference is separate from the Cartesia phone path. Model router · GX10 evidence.

Run It

You need Node.js 22+ and pnpm. The repository pins its package-manager version in package.json.

git clone https://github.com/azizu06/backrooms.git
cd backrooms
pnpm install
pnpm -r build
pnpm -r test

Start without credentials

pnpm dev:web

Open localhost:3000/office for the office preview with labelled simulated state. No database or provider keys are needed for this mode.

To run the deterministic server loop in the terminal:

pnpm demo:core

This exercises policy, approval verification, payment matching and audit with scripted call turns, a software test authenticator and fake bank HTTP. It makes no model or sponsor requests. Exact flow and adapter boundaries.

Connect the demo host

The full host needs the SpacetimeDB CLI and its local runtime, plus the setup in the demo runbook. pnpm demo:up starts owned local state by default; Maincloud is opt-in. The runbook covers ports, operator access, passkey enrollment, reset and shutdown.

Copy .env.example to ignored .env.local only when configuring integrations. Keep credentials server-side. Follow each provider's guide rather than enabling every adapter at once:

Integration Setup
State and office subscriptions SpacetimeDB module · Host runbook
Claude and GX10 Model router · Agent runtime
Cartesia calls and handoff voices Cartesia · Call evidence
Human approval Passkey setup
Sandbox payments Nessie · Pay and reconcile
Coinbase testnet payments CDP wallet and x402, with Mac Keychain credentials
Public-web checks Apify Actor

A configured service is not a completed call or payment. Use only authorized test targets and keep sandbox, cached and simulated labels visible.

The Receipts

Evidence What it establishes
Published demo and project story The team's recorded presentation and description. Reproduce individual integrations with their own runbooks and receipts.
Maincloud office parity 20/20 request-to-frame samples below one second using hosted SpacetimeDB and a Mac browser. No live phone or bank request occurred in that test.
Coinbase CDP receipt An approved 0.01 test USDC invoice paid through the named CDP wallet and public x402 facilitator on Base Sepolia, with independent on-chain checks. No mainnet or real-money payment.
Offline scoreboard Scripted code-path results and recorded extraction evidence. Its denominators and unexecuted operations stay separate from live-provider claims.
Core demo A reproducible network-free loop through policy, test approval verification, payment matching and hash-chain audit.
Sponsor checklist Integration-by-integration evidence, outstanding gates and claim limits.

Backrooms is a hackathon prototype using a synthetic company. The sections below retain the integration boundaries; a passing scripted test does not establish a new phone call, human passkey tap or real settlement.

Inside The Repo

Area Entry point Guide
Office and human UI web/ Office view · Replay
Agent runtime and tools orchestrator/src/agents/ Seven roles · Model control
Policy policy/ Product spec · Policy editor
Shared state spacetime/ Tables and reducers · State evidence
Bank client integrations/nessie/ Nessie setup
Public Actor apify/client-health-check/ Inputs, outputs and limits
Synthetic data and evaluation fixtures/, docs/eval/ Scoreboard · Red team
Team coordination tools/board, AGENTS.md Board setup · Team contract

Integration Notes

Cartesia Setup Features And Limitations

Cartesia Managed Agents provide the collections conversation and server-gated webhook tools; role-specific TTS makes responsibility handoffs audible. Code validates commitments and amounts. Voice never approves a payment or bank change. The office uses seven library voices (is_owner=false). We do not clone teammates or other people. Cloning remains a plan capability, not a feature of this demo.

Start with Cartesia configuration and the T1 call evidence/runbook. Team credentials belong only in ignored .env.local; the authenticated gateway and event receiver must be reachable from the configured provider. Keep the fixed disclosure and identity check before invoice amounts. A new call requires a fresh target/consent and go from Aziz/Firstmate; the setup instructions are not permission to redial.

The offline core demo uses scripted call turns. A software authenticator is not a human passkey tap. The recorder fix alone proves neither disclosure delivery nor a successful tool round trip; historical partial call receipts are scoped in the T1 document. A full phone-to-human-approval-to-bank flow needs its own trace. Narration, cached audio, or a queued link cannot establish that flow. No new Cartesia request was made to prepare this README.

Apify: Best Use And Best Actor

Client Health Check is our public Actor for both Best Use of Apify and Best Actor. Its source and setup README documents inputs, outputs, costs and limitations. It probes a supplied business website and can normalize supplied Maps observations and phone comparisons; it does not discover businesses or launch Maps scrapers. The retained evidence separates the historical website-only run from the later public-visibility check.

Real Versus Simulated

Component What it demonstrates Boundary to preserve
Northfield data and answer key Signed synthetic company, invoices and expected outcomes Consents and contacts in the seed do not authorize real calls; outside authorship is still 0/34
Policy and audit Real deterministic checks, rule/version evidence and chain verification A fixture-fed ALLOW is not a live payment or human approval
SpacetimeDB Actual state/reducer/subscription code; standalone evidence below Memory replay is not a hosted-database or durability measurement
Cartesia Provider voice/tool implementation and scoped historical call receipts Scripted turns and recorder tests are not a new successful phone call
GX10 and cloud models Real inference paths with retained per-run evidence Scripted eval has no live-model accuracy claim; fallback must retain its route label
Apify Public-web Actor and timestamped receipts where retained Fixture/cached signals remain labeled with their source/time; no new scrape is implied
CRS Sandbox-only projected evidence with test-identity labels Public records/fraud risk are not business-credit or OFAC products; fixture CRS is FAKE. Cached sandbox evidence is wall-only and cannot turn a pre-call hold into a pass
Nessie and pay page Sandbox API integration and a simulated card Posted deposits and displayed account balance are separate; neither fabricated balance growth nor settlement is claimed. A balance shown while Nessie is down keeps the cached-at label and is not a live read

See the sponsor evidence checklist before copying claims into a pitch. The synthetic eval recheck reports answer-key matches and explicitly unexecuted operations separately.

CRS Data Handling

Use only sponsor-provided sandbox identities. Server-side credentials stay in ignored environment files. The client projects typed summaries plus response hashes, source and observation time; do not publish raw reports, credentials, private identity records or phone numbers in screenshots, logs or board posts. Preserve crs_sandbox versus crs_fixture and the FAKE/test-identity label. When the sandbox is unreachable, the demo host may repeat the last evidence with cached: true and a cached-at time. That copy is audit-wall evidence only. The pre-call decision stays on the uncached client, so a cached clear cannot turn a hold into a pass. The retained sandbox receipt explicitly says business credit and OFAC were not run because those products are absent from the Cal Hacks sandbox. It does not establish live OFAC coverage. Integration behavior and any new product mapping remain with the owning stream and agreed spec.

Current CRS implementation (distinct from live evidence)

Merged code consumes sandbox public records before calls and sandbox fraud risk for vendor changes/payments. Any bankruptcy record stops the call (BANKRUPTCY_STOP); counts do not distinguish open from discharged bankruptcy. Fraud risk at least 70 holds the bank change/payment for Dana (FRAUD_RISK_HOLD, NF-028). Defaults remain fake; PRECALL_CRS and VENDOR_CRS select opt-in sandbox clients, and OFAC stays unavailable rather than clear. See the consumer contract. The P06 client receipt linked above is not an end-to-end P07/P13 wiring run; that credentialed wiring receipt remains pending in the sponsor checklist. This documentation does not enable or change either integration.

SpacetimeDB Architecture

SpacetimeDB owns live state and reducer-enforced transitions. The orchestrator performs external I/O and applies policy; the office subscribes to state and renders it. The renderer does not authorize actions. Human approval is a server-verified passkey assertion, never voice or an avatar movement.

Read tables, reducers and setup, standalone state evidence, and approval integration. The rehearsal guide labels its default mock bank and software paths. Evidence from a local server, a memory adapter, a hosted instance and a synthetic run must retain those distinctions. Hosted state and browser catch-up were separately verified in the retained Maincloud parity receipts. These use hosted state and a Mac browser, not proof of the GX10 web host. See current host/reset/fallback operations. Neither receipt proves a live call or human approval; the historical standalone docs above do not describe the current hosted-authentication status.

Implementation and evidence index

Each source has its own execution scope and failures. These links do not imply that the whole phone, human-approval and bank flow has been live-tested.


Built By

Abduaziz Umarov · Tomiwa Aluko · Diego Mendoza · Anthony Terry

Built at Cal Hacks 13.0. Watch the demo · Read the project story.

Every case has a desk. Every decision has a receipt.

About

A 3D back office where AI agents work real finance seats and every limit is enforced on the server. Hyphenate track prize, Cal Hacks 13.0.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages