Explain why a decision exists, quoting the client conversation behind it.

Use when a constraint looks arbitrary, when you are about to argue against an existing decision, or when the user asks where a requirement came from. Returns decisions plus dated, speaker-attributed excerpts from the meetings that motivated them.

Search what clients and stakeholders actually said, from meeting transcripts.

Use to find where an ask originated, what was promised, or what a client
required — before writing code against a second-hand description of it.
Facts carry temporal validity: a fact with an invalid_at date was superseded.

Search prior architectural decisions before proposing an approach.

Call this before designing anything non-trivial. Superseded decisions and rejected alternatives are the most useful results — they are exactly the approaches that should not be proposed again.

Record a settled architectural decision so it is not re-litigated.

decision_key is a stable lowercase kebab-case topic preserved across revisions.
decided_at is when the ruling became effective, not when it was recorded.
scope: 'repo' (this repo only), 'client' (all client repos), or 'practice'.

Retire a decision and replace it, preserving the old one as REJECTED history.

Return decisions that were effective at a historical point in time.

Return the one live decision for a stable topic key.

Show the oldest-to-newest supersession chain containing a decision.