PostgreSQL
also: PostgresRelational database. Stores rules, their triggers, the plan graph and, through Apache AGE, the phyto memory graph.
Reference ↗Twelve modules we wrote by hand instead of installing a framework: rank fusion in 84 lines, a tool-call salvager in 197. What each replaced, and when a library is still the right call.
Before rewriting our research, we probed every read tool by content, not by HTTP status. Thirty-odd tools worked. Four defects surfaced, one of which was not a defect: we had reported a number without reading the design behind it.
For three and a half hours our agent layer recorded none of five local-model runs. A network sensor that knows nothing about agents recorded all five, to the minute. Self-report was not wrong. It was absent, and absence reads as 'nothing happened'.
Our planning database had 1,061 nodes and nothing written in seven weeks. Meanwhile the real planning ran in a chat thread. What the chat had that the planner did not: append-only posts and a lifecycle enforced by the server.
12 MB of vectors, a 39 GB index, zero dead rows. A nightly sync updated every row whether or not anything had changed, and a vector index never gives back space from updates. Ten million no-op writes, found by one ratio.
The first A/B that actually queried both sides. The document store returns a filename. The organic memory returns the sentence that answers. Plus the bug that held 38% of every answer hostage.