
MTAR T3D Sessions | When Postgres Is Enough | Building PostgreSQL Apps for AI Agents (Part 3)
In the final part of "When Postgres Is Enough," Michael Cooper and JD discuss how AGLedger is adapting a PostgreSQL-based application for agents that move quickly, anticipate next steps, and may not follow the same process twice. A workflow that works with a simpler agent can expose gaps when a more capable model begins skipping steps.
Michael explains why probabilistic agents need deterministic systems around them. PostgreSQL gives AGLedger the flexibility to change schemas as agent behavior evolves while still enforcing consistent rules around the shape of its records and data.
They also look at the next stage of AGLedger: storing an agent’s working context in real time. That raises practical questions about what belongs in the encrypted ledger, what should remain available as agent memory, and what can be temporary or deleted.
The episode closes by defining what it means for an agent to work faster. It is not simply about using more tokens. The real measure is how quickly an incoming request becomes a completed decision or action.
🔗 Michael Cooper: https://www.linkedin.com/in/michaeldc/🔗 AGLedger: https://www.linkedin.com/company/agledger/
Więcej odcinków z kanału "More than a refresh: Conversations with the most interesting people you've never met"



Nie przegap odcinka z kanału “More than a refresh: Conversations with the most interesting people you've never met”! Subskrybuj bezpłatnie w aplikacji GetPodcast.








