Back to home
Current stateAccessRoadmap

System

How AIvan is structured in public-safe terms

AIvan is being built as a layered operator system. The public site explains that shape directly: what users see, what executes underneath, how knowledge compounds, and how the public lane ships.

Current branch

feat/sprint12-post-v1-improvementsOrchestrator v3 sweep approved after a six-agent audit across hooks, skills, MCP, memory, and multi-AI behavior.

Snapshot date

March 8, 2026Public-facing system posture should stay anchored to this timeline.

Layer map

Four layers make the public story coherent.

01

Operator surfaces

The public face starts with visible entry points that make AIvan feel like a real system rather than a single terminal prompt.

CLI commandsworkflow lanescaffold lanevisualizervoice
02

Execution core

Under those surfaces sits the runtime that routes tasks, manages providers, applies security posture, and executes work.

session runtimeprovider managerplugin registrysecurity tierscommand router
03

Knowledge engine

AIvan compounds instead of resetting because it promotes useful context across hot memory, cold store, patterns, and decisions.

MEMORY.mdlearning journalerror memorypatternsdecisions
04

Delivery lane

The system now has a public ship path that stays independent from the private core while remaining visibly connected to it.

GitHub repoVercel deploysCloudflare DNSaivan-siteaivan.ivanm.dev

Boundary

What the site reveals and what it protects

  • Public: product shape, capabilities, command lanes, architecture posture, release log, and deployment status.
  • Private: research artifacts, patent work, internal prompts, sensitive memory, and detailed orchestration internals.
  • Rule: show confidence and specificity without leaking the materials that create AIvan's edge.

Visible signals

Public metrics that prove the system is real

24plugins enabled
40+subagent types
10automation hooks
4provider lanes

Deployment lane

Separate public repo, same product identity

The website ships from `aivan-site` on Vercel with Cloudflare DNS at `aivan.ivanm.dev`. That separation keeps the public surface fast to evolve without tangling it with the private AIvan core repo.