Planner
Structured execution plans with steps, tool names, risk levels, success criteria, metrics, and assumptions.
KERNOLIX PLATFORM
The execution layer between AI intent and business systems.
Models reason. Business systems have side effects. Kernolix sits between them with tools, policies, approvals, execution state, and auditability.
01GoalBusiness intent
→02PlannerStructured steps
→03Tool RegistryCapabilities + risk
→04Approval GateHuman control
→05ExecutorReal side effects
→06VerifyResult + audit
RUNTIME PRIMITIVES
Small primitives. Strong boundaries.
The platform is intentionally built from explicit components so model output cannot silently become a real-world action.
Tool registry
A central catalog defines what a tool does, whether it reads or writes, and whether approval or a connector is required.
Approval policy
External writes can be blocked until a human explicitly approves the exact action.
Run state
Every plan and action carries execution status instead of collapsing the workflow into one opaque model response.
MODEL FLEXIBILITY
The workflow belongs to Kernolix, not to one model.
Planning and execution are separate concerns. This keeps the business process stable while model providers and capabilities evolve.
MODEL LAYERReasoning / planning / researchreplaceable
↓
KERNOLIX RUNTIMEPolicy / tools / approvals / run statecore
↓
BUSINESS SYSTEMSEmail / CRM / files / messaging / internal APIsconnected
CURRENT CAPABILITY STATE
We show what works — and what is still gated.
“Connector required” is a product state, not an error to hide. It makes the execution boundary clear before a workflow can affect external systems.
- ✓ Workflow analysis · available
- ✓ Time-savings baseline · available
- ✓ Draft generation · available
- ✓ Company research · available when server-side AI is configured
- ✓ Gmail send · pilot bridge, exact payload + approval required
- ↗ CRM / Slack / Drive writes · connector-gated
TOOL REGISTRYpolicy snapshot
workflow_analyzeLOCALresearch_companyREADdraft_messageLOCALcrm_upsertAPPROVALsend_emailAPPROVALBUILD ON THE RUNTIME
Start from a measurable workflow, not a generic chatbot.
Operator gives us the execution primitive. Focused products such as Sales Operator are built on top of the same control plane.