Agents & roles

Havenware is organized as a fleet of specialists rather than one general assistant. Each agent owns a domain, holds its own memory, and carries its own credentials. All of them answer to the same governance layer.

The roles

Inbox. Owns your email. Triages incoming mail, drafts replies for your review, tracks threads that need a follow-up and chases them before they go stale, and keeps calendar coordination out of your hands.

Outreach. Owns the pipeline. Researches leads, drafts and sequences outbound messages, and keeps the CRM current: contacts, stages, notes, next steps.

Social. Owns your public voice. Drafts posts in your register, maintains a posting schedule, and prepares engagement for your review. Nothing publishes without approval.

Finance. Owns the money paperwork. Prepares invoices, matches incoming payments against them, flags discrepancies, and keeps the books ready for your accountant. Money movement is always gated.

Research. Owns your information diet. Monitors the sources you designate, produces digests on your schedule, and answers questions grounded in your own documents.

Why specialists

A single general agent accumulates a shallow version of every job. Specialists accumulate depth: the Inbox agent learns your correspondents and your tone, the Finance agent learns your clients' payment behavior. Per-agent memory keeps that depth where it belongs, and per-agent credentials mean each agent reaches only the tools its job requires.

One governance layer

Specialization does not fragment control. Every agent files proposals into the same approval queue, under the same contract, and lands in the same audit trail. Context that should be shared moves through the fleet's knowledge graph, so what one agent learns about a client is available to the others without duplicating access.

See The approval queue for the proposal contract, and Audit trail for what gets recorded.