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

DocumentKind
ADR-001: PostgreSQL as the booking storeDecision record
ADR-002: Seat holds while a passenger paysDecision record
ADR-003: Application log retentionDecision record
ADR-004: Payment provider and idempotent payment callsDecision record
ADR-005: A warm standby in a second regionDecision record
Runbook: Seat hold backlogRunbook
Runbook: Payment webhook failuresRunbook
Runbook: Booking store failover to the standby regionRunbook
Incident report: Duplicate refunds and charges during the August failoverIncident report
Follow-up: Payment log retentionFollow-up

Suggested questions