iLiC Notes 005
Wizard as the Governed Operator Layer
A public note introducing Wizard as the human-facing embodiment of iLiC and the control surface for governed autonomy.
Summary
Wizard is the operator-facing embodiment of iLiC. It is not presented as a general chatbot or an invisible automation layer. Its purpose is to give the user a visible place to speak, inspect, approve, remember, and understand what the system is doing. iLiC provides the governed cognition core underneath that interface; Wizard makes that core usable as an accountable local companion.
Why Wizard Comes First
A governed cognition system needs an understandable front door. Without one, architecture terms such as memory, telemetry, agents, state machines, and approval loops can sound abstract. Wizard gives those ideas a practical shape. It is the panel the user sees, the place where requests begin, the place where system activity can be inspected, and the layer that should ask before meaningful machine actions occur.
Governed Autonomy
Wizard and iLiC are designed around governed autonomy, not uncontrolled automation. The system can initiate, observe, suggest, remember, and prepare actions, but the user remains the authority. Meaningful action should be bounded by consent, policy, provenance, telemetry, and approval. The goal is not to create an AI with sovereign free will, but a trusted operating layer that can help without becoming unaccountable.
System Relationship
Publicly, the relationship can be described simply: Wizard is the user-facing operator layer, while iLiC is the governed cognition engine underneath it. Wizard handles the lived interaction: chat, thread steering, memory inspection, health signals, telemetry views, agent surfaces, and approval prompts. iLiC handles the internal control discipline: deterministic state flow, bounded memory behavior, knowledge lookup, proposal generation, and governed execution paths.
Design Boundary
The system may produce autonomous-origin candidates, such as research thoughts or proposed next actions, but that is not the same as independent authority. A useful operator layer can notice and prepare without taking over. Wizard's job is to keep initiative visible, constrained, and answerable to the person using the system.
What Is Intentionally Not Disclosed
This note does not disclose private control paths, local memory contents, agent internals, prompts, or implementation details. Its purpose is to introduce Wizard as a public-facing concept before describing iLiC's deeper governed cognition architecture.