- Party
- 2 adults + 2 children
- Room
- Family Room
- Room Fit
- Proper sleeping places for four.
- Honest limitation
- One open-plan sleeping space.
- Expected arrival
- 23:30
- House policy
- Arrival after 20:00 requires written confirmation.
How Tamaga works
Follow one hotel promise from approved fact to responsible action.
A family chooses a suitable room and says it expects to arrive at 23:30. The house requires written confirmation after 20:00. Tamaga keeps that condition attached to the stay: the Stay Request remains pending, Host Desk surfaces the unresolved condition as separate human work, and only an authorized person can confirm or decline the arrangement.
Arrival after 20:00 requires written confirmation.
House Record
Approved meaning
Guest View
Guest understanding
Host Desk
Accountable action
Channel Lens
Representation check
One governed promise, carried through one consequential stay.
Scenario facts
A family of four expects to arrive at 23:30.
23:30 activates the condition. It does not confirm the arrangement.
Expected arrival
23:30
Stay RequestPENDING
Received by the house
After 20:00
requires written confirmation from the house
Host AttentionOPEN
Established
The House Record governs the room meaning and arrival condition.
Understood
Guest View shows fit, limitation and policy before commitment.
Requested
Entering 23:30 creates Stay Request: PENDING and Host Attention: OPEN.
Owned
A responsible person claims the Host Attention item; the Stay Request remains PENDING.
Resolved
An authorized human confirms or declines the stay-specific arrangement; only then does the guest outcome change.
Checked
Channel Lens tests whether other representations preserve the condition.
What carries forward
Carry the right context forward without turning everything into memory.
Link the person and the stay.
CRM preserves enduring Contact identity while the reservation source retains booking authority. A stay projection is context, not a replacement for the source record.
Remember only what was explicitly established.
The late-arrival request remains stay-specific. A named operator action is required to create reusable Guest Memory, and the resolver applies it only when House, party, room, dates, review state, and access still match.
Explain without taking authority.
Ask the House reads approved public claims; it can explain Room Fit and prepare the existing request form, but it cannot confirm, transact, send, or use CRM or Guest Memory.
Working proof
Inspect the scenario in the fictional Tamaga Hotel.
Tamaga Hotel is a fictional, inspectable reference implementation. It demonstrates the relevant guest and host states without presenting a completed real booking.
- No real reservation placement.
- No payment.
- No personal information.
- No external message.
- Host resolution remains an authorized human action.
Questions
Request, authority and representation stay distinct.
Is a request the same as confirmation?
No. A Stay Request can remain pending while a separate Host Desk Attention item is open or owned by a responsible person. Only an authorized human confirmation or decline resolves the stay-specific arrangement.
Does Tamaga replace the PMS or booking engine?
No. The PMS, CRS or booking engine remains authoritative for live rates, restrictions and availability.
Does every request become Guest Memory?
No. A request is not a preference. Reusable Guest Memory requires explicit establishment, provenance, scope, and an applicability decision.
Can Ask the House read CRM or Guest Memory?
No. Under the current public contract, Ask the House reads approved House knowledge only; it cannot read CRM or Guest Memory.
Next step
Start with one promise that should not change between systems.
Trace where it begins, what the guest relies on, who must act, and what every representation repeats.