House Record
The governed record says what the hotel means and what condition attaches to it.
How Tamaga works
From what the house knows to what the guest receives.
Tamaga Hospitality starts with one question: can the hotel carry a consequential fact from its source, through the guest decision, into the work before arrival, and still recognize the same meaning when it appears somewhere else?
Later arrival after 20:00 requires written confirmation.
House Record
Establish
Guest View
Understand / request
Host Desk
Own / resolve
Channel Lens
Compare / verify
Established→ Understood→ Requested→ Owned→ Confirmed→ Checked
One governed promise, carried through one consequential stay.
The model
One record. Three views. Four jobs.
Guest View
The guest can choose correctly
Host Desk
The unresolved condition becomes named staff attention with an accountable owner.
Channel Lens
Representations can be checked without demanding identical wording everywhere.
The scenario
A family of four expects to arrive at 23:30.
2 adults + 2 children
Family Room · The Family Room fits four people.
Expected arrival: 23:30.
Later arrival after 20:00 requires written confirmation.
Established
The promise is governed before the guest has to decide.
Understood
The guest sees fit
Requested
A late arrival enters the stay as a request
Owned
The host sees the condition as work that needs a person.
Confirmed
The responsible person resolves the stay-specific outcome.
Checked
Channel Lens checks whether the condition survives its representations.
Step 1 / establish
Start from governed meaning
The Family Room provides proper sleeping places for four people. It also has an honest limitation: one open sleeping space. The house policy says: Later arrival after 20:00 requires written confirmation.
Step 2 / explain
First establish fit. Then show availability and the condition.
Rooms that do not fit are excluded with a reason. The Family Room fits. The limitation stays visible. Availability remains authoritative in the PMS or booking engine.
Step 3 / act
A condition becomes work for a person.
The guest enters 23:30. The Stay Request is pending and the Attention Item is open. Receiving the request does not confirm it. The host can confirm, decline, or otherwise resolve the arrangement.
Step 4 / inspect
The condition should not disappear when the wording changes.
A shorter representation is not automatically wrong. Channel Lens checks whether the condition that changes the guest decision survived the journey.
What survives
The guest should not have to start the decision again at every screen.
The room fit, honest limitation, expected arrival, policy condition, request state, and responsible action remain connected as the promise moves through the stay.
Four deeper paths
Open the part you want to understand.
House Record
Give a promise a source
Open House Record →Guest View
Help the guest choose correctly before checking availability.
Open Guest View →Host Desk
Turn conditional requests into named staff attention.
Open Host Desk →Channel Lens
See where a hotel promise changes meaning.
Open Channel Lens →Working proof
Follow the same logic in the fictional hotel.
Tamaga Hotel is a synthetic reference environment. It lets the scenario be inspected without presenting planted fictional evidence as a real hotel’s market performance.
Questions
The four-part model stays bounded.
Does Tamaga replace the PMS?
No. The PMS or booking engine remains authoritative for live availability
Is a request the same as a confirmation?
No. A request remains pending until a responsible human resolves the stay-specific outcome.
Must every surface use identical wording?
No. Different formats are expected; consequential meaning should not change accidentally.
What is demonstrated today?
The governed House Record and Promise Cards
Keep going
Govern the meaning. Explain it to the guest. Give unresolved conditions to a person. Check what every version repeats.
Start with the part of the hospitality model you need to understand.