The catalog nobody could open
47 solutions. For a while, none of them were readable.
The rows made the trip across from the old system intact. The tool that would let Claude read one back did not exist yet. Data and access are two different pieces of work, and this is what it looks like when the first finishes before the second.
The table came over. The tool didn't, at first.
Solutions is one of 36 tables in the database, and its 47 rows crossed over with the rest of the 8,724 in the migration. That part is a copy: read the export, write the row, check it landed. It's mechanical, and it's done.
Reachability is a separate piece of work. A row sitting in a table isn't the same as a row Claude can ask for — that requires a tool with a name, a schema, and a place in the 44-tool surface that decides what gets exposed and how. For a stretch after the migration, that tool didn't exist for this table. The data was correct and present. It was also, from inside a conversation, invisible.
Now there's a verb for it.
The tool surface here is organized around the verb in your sentence, not the table underneath it. Solutions got its own: a read named for the question, and writes named for what you'd actually say.
- list_solutionsAsks for what's there. Paged, with a real total, so "47" isn't a number you have to take on faith — it's what the count returns.
- create_solutionWrites a new one from a sentence, the same shape as every other capture tool in this system: named for the past-tense verb, one approval per write.
- update_solutionChanges an existing row without you retyping the parts that didn't change.
- link_recordsConnects a solution to the initiative, task, or decision it actually belongs to — so "what did we build for this" has an answer that isn't a manual search.
Some of these started as something smaller.
51 ideas exist in the record. 2 have been acted on — meaning a real link exists from the idea
to whatever it became, tracked by get_idea_lineage rather than assumed from age or proximity.
Most solutions in the catalog didn't arrive that way; they were built and recorded directly. The lineage
tool exists for the minority that did, and it says so plainly when there isn't one to show.
Being readable is not the same as being searched.
No full-text search over descriptions No staleness check No scheduled review
Search here reads the words you say in a conversation, not the inside of every stored field. And like everything else in this system, nothing runs on a timer — a solution that hasn't been touched in a year sits there quietly rather than surfacing itself. If you want to know what's gone stale, you still have to ask.
Want the list of all 47, or the tool reference for what changed? Write and I'll send it: jake@aifrontdesk.com.