API Modernization
The pipeline still used patterns from early in the year: an old Claude library, no caching, one giant analysis prompt. Mark also asked whether it was time for a database.
All six pieces landed in a day. Repeat calls reuse a cached prompt, analysis runs per use case and per company, and the answer on a database is no, for now.
Documents
With file names, on their own page →Start here
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The data stays in plain files kept in version control; a database waits until it's really needed.
No database, and when to revisit · came from Mark Parson
- 2
Analysis now reads each use case and each company separately, then writes an overview from those.
Analysis in small pieces
- The instructions sent with every call are cached, so the second call reuses them. In words
- Strictly shaped output works for the small analysis steps, but the per-call record is too big for it. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
market-analyst-c10-D1 Stay on git-tracked JSON; no database. Re-evaluate on concurrent multi-user writes, genuine relational queries, or raw-transcript storage becoming painful; SQLite first if ever. — Mark Parson
The data stays in plain files kept in version control; a database waits until it's really needed.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Analysis now reads each use case and each company separately, then writes an overview from those.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked whether the pipeline was still best of breed, and whether it needed a database
Cited: the record's Why and initial prompt carry his question ("let's not do so unnecessarily, but I'd like to evaluate"). The no-database verdict is recorded without a name; credited to him as the asker and cycle owner.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 1 decisions · 6 key-change entries · 933 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c10 →