A private intelligence system, exposed only where it should be.
Project Kaizen is built around a simple operating idea: powerful AI should be useful without requiring the private system to become public. The private side runs Max, personal memory, voice, automation, diagnostics, and model routing. The public side gets KaizenAI Open: a limited, queued, rate-limited chat lane with strict boundaries.
Design Goals
How Kaizen Is Organized
The platform is not a single chatbot. It is a set of cooperating services with clear boundaries.
Private Runtime
The private Max experience handles owner context, memory, long-running jobs, iOS continuity, voice, and authenticated model routing.
Public Runtime
KaizenAI Open is a deliberately smaller assistant with a public prompt, request queue, rate limits, abuse monitoring, and no personal memory.
Orchestrator
The dashboard manages service health, prompts, memory editing, public chat controls, diagnostics, and stack operations.
Shawn's Journey
The project grew out of decades of owning the full stack instead of renting pieces of it.
From IRC to infrastructure
INTRAC.NET began in 1998, when Shawn McCalla was running internet services, IRC networks, dedicated servers, and security-focused infrastructure at a time when uptime and hardening were learned in real production conditions.
That work shaped the pattern that still drives Kaizen: understand the layers, own the stack, keep systems observable, and build tools that can be trusted when they are used every day.
From homelab to AI
The same mindset later moved through home automation, networking, secure tunnels, private dashboards, and local services. When local Apple Silicon and Apple Metal made private AI practical, Project Kaizen became the next step.
The goal is not novelty. It is a personal intelligence system that feels useful, private, inspectable, and controlled: Max for the protected owner workflow, and KaizenAI Open as a carefully bounded public lane.
Evolution Roadmap
A clean public view of how Kaizen has evolved and where it is going.
INTRAC.NET foundation
Cybersecurity, internet services, server operations, IRC networks, and the early discipline of owning production systems end to end.
Private infrastructure layer
Networking, DNS, tunnels, dashboards, storage, monitoring, and home automation became one integrated operating environment.
Local AI runtime
Private assistant workflows, current search, voice, memory, model routing, diagnostics, and service orchestration moved into one local-first stack.
Native iOS experience
The private assistant became portable through a native app with chat, advanced voice, runtime status messaging, background continuity, and diagnostics.
Public lane and stronger governance
KaizenAI Open adds a queued, rate-limited public chat path while memory editing, web search quality, HomeAuto safety, and dashboard controls continue to mature.
More polish, safer access, deeper automation
Planned work includes cleaner public presentation, stronger audit loops, better public queue visibility, refined memory governance, and carefully gated multi-user access.
Release Naming
Public terminology is product-facing, not model-facing.
Why It Exists
Project Kaizen is about ownership, observability, and safer AI operations.
Private by default
Personal memory, account context, device control, home automation, and operational diagnostics remain on the protected side of the system.
Public by design
Visitors can try a controlled public assistant without gaining access to the private assistant, model inventory, prompts, runtime internals, or home systems.
