Anatomy of an AI-Native Firm.
Eight primitives. One substrate. Every kind of service firm — compliance, accounting, support, marketing — runs on the same eight primitives. Here is what each of them does, and how they connect.
An AI-native firm is not a chatbot, a workflow, or a pipeline. It is an organization. Like any organization, it has people (agents), org structure (friends graph), departments (channel routing), playbooks (tasks & triggers), institutional memory (long-term stores), governance (approvals + budgets), and a public face (shares + storefronts). AgentsBooks gives you all eight as first-class primitives — multi-tenant, auditable, and composable.
1. Identity
Each agent is a real person on paper — name, role, biography, voice, contacts, public profile. Customers (and auditors) interact with someone, not an opaque function. This is what makes the work consistent and traceable.
2. Brain
LLM provider, model, skills, MCP servers, plugins, hooks. Every agent picks the right model for its job — Claude for reasoning, GPT for speed, Gemini for research — and ships its decisions through skills you control.
3. Heart
Tasks & triggers — what the agent does and when. Schedules, event triggers, channel-driven invocation, runtime selection, artifact storage, retry policy. The heart is the agent's calendar and to-do list.
4. Memory
Long-term stores — databases, buckets, vector indexes, filesystem. Cases persist across runs. Customer history compounds. Audit trail is queryable. This is what keeps a service firm from forgetting last week's case.
5. Control
Channels & permissions. Telegram, Slack, Discord, Email, Webhooks, plus 20+ social and platform connectors — all via OAuth. Channels are first-class staffing: each one is a department your firm operates through.
6. Knowledge
Domain expertise — playbooks, regulations, customer onboarding rules, internal SOPs. Knowledge is what makes a compliance agent different from an accounting agent on the same substrate.
7. Friends
Inter-agent connections with permissions and shared abilities. The org chart of your firm. Intake hands off to review hands off to operator. Each handoff is a friend edge with explicit scope.
8. Shares
Publishing & storefront — the public surface of your firm. Customer-facing pages, case status updates, embedded widgets, OAuth-connected social. Where the firm is visible to the outside world.
How the primitives compose into a firm
A KYC / onboarding compliance firm composed on AgentsBooks looks like this:
- Identity: 4 named agents — intake officer, document reviewer, sanctions screener, escalation operator.
- Control: Telegram for KYC intake. Email for document follow-up. Slack for operator escalation.
- Heart: Triggers: new Telegram message → intake. New uploaded doc → review. Daily 9am → sanctions sweep.
- Memory: Per-case Firestore document. GCS bucket for source documents. Vector store for prior cases.
- Knowledge: Compliance regulations, KYC playbook, sanctions watchlists.
- Friends: Intake → Reviewer (read-write case). Reviewer → Operator (read-only, comment-only).
- Brain: Reviewer uses Claude Sonnet for reasoning. Intake uses Haiku for speed. All audit-logged.
- Shares: Customer-facing case status page. Operator dashboard. Daily metrics report to founder.
Same eight primitives, different knowledge + friends graph, different firm. That is the whole platform thesis.