Guest-facing Lucia can convert public guest conversation into privacy-reduced operational signals that the operator system can review without pretending unverified guests are linked to bookings.
The Guest Agent and Engine contracts on this page were verified from source on 2026-08-12. The latest accepted Guest Agent same-deploy and model-provider proof remains the 2026-07-18 receipt for commit fbf77b662511cf004ee1f46787e05773a8a78d71. This documentation pass did not submit a new live signal, call a provider, read live guest data, or re-test the Admin UI, so source implementation must not be read as fresh end-to-end live proof.
Source-implemented signal path — verified 2026-08-12
The source-reviewed bridge is:
guest-facing Lucia conversationprivacy-reduced operational signalauthenticated server-side deliveryEngine-owned intake and persistencedownstream operator review expectation
Guest signals are operational clarity, not automatic booking truth.
Evidence scope:
The 2026-07-18 Guest Agent runtime receipt proves the exact Guest deployment and its model-bearing path. It does not by itself prove that a guest signal traversed Engine persistence or appeared in Admin.
Authenticated delivery boundary
Guest Agent source delivers guest signals through a protected server-to-server boundary when that path is configured.
Core boundary:
Identity Normalization
Engine normalizes guest signals while preserving identity, verification, linkage, access, and mutation boundaries. Exact internal field names and enumerations are intentionally omitted from public documentation.
For an anonymous or unlinked guest:
For a guest-claimed booking:
For a verified guest relationship:
Downstream operator-surface expectation
The product expectation is that an Admin operator surface will make guest signals reviewable. The 2026-08-12 source review did not include dated authenticated Admin proof, so the behaviors below are expectations rather than verified current rendering:
Signal Stream language must stay honest:
It must not imply:
unless that state is proven.
Focus Ops Boundary
Guest signals may seed Focus Ops context.
Operator-assistance surfaces must not let claimed or unlinked guest signals drift into similar existing bookings.
In particular:
The labels above are explicitly synthetic and do not identify real guests.
See Also
