Governed House Record
Important hotel promises carry explicit meaning, condition, authority, provenance, and ownership.
Working proof
Book it like a guest. Inspect it like a host.
Tamaga Hotel is a fictional ten-room property imagined near Tamga, on the south shore of Issyk-Kul. It exists so the guest journey and the system underneath it can be opened, tested, and questioned without exposing a real property’s operations or a real guest’s data.
Diagrammatic proof stage
One family. One late arrival. One promise carried through the system.
Guest
- 2 adults + 2 children
- Family Room: fits
- One open sleeping space
- Expected arrival: 23:30
- Late-arrival request: pending
Host
- Attention required
- Condition: written confirmation
- Resolution: host confirms
Evidence
- Channel Lens
- Fictional representation
- Condition lost
Fictional product demonstration. No real hotel inventory, booking completion, payment, or guest identity.
Current demonstrated capability
The product story can be followed from room choice to operational attention.
Room Fit
Suitability is evaluated separately from date inventory. A room can be unavailable, suitable, unsuitable, or not established for different reasons.
Promise-to-Task
A conditional arrival becomes a Stay Request and an operator Attention Item without pretending that the request is already confirmed.
Isolated demonstration
The guided scenario reaches Demonstration scenario complete without creating a real reservation, room allocation, payment, or guest profile.
Channel Lens
Current observations, frozen captures, and deterministic assessments remain distinct. The demo includes explicit fictional drift so a visitor can see what a meaningful mutation looks like.
A guided path
One family. One late arrival. One promise carried through the system.
Set the party
Use the guided scenario with two adults and two children.
Compare room fit
See which room types do not provide enough proper sleeping places and why. The Family Room fits four people and exposes one open sleeping space.
Add the expected arrival
Set 23:30. Later arrival after 20:00 requires written confirmation.
Keep the request pending
The system records the late-arrival request without turning requested into confirmed.
Inspect Host Attention
See what the host needs to resolve and the promise evidence attached to that work.
Resolve the request
The host can confirm or decline the synthetic request.
Inspect Channel Lens
Compare the governed meaning with selected fictional representations and identify where the condition changes.
Demo Release
The reference implementation is past prototype theatre.
The Tamaga Hotel Demo Release was declared after the governed House Record, Room Fit, Promise-to-Task workflow, isolated synthetic scenario, Host Attention, and Channel Lens were verified together.
The release evidence includes tagged installation checks, structural parity, safety auditing, Channel Lens immutability checks, rollback proof, and mobile performance evidence.
This is evidence about the software reference implementation. It is not evidence about a real hotel’s performance, conversion rate, guest satisfaction, or revenue.
What the demo deliberately refuses to do
Safe proof is stronger than fake realism.
- Real guest names.
- Email addresses.
- Telephone numbers.
- Billing profiles.
- Payment-card data.
- Identity documents.
- Real room allocation.
- Real payment.
- A real hotel address.
- A fake review score.
- A fake OTA listing.
- An autonomous AI confirmation.
The fictional policy and planted external drift are demonstration data. They must not be cited as market evidence.
Capability sequence
What you can inspect today is intentionally narrower than the roadmap.
Current reference implementation
House Record, Room Fit, request and attention states, Promise-to-Task, Host Attention, isolated synthetic scenario, and Channel Lens.
Narrow live-house pilot
A later phase with connectors selected from observed property demand.
Guest Memory and broader live-channel acquisition
Later work follows consent, retention, provenance, permissions, and lawful technical boundaries.
The next question
The demo should make you ask what this would look like for your hotel.
Tamaga Hotel is a reference environment, not a template property. Establish one consequential promise in your own house and see how it currently travels.
A safe reference house
We built a hotel that does not exist so the whole system can be inspected.
A real client property carries real guests, private operations, live prices, credentials, staff responsibilities, and commercial consequences. That is the wrong place for a public product laboratory.
Tamaga Hotel creates a different kind of proof. The house is fictional, the scenarios are synthetic, and the safety boundaries are explicit. That lets Tamaga expose the structure behind the stay without manufacturing a real accommodation business.
- No invented street address or map pin.
- No star rating, review score, or guest testimonial.
- No Google Business Profile or OTA reputation footprint.