The Architecture
A deterministic kernel
Large language models are probabilistic. Enterprise operations demand deterministic,
auditable state transitions. ADEPT separates the two: the LLM proposes, the Kernel
disposes.
Everything is an Object
Object Model
Every business entity is a strictly typed, immutable object with a defined lifecycle:
LegalEntity, Customer, FinancialTransaction, VentureBlueprint, ComplianceGate. All
defined in the Object Definition Language (ODL).
- Typed references, validated at write time
- Versioned schemas with constitutional amendments
- No dangling references, ever
Nothing changes silently
Event Bus
Objects are never mutated directly. Every state change is an immutable event
appended to a cryptographically chained ledger, fully replayable for audit.
- SHA-256 hash chain with post-quantum ML-DSA signatures
- Checkpoint, rewind, and replay to any point in time
- Complete audit trail for regulators
Execution is governed
Capability System
Capabilities are atomic, state-gated operations. An agent cannot invoke
Payment.ProcessCard unless every precondition is met, or the kernel throws a
StateViolationException.
- State-gating is non-overridable
- AI cannot bypass business logic
- Version-controlled and testable like CPU instructions
Intelligence Layer
Strategists, marketers, analysts. LLMs perceive, analyze, and recommend. Purely probabilistic.
↓ submits CapabilityInvocationRequest ↓
Kernel (Gatekeeper)
Validates state, capability tokens, and policy thresholds. Executes deterministically or throws StateViolationException.
↓ deterministic transition ↓
State Machine
Immutable object graph. Customer to Paid to Refunded. Every transition is an auditable event.
Businesses become version-controlled artifacts. A pricing experiment is
PricingModel_v2, and if it underperforms, the kernel executes a rollback in
milliseconds. Branching enables zero-risk experimentation: a European expansion can
be spun up, tested, and merged or archived without touching the core venture.