Lucia’s reasoning model combines deterministic operational structure with model-assisted language and judgment.
Core Principle
Lucia should not rely on model vibes alone.
The system must combine:
Current Model Layer
Lucia Engine v0.1.3.6 currently uses:
The upgrade path is intended to future-proof model swaps while preserving Lucia’s behavior contract.
Deterministic vs Model Responsibilities
Deterministic Logic Owns
Model Reasoning Owns
Never Let the Model Own
Runtime Boundary
Model output must be refined into Lucia’s stable structure before reaching the operator.
GPT-5.6 Sol response refinement sits over verified context packs. It can explain why a recommendation matters, answer short follow-ups, and keep the operator calm. It cannot change the booking, route, payment, task, save, or completion truth supplied by the deterministic layer.
The current Engine makes the execution path explicit in /admin/operator-focus response metadata:
These fields describe what happened for that response. The configured model alone must never be treated as proof of model invocation, and historical runs without captured provenance must not be retroactively labeled.
Current payment reasoning boundary:
If model output fails, Lucia should degrade safely.
06 - Semantic Conversational Intent Assist supports this boundary by helping Lucia classify lightweight utility and conversational prompt families before response shaping. It does not own truth-state, external execution, or open-domain general assistance.
Core ordering:
Workspace Context Reasoning
Lucia can now reason from the operator’s current workspace surface.
Current Development behavior:
Supported surfaces include:
Reasoning must preserve truth-state. A saved DAW step can be acknowledged as saved, but it must not become a claim that the payment, arrival detail, guest request, or underlying issue is resolved.
Operator-facing reasoning must not expose raw implementation language such as active_context, current_surface, payload, or metadata.
Good Reasoning Behavior
Lucia should say:
Not:
Model Upgrade Discipline
Model changes are allowed and expected.
But the following must remain stable:
See Also
