> ## Documentation Index
> Fetch the complete documentation index at: https://helloluciallc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Guest Operational Signals

<Note>
  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.
</Note>

***

## Current Implemented Signal Path

Current guest operational signal bridge:

<div className="hl-flow-v"><span>guest-facing Lucia conversation</span><span>operational\_signal v0</span><span>server-side signed POST from guest agent</span><span>Engine /v1/guest/signals</span><span>safe Engine persistence</span><span>Admin /admin/dashboard sections.guest\_signals</span><span>Admin Signal Stream guest signal rendering</span></div>

Guest signals are operational clarity, not automatic booking truth.

***

## Signing Boundary

Guest agent signs and POSTs guest signals server-side.

Core boundary:

```text theme={"dark"}
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:

```text theme={"dark"}
/v1/guest/signals
```

***

## Identity Normalization

Engine normalizes guest signals into explicit identity/linkage contract fields.

Anonymous/unlinked defaults:

```text theme={"dark"}
unknown_or_anonymous
not_applicable
unlinked
public_only
review_only
no mutations
```

Guest-claimed booking:

```text theme={"dark"}
claimed_booked_guest
guest_claimed
candidate_booking
operator_link_required
no mutations
```

Verified session:

```text theme={"dark"}
verified_booked_guest
verified_booking
booking_action_allowed
still no unrestricted Full Booking mutation
```

***

## Admin Display Contract

Current Admin behavior:

```text theme={"dark"}
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:

```text theme={"dark"}
review this guest signal
candidate booking claim
operator link required
unlinked public guest signal
```

It must not imply:

```text theme={"dark"}
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:

```text theme={"dark"}
service overlap is not identity evidence
airport pickup overlap must not attach an unlinked guest to Luca/Nora
```

***

## See Also

* [05 - Guest-to-Operator Bridge](/lucia/guest-facing-lucia/guest-to-operator-bridge)
* [01 - Guest Identity and Linkage Contract](/lucia/guest-facing-lucia/guest-identity-and-linkage-contract)
* [00 - START HERE - Operations](/lucia/operations/start-here-operations)
* [02 - Focus Ops Intelligence](/lucia/intelligence/focus-ops-intelligence)