What changed, and what we learned
A lab notebook rather than a company blog. New modules, updated modules, new lessons, useful member builds, standards work, and the agent developments that actually matter to car rental.
The entries below are written examples showing how Lab Notes will read. They record principles and direction, not shipped work, and carry no dates because nothing has shipped yet. Edition numbers are placeholders.
Starting with three modules, not thirty
Why the first module set is deliberately small, and what has to be true before a module moves out of development.
Module work
Three modules are in development: Rate Data Checker, Market Position Board and Fleet Pressure Calendar. Each one exists because it teaches a complication that catches people out in real operations — stale rates, vehicle class normalisation, and availability across the full rental period.
Why small
A long module list is easy to publish and hard to keep honest. A short list can carry real setup steps, real tests, and a real statement of what is not yet true.
Standards work
The data exchange standard is being scoped narrowly to start: rate shop data, fleet and utilisation, reservations and booking pace, and pricing actions. No industry adoption is claimed.
Read before write
Why early connection work is read-only, and what would have to exist before that changes.
The principle
A tool that reads authorised data and explains what it sees can be useful on day one and withdrawn without consequence. A tool that writes a price cannot. Read access and write access are different products with different guarantees, and they should not arrive together.
What write access would need
Approved interfaces, authorisation, tenant isolation, verified data rights, validation, explicit action limits, monitoring, audit history and a tested way back. Shadow mode, where a recommendation is recorded and compared but never published, sits between the two.
Status
Vibe Connect is proposed. Nothing about access, entitlement, pricing or timing is approved.
Naming the things every tool needs
Planned. The note will cover the objects that appear in almost every tool an operator builds: locations, pickup and dropoff pairs, vehicle classes, rate observations, rate products, currencies, taxes, fees, availability, fleet, reservations, booking pace, utilisation, demand, pricing recommendations, pricing actions, acknowledgements and errors.
What goes in a Lab Note
Seven things, when there is something real to say about each.