HelloLucia Library

Guest-facing Lucia can convert public guest conversation into structured operational_signal v0 payloads that the operator system can review without pretending unverified guests are linked to bookings.

Current Implemented Signal Path

Current guest operational signal bridge:

guest-facing Lucia conversationoperational_signal v0server-side signed POST from guest agentEngine /v1/guest/signalssafe Engine persistenceAdmin /admin/dashboard sections.guest_signalsAdmin Signal Stream guest signal rendering

Guest signals are operational clarity, not automatic booking truth.

Signing Boundary

Guest agent signs and POSTs guest signals server-side. Core boundary:

public browser does not own signal authenticity
guest-agent server function owns signed delivery
Engine verifies signed guest signal intake

The current intake route is:

/v1/guest/signals

Identity Normalization

Engine normalizes guest signals into explicit identity/linkage contract fields. Anonymous/unlinked defaults:

unknown_or_anonymous
not_applicable
unlinked
public_only
review_only
no mutations

Guest-claimed booking:

claimed_booked_guest
guest_claimed
candidate_booking
operator_link_required
no mutations

Verified session:

verified_booked_guest
verified_booking
booking_action_allowed
still no unrestricted Full Booking mutation

Admin Display Contract

Current Admin behavior:

guest signals render in Admin Signal Stream
actionable guest signals are visible before collapsed rows
unlinked guest signals show honest review/link language
candidate/unlinked guest signals do not fake DAW routing
linked/verified signals may eventually route to DAW when safe
guest signals can seed Focus Ops context

Signal Stream language must stay honest:

review this guest signal
candidate booking claim
operator link required
unlinked public guest signal

It must not imply:

booking verified
guest attached
DAW ready
record updated

unless that state is proven.

Focus Ops Boundary

Guest signals may seed Focus Ops context. Focus Ops must not let candidate or unlinked guest signals drift into similar existing bookings. In particular:

service overlap is not identity evidence
airport pickup overlap must not attach an unlinked guest to Luca/Nora

Get Started

Foundation

System Architecture

Intelligence

Intelligence Architecture

Properties

Evaluation

Guest-Facing Lucia

Project Operating Context

Operations

Infrastructure

Marketing

Roadmap

Decisions

Releases

Templates

Branding and Identity

Lucia Encyclopedia of Knowledge

Lucia Intent Layer Canon Pack

Guest Operational Signals

Current Implemented Signal Path

Signing Boundary

Identity Normalization

Admin Display Contract

Focus Ops Boundary

See Also

​Current Implemented Signal Path

​Signing Boundary

​Identity Normalization

​Admin Display Contract

​Focus Ops Boundary

​See Also

Current Implemented Signal Path

Signing Boundary

Identity Normalization

Admin Display Contract

Focus Ops Boundary

See Also