Public operating brief
The site now reads like an operating surface instead of a pile of claims. Start with evidence, then move into system posture, access paths, and the release ledger.
Proof strip
The fastest way to trust AIvan is to see the visible command lanes already working in the repo.
Natural-language transforms
live lanenode ./bin/dev.js transform ./examples/orders.json "Sort by total descending and keep top 10"Intent becomes executable local data work instead of a one-off answer.
Structured-data transforms already run today for JSON, JSONL, and NDJSON inputs.Provider routing
live lanenode ./bin/dev.js transform ./examples/events.jsonl "Group by region" --provider claudeProvider choice is a runtime lane, not a redesign project.
The same task can move across Gemini, Claude, OpenAI, and local OpenAI-compatible endpoints.Workflow lane
live lanenode ./bin/dev.js workflow --helpWorkflow automation is already a first-class command surface.
The direction stays DAG-based task execution rather than a pile of prompt snippets.System snapshot
AIvan stays legible because the public story is structured: surfaces, core, memory, and delivery.
01
The public face starts with visible entry points that make AIvan feel like a real system rather than a single terminal prompt.
02
Under those surfaces sits the runtime that routes tasks, manages providers, applies security posture, and executes work.
03
AIvan compounds instead of resetting because it promotes useful context across hot memory, cold store, patterns, and decisions.
04
The system now has a public ship path that stays independent from the private core while remaining visibly connected to it.
Route index
The route map stays intact, but each page now has a tighter job and less overlap.
Snapshot date, branch focus, metrics, and proof in one scannable page.
Open pageSystemPublic-safe architecture dossierThe four-layer model, boundary rules, and delivery posture.
Open pageAccessQualification and contact routesWho AIvan is for right now and how to start the right conversation.
Open pageManifestoPositioning without AI wallpaperThe operating principles behind the product surface and the site itself.
Open pageRoadmapPhases and contribution rulesWhat the website should add next, and how changes stay grounded in the real system.
Open pageSelective release ledger
Enough detail to prove motion. Not enough leakage to expose the private core.
March 8, 2026
The public surface now ships from a dedicated Next.js repo at aivan.ivanm.dev instead of staying coupled to the main portfolio codebase.
March 8, 2026
Six parallel audit lanes identified infrastructure, content, and feature upgrades across hooks, skills, settings, MCP, cold store, and multi-AI behavior.
March 7, 2026
AIvan now persists orchestration and research updates with less manual cleanup, strengthening the compounding knowledge loop.
March 6, 2026
The current product direction was codified through an Ouroboros interview-to-seed flow covering transforms, scaffolding, workflows, voice, visualization, and security.