One real run · one complete calendar
The same production run reconsidered all 365 dates, lowered one pressured August stay, raised remaining October and November dates that were booking too quickly, and independently confirmed every new price from Guesty.
01 · Evidence packet
Code prepares reproducible guideposts. Greg can read the underlying sources, challenge contradictions, and change a soft recommendation. The writer enforces only the owner's hard promises and verification rules.
This listing had already accepted more nights than its dates normally should by this point. That is the strongest signal that the remaining prices needed to move up.
August 3 to 5 remained open inside the final checkpoint. Greg moved the coherent stay, not the whole month.
Six usable seasons inform each date. The COVID shutdown years are retained in the corpus but excluded from demand curves.
BookBy does not replace Wheelhouse. It adds listing pace, owner context, complete-stay geometry, and accountability.
High asks beside plentiful supply were not treated as achieved demand. Listing overbooking still required a throttle; market evidence determined how far.
The listing was being seen and saved. That made another blanket discount a weak first answer.
Prices were evaluated as stays guests can buy. Separate controls prevent arrivals and departures that would strand one night.
02 · Competitive telescope
BookBy asks which stay mission matters, which listings are actually substitutes, whether supply is tightening, and whether this listing was eligible for the same demand.
One-bedroom substitutes matter more close in. Two-bedroom and higher-capacity stays matter more farther out. Greg evaluates both instead of imposing one static comp identity.
The August 3 to 5 opening, its three prices, timing pressure, and next checkpoint.
One expected booking curve for every future date, built from six usable seasons.
Sixteen stable listings preserve continuity while eight scouts challenge the membership.
One- and two-bedroom alternatives that could plausibly serve different guest missions.
The broad discovery universe that tests assumptions without pretending every listing is an equal comp.
Listing pace determines whether the board needs upward or downward pressure. Wheelhouse and the selected market then size and localize that response. A high asking price with no clearing evidence is not proof that this listing can charge it.
The first full 24-listing baseline is real. Daily comparisons will infer when a listing changes from available to unavailable, but BookBy labels that as inferred booking evidence because a host block can look the same. The last observed ask is never called the guest's paid price.
The announced Wheelhouse API endpoint for individual member calendars is still pending. Until it arrives, the signed-in daily Calendar capture is an explicit operational duty, not a hidden unsupported API claim.
03 · Symmetric control
Greg is not rewarded for making changes or filling dates early. He is responsible for keeping each future slice on the right revenue path.
Only one complete stay had the timing pressure and the evidence for an immediate move. A blanket drop would repeat the old panic loop.
Accepted bookings on this listing already exceeded its date-specific curve. Market data sizes the response; it does not get to erase the strongest evidence.
The dates are still open. The scoreboard waits for a later accepted booking before it records a realized comparison.
A new booking, cancellation, comp movement, event signal, or change in geometry can move the correct target for another date.
one pressured three-night path
→$124 + $124 + $121Two nights changed and the third was already at target. The entire sellable stay was checked before either write was allowed.
04 · Production receipt
The operator sent one preflighted batch to Wheelhouse, then checked each price from Wheelhouse and Guesty. A partial stay or mismatched channel price would have failed the run.
Fresh calendar, listing pace, market, funnel, geometry, and owner constraints.
The controller required both recovery and throttling in the same run.
2 near-term lowers and 15 long-lead raises.
The system that accepted the write was reread before moving on.
The receipt closed only after the independent channel readback.
What this proves