Hammonds Agent Playbook V1

Mission Control reference for agent roles, ownership, routing rules, and roster structure.

1. Purpose

This playbook defines the Hammonds agent roster, what each agent is for, who it supports, and when Alex should route work to each one. It is intended to be the operating reference for the Hammonds Agentic Environment.

2. Core Routing Principle

Alex remains the primary orchestration layer. If a task is cross-functional, unclear, decision-heavy, or approval-sensitive, Alex should handle the thinking first and only then route to a specialist agent where useful.

3. Current Roster Structure

AgentRoleStatusBusiness areaMain owner
AlexCOO / Chief Orchestration OfficerActiveLeadership / OperationsJaco
MaraMarket ResearchActiveMarket IntelligenceJaco / Commercial
VanceStrategy & PricingActiveCommercial StrategyJaco
AxisProductionActiveProduction / ManufacturingJaco / Factory
RexLogistics ManagerActiveLogistics / FulfilmentJanice / Office Ops
CabiCustomer ChatActiveCustomer CommunicationOffice / Sales
AquaBrand & ContentActiveMarketing / BrandJaco / Marketing
MiloSales OptimizationActiveSalesOffice / Sales
NiaData & InsightsActiveData / ReportingJaco / Management
JuraContracts / Risk / ComplianceActiveLegal / ComplianceJaco / Approvals
ORIONIT & Systems Agent / Systems ArchitectPlannedSystems / AutomationJaco / Digital Systems
CHECKAQuality Control Agent / Audit & Verification SpecialistPlannedQuality Control / AuditJaco / Janice
SENTRASecurity & Risk Agent / Risk & Compliance OfficerPlannedSecurity / RiskJaco / Governance
LEDGERFinance Agent / Financial ControllerPlannedFinanceNicolette / Jaco
NOVAPeople & HR Agent / Talent & Culture ManagerPlannedPeople / HRJaco / Janice

4. Routing Rules by Agent

AgentUse when...
AlexThe task is broad, cross-functional, ambiguous, approval-sensitive, or needs operating judgment.
MaraYou need competitor, market, or pricing context from outside the business.
VanceYou need commercial strategy, margin logic, positioning, or pricing tradeoff thinking.
AxisYou need production drawings, BOMs, build logic, or manufacturing-ready technical outputs.
RexYou need order movement, logistics, route, delivery, BoB, or fulfilment process support.
CabiYou need inbound customer response drafting or lead/chat handling support.
AquaYou need copy, content, social posts, campaign drafts, or brand-aligned website text.
MiloYou need sales follow-up logic, lead improvement, or conversion support.
NiaYou need structured data, analysis, reporting, tagging, or insights work.
JuraYou need contract, disclaimer, privacy, T&C, or legal/risk review support.
ORIONYou need systems architecture, technical automation, integration planning, website systems work, or infrastructure support.
CHECKAYou need a verification pass on quotes, data, orders, process outputs, or release readiness.
SENTRAYou need security posture review, risk monitoring, safeguards, or operational risk scanning.
LEDGERYou need finance analysis, costing visibility, invoice logic review, or profitability support.
NOVAYou need onboarding, role clarity, people-process structure, or internal alignment support.

5. Recommended Phasing

Boundary note: Some planned agents overlap partially with existing roles. Before moving them from Planned to Active, their handoff boundaries should be made explicit so the roster stays useful instead of becoming noisy.

6. Mission Control Rule

Mission Control is the maintained source of truth for the Hammonds Agentic Environment. When an agent is added, removed, paused, activated, or repurposed, the roster and playbook should be updated together.