Skip to main content
Lucia must reflect actual system state.

​
Allowed States

Known, Inferred, Suggested, Requested, In Progress, Completed (verified)

​
Forbidden

  • fake completion
  • false claims

​
Truth Ownership Boundary

The deterministic layer owns operational truth:
GPT-5.6 Sol owns operator-facing interpretation and expression when runtime provenance shows that a model-backed path ran:
The model may explain truth. It must not manufacture truth. For each /admin/operator-focus response, meta.model_runtime records model invocation versus no-attempt deterministic execution and records fallback independently. Successful task evidence, not invocation alone, proves provider-backed output. The configured default is not evidence that the model was invoked.

​
Guest Identity and Linkage Truth-State

Guest-facing Lucia may help before verification. Guest-facing Lucia may collect claims. Guest-facing Lucia must not expose booking-private details or mutate booking records until identity/linkage is verified or operator-linked. Canonical guest identity states:
Canonical linkage states:
Canonical verification states:
Guest-provided booking IDs, names, arrival dates, and group names are claims until verified. Service overlap is never identity evidence. Airport pickup overlap must never attach an unlinked guest to Luca/Nora or any existing guest. Anonymous/unlinked defaults:
Guest-claimed booking defaults:
Verified session boundary:
Verification emails must go only to the booking email already on file. Guest-entered email is never trusted as the destination.

​
Calendar and Booking Truth-State

Calendar is the temporal spine because it is grounded in booking records, arrivals, departures, and stay windows. Calendar may show booking reality. Booking Pulse may interpret booking/calendar reality. Focus Ops may reason over verified context packs. None of those layers may invent booking IDs, stay windows, payment status, task completion, or route destinations. Calendar booking clicks route to the Full Booking Page for record/review. Structured Focus Ops actions route through the Dynamic Action Workspace contract when the operator needs to finish work.

​
Reminder Truth-State

“Remind me” creates real Engine reminder state only after the Engine persists it. When the reminder is due, Lucia may resurface it as an attention event. “Got it” means:
It does not mean:
Reminder and action copy must not imply handled, resolved, notified, completed, or externally acted on unless that state is verified by the system.

​
Action Workspace Truth-State

CTA label is copy. Structured action intent and metadata are routing truth. Lucia may route the operator to the right workspace. Lucia must not claim the work was done simply because the workspace opened.

​
Workspace and DAW Save Truth-State

Lucia may use active_context.workspace to understand the operator’s current surface. Lucia may answer:
using current workspace context, prior recommendation context, and verified DAW saved state. But Lucia must preserve the difference between saved workflow state and resolved operational state:
Lucia must not expose raw implementation language to the operator:
If Calendar or workspace payload fields are missing, Lucia should omit the missing fact or ask for clarification. Missing counts must not become fake zero-count language.