Sample corpus
Tallowmere Systems is a fictional company that builds Ferrylog, a booking system for small ferry operators. Its ten documents are decision records, runbooks, an incident report and a follow-up: the kind of engineering records an agent is asked about. They were written for this documentation. Any resemblance to real companies or people is coincidental.
Load them into your trial tenant as the quickstart describes, then ask the questions below. Each one is answered by specific sentences in the documents, so you can check every citation your agent returns.
Two documents disagree on purpose. A decision record sets how long payment logs are kept, and a later follow-up changes it. The payment-log question shows how a memory recorded from the first document is superseded when the second one is read.
Documents
Download all 10 documents (zip)
Licence: CC BY 4.0
| Document | Kind |
|---|---|
| ADR-001: PostgreSQL as the booking store | Decision record |
| ADR-002: Seat holds while a passenger pays | Decision record |
| ADR-003: Application log retention | Decision record |
| ADR-004: Payment provider and idempotent payment calls | Decision record |
| ADR-005: A warm standby in a second region | Decision record |
| Runbook: Seat hold backlog | Runbook |
| Runbook: Payment webhook failures | Runbook |
| Runbook: Booking store failover to the standby region | Runbook |
| Incident report: Duplicate refunds and charges during the August failover | Incident report |
| Follow-up: Payment log retention | Follow-up |
Suggested questions
- Why did Tallowmere choose PostgreSQL for Ferrylog's bookings?
- How long does a seat hold last, and what should on-call do when expired holds are not being released?
- Why were some passengers refunded twice during the August 2024 failover, and which rule did that break?
- Who can approve failing over the booking store, and how many recent writes can a failover lose?
- How long does Ferrylog keep payment logs?
- Is it safe to replay the payment of a booking stuck in payment pending?