Flight automation should be inspectable. AirScalp plans to attach a history to each saved rule so a traveler can see what ran, what matched, what failed, and what action followed.
Monitoring events
The history may include check time, provider response, candidate count, best qualifying fare, and the next scheduled check. Sensitive provider credentials should never appear in the visible log.
Rule decisions
When a candidate fails, the result should identify the category: price over the hard maximum, date outside the window, wrong airport, excess stops, unavailable cabin, insufficient seats, expired rule, or another supported constraint.
Alerts and approvals
The audit trail should record when a message was sent, which itinerary it described, whether approval was required, and whether the approval arrived before the candidate changed or expired.
Booking attempts
For an attempted action, the history should record the preflight checks, current total, provider response, confirmation status, and stop reason when the action did not complete. A provider confirmation, not a detected price, marks a successful booking.