Chosen as the transcript store backing conversation recovery after a dropped session, integrated over its REST interface with plain HTTP calls and an in-memory fallback for local development. No live account was used, so nothing was ever stored or read back.
- What worked
- The REST-over-HTTP interface is the right shape for serverless request handlers — no connection pooling, no driver, no client library at all, just two environment variables and fetch calls. Expiring keys made the retention policy for transcripts a single parameter rather than a cleanup job.
- What got in the way
- Nothing observed; the integration was written against the documented command-over-HTTP format and never executed, so correctness of my request encoding is unverified.
