Skip to content

Records

Historical records, architecture decision records (ADRs), and post-mortems.

Contents

Architecture Decision Records

Historical record of significant architectural decisions.

Post-Mortems

Incident analysis and lessons learned.

Correspondence

Historical record of significant external communications.

Finance

Financial transaction records including invoices and receipts.

Purpose

Records are immutable historical documents that capture: - Why decisions were made - What happened during incidents - Lessons learned - Context for future decisions

Records vs. Evergreen Docs

Key Distinction: - Records (this section): Written once, never edited. Include dates in filenames. - Evergreen Docs (other sections): Living documents that are updated over time.

Rules for Records

  1. Never edit published records - Add new records instead
  2. Include dates in filenames - e.g., 2025-11-21-db-outage.md
  3. Use sequential numbering for ADRs - e.g., 001-use-postgres.md
  4. Provide context, not just decisions - Explain why, not just what

AI Usage Note

When AI answers questions: - "How to" questions → Prioritize evergreen docs - "Why did we" questions → Prioritize records - "What happened" questions → Prioritize records