LIFEOSAI — the Living AI Office

LIFEOSAI is the orchestration substrate — the back-end engine that makes many agents work together as a company. It is not a chatbot. It is not a workflow tool. It is an office, with org charts, budgets, governance, ticketing, and audit.

The mental model

Every interaction in the system reduces to three things:

Wakeup — “Please run this agent because X just happened.” Audit trail of every wake.
Run — An actual agent invocation. queued → running → succeeded/failed.
Issue — The unit of work, Kanban-style. Only one agent runs against an issue at a time.

A typical flow: comment arrives → wakeup fires → creates a queued run → next run claims the work → Claude SDK is invoked → result persisted → finally block releases the lock and starts the next queued run.

What’s running today

Metric	Live count
Active agents	40
Companies	3
Issues	311
Heartbeat runs	264 (230 succeeded · 35 failed · 1 running)
Routines	35

Sample agent roles in production: MD, Fleet Technical Director, Vessel Manager (TSI) - GCL GANGA, Flag Circulars Manager, UX Designer, CMO. Heterogeneous use, one runtime.

The two pillars

Pillar	What it explains
Orchestration substrate (this page)	How agents work — wakeups, runs, issues, org chart, budgets, approvals, adapters
Office library + memory	How the office remembers — 5 perspectives per file, story-building, provenance

Both run on the same engine. Day 2 + Day 3 of the workshop walk both pillars in detail.

Multi-company

A single deployment runs many companies with complete data isolation. The AI Guardrail Lab is the first office NBS will see; the substrate supports many more — NBS-Dev, Philippines-IoT, NBS-Accounts, NBS-Logistics, etc.