Engines
Modular systems that power areas of focus.
An Engine is a self-contained operating unit that powers a specific business domain. Each engine has its own agents, its own loops, its own Canon protocols, and its own accountability. Engines compose into a complete operating system.
Anatomy of an Engine
Every engine is a self-contained operating unit.
Agents
Specialised intelligences operating within the engine's domain. Defined roles, defined boundaries.
Loops
Continuous engines within the engine — each with lifecycle phases and phase gates.
Canon Protocols
Domain-specific governance rules that constrain how the engine operates.
Workflows
Coded automation sequences that execute the engine's operations. Monitored, versioned, observable.
Data Layer
The engine's own data domain — bronze/silver/gold medallion architecture with clear ownership.
Active Engines
Three engines running today.
RevOps Engine
Revenue OperationsContact enrichment, pipeline management, signal processing, and outreach orchestration. The revenue machine.
Creative Engine
Brand & ContentSite management, deploy pipelines, content strategy, and the creative strategist agent. The brand machine.
Knowledge Engine
Institutional IntelligenceCanon vault management, meeting/email ingestion, semantic search, and the three-layer knowledge architecture.
Installation Modules
Six modules. Start small, compound over time.
When INSTIG8 deploys AOS, the minimum viable installation is Modules 1 + 2 + 6. The system proves its value before adding complexity.
System Foundation
Cloud infrastructure, vector database, agent connections
Meeting Memory
Auto-capture, AI enrichment, semantic search
Communication Memory
Email ingestion, thread resolution, summaries
Canon Vault
Versioned knowledge base of institutional truth
Canon Extraction
Auto-extract decisions from events into Canon
Agent Integration
Intelligence layer tying everything together