Shore Room
Does not provide enough proper sleeping places for two adults and two children.
How Tamaga works / Guest View
Help the guest choose the right room before checking availability.
A booking engine can tell the guest whether a room is available. That does not always tell them whether the room works for their party, access needs, or conditions of the stay. Guest View makes that decision clearer before the guest commits.
2 adults + 2 children
Family Room
Fits
4 proper sleeping places
One open sleeping space.
The physical room explains the fit. The room result is not a live availability claim.
Date inventory → PMS / booking engine
Shore Room
Does not provide enough proper sleeping places for two adults and two children.
Orchard Room
Does not provide enough proper sleeping places for two adults and two children.
Garden Studio
Does not fit four people.
Fit first. Availability second.
Availability is not suitability
“Available” is not the same as “right for us.”
Orchard Room
Does not provide enough proper sleeping places for two adults and two children.
Garden Studio
Does not fit four people.
Family Room
Fits four people; one open sleeping space remains an honest limitation.
Hard constraints first
Start with what must be true for the room to work.
Room Fit can evaluate maximum occupancy, proper sleeping places, bed types, adult and child rules, access constraints, bathroom configuration, and other property-specific non-negotiables. The result should explain why a room fits or does not fit.
After fit
A good view cannot compensate for the wrong sleeping arrangement.
Once hard constraints are satisfied, softer preferences such as quieter location, orientation, terrace, privacy, or morning light can come second.
Tamaga Hotel example
Four people need four proper sleeping places.
2 adults + 2 children
The Family Room fits four people.
One open sleeping space.
Direct-booking bridge
The guest should not have to start the decision again at every screen.
Moving to availability should not erase the party, fit result, limitation, expected arrival, or policy condition that the guest just understood.
Request boundary
A request should stay a request until someone with authority resolves it.
The guest can provide an expected arrival of 23:30. That creates a pending late-arrival request; it does not silently confirm after-hours access.
Authority
Guest View improves the decision without pretending to own every transaction.
| Information | Default authority |
|---|---|
| Room meaning | Tamaga Room Fit |
| Date inventory and reservation | PMS / booking engine |
| Stay-specific confirmation | Responsible human |
Later capability
Ask the House comes later.
A future assistant should answer from the House Record, not from memory it invents. Ask the House is not presented as released in this intermediary build.
Questions
A clearer decision still has boundaries.
Does Room Fit use AI to recommend rooms?
The demonstrated Room Fit reasoning is explicit and inspectable. It explains hard constraints rather than presenting an opaque recommendation.
Does Room Fit replace availability search?
No. Suitability is Tamaga’s role; date inventory and reservations remain with the PMS or booking engine.
Can a hotel decide its own fit rules?
The governed hotel meaning and property-specific facts define what should count as a fit
Does Guest View confirm special requests?
No. It can preserve a request and its condition; a responsible person resolves the stay-specific outcome.
Is Ask the House already live?
No. It remains a later capability.
Keep going
The guest has chosen. Now show the host what still needs attention.
Continue from a clearer guest decision into accountable host work.