Close-out ritual
This project taught us three things.
Hotel Channel Manager shipped. Before we close it, the flywheel turns: accept what the studio learned, and it compounds into everything we build next.
◈
Proposed new skill
/rate-parity-rules
Extracted the rate-parity logic into a portable playbook — the rule set, the edge cases (channel-specific overrides), and the test fixtures. Re-usable in the Restaurant POS and any pricing surface.
✓ Added — skills now 23↑
Component promotion
booking-calendar → hardened
Survived a third production project with zero new bugs. Promote prototype → hardened; the next project that pulls it gets the battle-tested defaults baked in.
✓ Promoted to hardened⚠
Documented failure mode
Channel sync race on simultaneous edits
Two channels writing the same date in the same second caused a phantom double-booking once during build. Root cause + the lock pattern that fixed it, written up so no future project rediscovers it.
✓ Documented as a failure mode↻
The flywheel
Three competitors ship the build. None of them ship this screen. The studio is smarter than it was an hour ago — and stays that way.