Verticla packs are MCP-tool bundles loaded into a pod's agents at boot. Two pack types ship: core packs for horizontal capabilities every business needs, and industry packs for vertical-specific schemas, workflows, and compliance scaffolding. The core packs are available to every pod regardless of industry. Industry packs extend the foundation per vertical; real-estate is the first pack in preview and is the most mature.
TL;DR
- Six core packs: inbox, calendar, contacts, documents, projects, comms — horizontal, business-agnostic
- One industry pack in preview: real estate
- Industry packs on the roadmap: construction, auto sales, marketing studios, watch trading, logistics, legal
- Pack enablement: pod admin toggles packs in the admin surface; tools appear in agents at next session start
- Pack customization: pods fork the pack's control-file templates per user or per pod
What's a pack?
A pack is a versioned bundle that registers a set of MCP tools with the per-user MCP sidecar at container boot. Each pack ships:
- A schema migration adding the pack's tables to the pod's tenant scope
- A set of MCP tool implementations
- Default
TOOLS.mdandAGENTS.mdcontrol-file templates the pod can fork - Per-pack documentation written to
verticals/<pack>/context/so agents have the domain context at session start - A pack-specific allowlist key the pod admin can toggle
When the pod admin enables a pack, every agent in the pod sees the pack's tools the next time they spawn. Tool name conflicts across packs are caught at registration; pods choose which pack wins for any conflicting tool name.
Core packs
The six core packs ship in every Verticla foundation. They cover the horizontal capabilities every business team needs regardless of industry.
inbox
Email-and-message drafting in 2–3 voice variants per send, reply drafting, sequence state. Composes with the pod's connected email account through the comms pack.
| Tool | Purpose |
|---|---|
inbox_draft_message | Generates 2–3 voice variants of a message for a given context |
inbox_draft_reply | Drafts a reply to an inbound message in the user's voice |
inbox_check_thread | Pulls recent thread state for context-aware drafting |
inbox_log_send | Records the sent message in the audit log + contact's history |
calendar
Availability lookup, meeting prep summaries, scheduling proposals. Composes with Google Calendar / Outlook via the comms pack.
| Tool | Purpose |
|---|---|
calendar_get_availability | Returns the user's free slots for a given window |
calendar_propose_meeting | Generates 2–3 slot proposals, formats for outreach |
calendar_brief_for_meeting | Pulls related contacts, deals, recent docs for meeting context |
calendar_log_meeting_outcome | Captures notes + next-action after a meeting |
contacts
Lightweight CRM — people, companies, relationship notes, last-touch tracking. The shared schema every other pack joins to.
| Tool | Purpose |
|---|---|
contacts_create | Add a new person or company |
contacts_update | Edit existing contact fields |
contacts_search | Find contacts by name, company, tag, or last-touch window |
contacts_log_interaction | Record an interaction (call, meeting, message, deal event) |
documents
Drafting, summarization, and retrieval over the pod's owned doc set. The agent's memory layer for long-form content.
| Tool | Purpose |
|---|---|
documents_draft | Generate a document from a template + context |
documents_summarize | Produce a summary of a long document |
documents_search | Semantic + keyword search over the pod's documents |
documents_save_version | Save a versioned copy with audit trail |
projects
Task tracking, status rollups, handoff queues. Composes with the coordination plane for cross-user handoffs.
| Tool | Purpose |
|---|---|
projects_create_task | Add a task with assignee, due date, dependencies |
projects_update_status | Move a task through the pod's defined state machine |
projects_handoff | Pass a task from one pod member to another via the coordination plane |
projects_status_report | Generate a rollup of pod-wide project state |
comms
Pre-wired integration to Slack, Microsoft Teams, AgentMail, Google Workspace, and a small set of other industry-accepted tools. Other packs invoke comms when they need to actually send a message externally.
| Tool | Purpose |
|---|---|
comms_send_slack | Post to a Slack channel or DM |
comms_send_teams | Post to a Teams channel or chat |
comms_send_email | Send via the pod's connected email account (AgentMail or pod's domain) |
comms_calendar_invite | Send a calendar invite via Google or Outlook |
Industry packs
Industry packs extend the foundation with vertical-specific schemas, workflows, vocabulary, and compliance scaffolding. Each industry pack ships when the research backing it matures into pack-quality tooling.
Real estate · Preview
The real-estate pack adds buyer-pipeline operations on top of the core packs. Three primary tools:
- Buyer-match — scores active buyers against new listings, returns top 5 with confidence breakdown in under 2 seconds
- CMA advisor — comparative market analysis returning fair/low/high with sourced comps and confidence in under 5 seconds
- NAR compliance — state-aware buyer-rep agreements, commission disclosure, audit logging
The pack's control-file templates pre-load the agent with realty-specific personality (SOUL.md), agent boundaries (AGENTS.md), and tool guidance (TOOLS.md). Pods in the realty vertical fork the templates per user.
The real-estate pack is the most mature pack in the system because the underlying platform architecture was built in service of it. See About for the trace.
Construction · Roadmap
Estimates, change orders, sub coordination, lien-rights compliance, project documentation. Schema covers projects, change orders, sub contracts, daily logs.
Auto sales · Roadmap
Inventory matching, follow-up sequences, F&I prep, manufacturer-rebate logic. Schema covers inventory, deals, financing terms.
Marketing studios · Roadmap
Campaign briefs, brand voice management, multi-channel coordination, content calendars. Schema covers campaigns, channels, content assets.
Watch trading · Roadmap
Authentication research, market comps, consignment ops, provenance tracking. Schema covers inventory, comps, authentication records.
Logistics · Roadmap
Route operations, exception handling, carrier coordination, document workflows. Schema covers shipments, routes, carriers.
Legal · Roadmap
Matter intake, document drafting, conflict checks, billing prep. Schema covers matters, documents, conflicts. Compliance scoping at production launch.
Pack version pinning
Each pack ships versioned. The pod admin pins a pack version at enablement, and version bumps are explicit (the admin reviews and accepts). This means a pack rev that changes tool behavior never surprises the pod's existing agent customizations.
A pack's version history is visible in the admin surface alongside changelogs.
Pack customization
Every pack ships with default control-file templates the pod can fork:
SOUL.md— agent identity tuned to the pack's domainAGENTS.md— what other agents in the pod do, scoped to pack-aware delegationUSER.md— per-user preferences (voice, schedule, role)TOOLS.md— when to use each pack toolHEARTBEAT.md— pack-recommended autonomous tasks
Pods edit the templates directly in their workspace git repo. See control files for the pattern.
Roadmap
Pack readiness order is research-driven. The next pack to land after real-estate enters preview is comms (general availability), followed by the construction industry pack. Order may shift based on pilot pod composition.
Subscribe to roadmap updates by requesting a pilot invite — pilot pods receive direct notification when their requested pack ships.