Skip to main content
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: 
structured state
deterministic ranking
verified context packs
workspace context
model refinement
stable output contract

​
Current Model Layer

Lucia Engine v0.1.3.6 currently uses: 
GPT-5.5 as default
OpenAI Responses API for Lucia JSON gateway calls
The upgrade path is intended to future-proof model swaps while preserving Lucia’s behavior contract.

​
Deterministic vs Model Responsibilities

​
Deterministic Logic Owns

route shape
response contract
known records
guest identity
booking identifiers
stay windows
payment state
Stripe financial truth
durable ledger truth
task identifiers
task status
route/action safety
save/completion truth
environment routing
deduplication

​
Model Reasoning Owns

language refinement
natural tone
some prioritization expression
multi-turn interpretation
emotional containment
operator-facing framing
permission-based phrasing

​
Never Let the Model Own

truth state
fake external execution
unverified completion
contract shape
system identity

​
Runtime Boundary

Model output must be refined into Lucia’s stable structure before reaching the operator. GPT-5.5 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. Current payment reasoning boundary: 
Stripe financial truth may suppress payment blocker attention when confirmed paid.
Property payment policy truth is not durable Engine-owned yet.
LIEA does not yet make full policy-aware due/overdue/partial/pending judgment.
Signal Stream is not yet wired to LIEA.
Admin renders payment truth read-only and does not mutate it.
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: 
Human first. Purpose second. Boundary third.

​
Workspace Context Reasoning

Lucia can now reason from the operator’s current workspace surface. Current Development behavior: 
Engine normalizes active_context.workspace safely
current surface context can orient the answer
explicit prompt subject still wins over page context
short next-step prompts resolve through workspace and prior context
saved DAW workflow state can inform the next response
Supported surfaces include: 
Dashboard
Calendar
DAW
Full Booking
Bookings
Maintenance
Concierge
Tasks
Reconciliation
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: 
This matters because check-in is tomorrow and the issue was guest-reported.
Not: 
This appears to be an operational concern that may require review.

​
Model Upgrade Discipline

Model changes are allowed and expected. But the following must remain stable: 
response contract
truth-state behavior
operator calm
routing correctness
permission-based action language

​
See Also