Private workflows stay private. Public chat stays bounded.
Kaizen is designed for daily AI use without flattening every workflow into the same risk profile. Search, voice, memory, dashboard operations, and automation each have their own trust boundary.
Example Split
Public Examples
These are appropriate for KaizenAI Open.
Current web questions
Ask for current weather, public news summaries, product research, or general research that benefits from current sources.
Technical explanations
Ask for a concept breakdown, code explanation, architecture comparison, or public documentation summary.
Project overview
Ask what Project Kaizen is, what KaizenAI Open can do, or how the public lane differs from the private runtime.
Private Examples
These remain on the protected side and are not available to public chat users.
Personal memory
Private recall, user-specific preferences, and long-running personal context are reserved for authenticated owner sessions.
Device or home operations
Automation controls, security-sensitive actions, and infrastructure operations are blocked from the public lane.
Account access
Private dashboard, iOS access, beta access, API access, and account requests go through announcements or direct approval.
Access Questions
If you want early access, iOS access, private access, or higher public limits, wait for public announcements on INTRAC.NET or email [email protected]. KaizenAI Open should not promise access or timelines inside chat.
