Repository navigation
Tags
Tags
inventory: a forecast learned from a flight's own departures pkg/inventory had EMSR-b and no forecaster. History is the forecaster: the booking record of one flight's cabin over its past departures, by time frame and by the lowest class on sale, and the class controls the record gives. Bookings are divided by the time on sale, which unconstrains them. The marginal revenue transformation of Fiig, Isler, Hopperstad and Belobaba (2010) turns each strategy's demand and revenue into independent demands at adjusted fares, which corrects for buy-down. EMSR-b then needs no change. The tests hold MarginalRevenue and EMSRb against tables 1 and 2 of the paper, and run example 5 of Cooper, Homem-de-Mello and Kleywegt's spiral-down paper: the manager's model protects 70 seats, the best level is 95, sales read as demand spiral to 7, and fare adjustment holds 94. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
store: a split store exports its records store.Split keeps the message log in one store and the records in another. It is the store of a hosted carrier with its records in Postgres. It did not implement store.Exporter, and a caller that type-asserted for the export found none, although the Postgres node view beneath it has one. Split.ExportPNRs now streams from the records store. It returns an error when that store cannot stream. The test checks that the export gives the records store's records and none of the message store's. wholesky found it: its ledger counts a database book record by record after a restart, and the count never started on a split store. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
inventory: an empty override is taken off SetOverride forces a class open, closed or waitlisted on one flight. The way to undo it was to set an empty status, and the empty status was stored like any other. The next request for the class was then answered with an empty status code, and the availability broadcast treated the class as open by default. An empty status now deletes the override, in pkg/inventory and in the gateway's simple inventory. The test closes a class, takes the override off, and checks that the class sells and is advertised open. It answered "" before the fix. wholesky found it beside a fault of its own: its lever for closing a class passed "C", which no inventory knows. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
gateway: an own sale does not write to a published record Book stores the record, publishes it on the bus, and from then on does not change it. The own-sale step added in v0.1.100 broke that: it set the segment statuses on the same record a moment after the publish. A subscriber reading the record raced with it. wholesky's revenue tap did, and its race suite caught it. sellOwn now takes the locator, reads its own copy from the store, decides on that copy, stores it and publishes it. Book and AddSegment return the decided copy. The new test makes 60 own sales while a bus listener reads every record. It reports 2 data races on the old code and none now. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
inventory: a class sold past its limit stays closed classOpen returned a class's authorisation less the seats sold in it and below it. The controller sets the authorisations again at every question, so a stronger forecast can put a class's authorisation under what the class has sold. The result was then negative. Decide and Availability both treat a negative count as "no ladder for this class", so the class sold to the last seat of the cabin and went out in the availability broadcast as open. The count now stops at zero. The test sells 60 seats in a discount class under a weak forecast, strengthens the forecast so that the class's limit is 49, and checks that the next request is refused and the class is advertised as closed. Before the fix the request was confirmed and the class was advertised with 113 seats. wholesky found it. A carrier's lowest class closed at 18 seats. One sale in the class above lowered the limit to 16, and the next request for the lowest class was confirmed. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
gateway: a carrier's node sells its own seats A node configured as a carrier answered the sells that other systems sent it and could not sell its own flight. Book wrote the record, asked for a link to the node's own designator, found none, and left the segment at HN. A carrier's website and call centre book on the carrier's own reservations system, so this was the direct channel missing from the gateway. Book now decides the node's own carrier's segments with the node's own Responder, with a nil peer and nothing sent, and writes the answers on the record. Cancel releases those seats through the Releaser and no longer reports the node's own carrier as unreachable. Ticket control, document control and the divide advice skip the node's own carrier. AddSegment decides an own segment the same way. Other carriers' segments on the record go over their links as before. A node with no Responder owns nothing and is unchanged. wholesky found it: a booking of a carrier's own flight at its own node stayed at HN on all 4 carriers of the test world. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
api: an NDC order is a sale in the NDC channel The order endpoint built its booking request without a channel. The record's origin then named none, and a fare whose rule limits it to NDC sellers could not be priced for the one kind of sale it was filed for. The request now carries the channel "ndc". Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
gateway: a booking may carry the fare its seller priced A seller that shops with its own engine quotes a fare and books afterwards. The node priced every booking itself as of the moment it arrived (or as of PricedAt, never later than now), so a booking could not keep a price worked out by anything but this node. BookingRequest.Quote hands the seller's fare.Quote over. A node with Gateway.AcceptQuotes stores it on the record -- money, fare components, fare calculation, fare basis per segment -- after holding it against the booking: a price for each passenger, a fare for each air segment, in the class booked. A node without the setting ignores the quote and prices as before, so nothing changes for a node that does not trust its callers. wholesky needs it: its travellers shop across carriers before they book, and what they were quoted is what they pay. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
fare: components and priceable units; mct: minimum connecting times Pricing sold each segment alone under its own market's fare. A connection cost the sum of two local fares, no rule reached past its segment, and there was no way to say who might sell a fare. pkg/fare now prices the way a fare engine does. A fare pays for one or more consecutive flights (a fare component); components are grouped into priceable units (one way, round trip, open jaw, circle trip); and Price searches every division of the itinerary for the cheapest whose fares all pass their rules. Advance purchase is measured to the first flight of the unit, the stay and its Saturday night across the unit, and the same four flights can sell as two open jaws when the circle trip fails. The model is Carl de Marcken's "Computational Complexity of Air Travel Planning" (ITA Software, 2003), and the tests price its worked examples from the slides: the $2,000 and $1,800 ways to pay for three flights, the H14ESNR fare, and the Denver circle trip. The rules follow ATPCO's categories by number: day and time, season, blackouts, flight application with partner carriers, advance purchase, minimum and maximum stay, stopovers, combinations, surcharges, sales restrictions by country, channel, agency and account, and penalties. A routing names the points a fare may connect at. Request.Open makes the pricing a lowest-fare search over the classes that can be sold. The quote carries its components, units and fare calculation line. A through fare is divided between its segments by miles, and a carrier-imposed fee is totalled apart from the taxes. The mileage system, the IATA construction checks, stopovers for a charge and the back-to-back restriction are not implemented, and the package says so. The gateway prices a booking for its point of sale. BookingRequest gains Country, Account and PricedAt; the record's origin keeps them; and a quote is honoured for Gateway.QuoteValidity. The record keeps the fare calculation and the components. inventory.Controller.Value is the carrier's own estimate of what a request brings it net of the channel's cost. A request for one leg is nested in the class that value covers, so a seat stays on sale in the carrier's own channel after it closes in a dearer one. pkg/mct is new: minimum connecting times to IATA's SSIM chapter 8 (March 2021), which is free. It reads and writes the 200-byte file and answers for a connection by the chapter's hierarchy of 31 elements, its codeshare rules, the global defaults and the connection-building filter. The fixtures are placed byte by byte from the layout table, and the Miami, New York and filter examples are the chapter's. The fuzzer found that a record with an invalid status was written and then refused; Encode now validates as Parse does. prorate.Divide values each coupon of a fare component under the terms two carriers agreed: a fixed amount, a share of the fare or of the local fare, a floor or ceiling, and a service charge or commission. Coupon gains Local. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4efsDi6fNVRMC3NcdWg1Q
crew: a member's history, the cumulative limits, cabin crew and pay Part 117 was checked one duty at a time, so a pilot could fly every day of the month. Crew tracking needs the look-back limits of §117.23 (100 hours of flight time in any 672, 1,000 in 365 calendar days, 60 and 190 FDP hours in any 168 and 672) and the rest of §117.25(b) and (e), which only mean something against what the member has already flown. History is the seam: a tracking store answers block and duty time inside a window, the last duty, and the longest time free. Record is the exact form. Duty.Admits evaluates every limit where it is highest; for block time that can be a middle leg's arrival, because an old leg can leave the window between two arrivals, and a test pins that case. Cabin crew get 14 CFR 121.467(b), checked on the schedule because (b)(14) excuses an overrun beyond the carrier's control, and the minimum complement of §121.391(a). The text of all of it is the eCFR's of 15 October 2026. PayRules prices a duty the way North American agreements credit it: the greater of scheduled or actual block, a minimum per duty, a 1:3.5 trip rig and a 1:2 duty rig. APFA's public On-Duty Contract Guide states that rule in section 11.D, and a test uses its numbers. Premiums, per diem and deadhead credit are the agreement's numbers, the caller's. Every new test was watched to fail against a mutation of the rule it checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PreviousNext