The Roomza Report, Week of July 20

Where things stand

• New. Room Lock, our exact-room booking product, built end to end this week across eight phases. This is the answer to the booking line that has been on this list since May 31.
• New. Apple Pay on the web.
• New. Payments run inside a locked-down path that only talks to hosts we have approved.
• In progress. Room Lock is in test. We drill it end to end before it goes anywhere near real money. That is the order we intend to keep for anything that touches a guest's card.

Shipped

• Room Lock, end to end. The data model, a state machine, an orchestrator, and an event log. Then the payments core, a rate service with a quote API, and the consumer booking flow.
• A live worker, deployed and running with health checks in the real environment.
• The booking bridge. Room Lock bookings flow into the guest booking record, appear in trips, and can be confirmed by a person when they need to be.
• Assignment and verification, built on the advocacy stack we already had, so we reused rather than reinvented.
• A locked-down payment path.
• An escape hatch on the phone. Press 1 during the call and you get the email path instead.
• Apple Pay on the web.

Improved

• Untyped rooms group up. When a hotel page has self-reported rooms with no type, we group them by the name guests gave them, so the page reads instead of lists.

Retired

• Guesswork in the booking path. Every step writes to an event log now, so when something needs explaining there is a record of exactly where it happened.

Eight phases in seven days, and a full end-to-end drill before a single real card was touched. That is the order we want to do this in.