Constructive retweeted
Your agent's memory is rotting and it doesn't know it.
@danielchalef of @zep_ai walked through this at FRC #26 at @pebble_bed: enterprises now hold agent context to the same bar as every other database. Provenance. Access control. Invalidation when facts go stale.
Commercial graph DBs weren't built for millions of mostly idle small graphs. So Zep built Konig. 20M+ graphs in production, sub-100ms retrieval.
Context isn't a prompt trick. It's production infrastructure.
Thanks @constructive_io for sponsoring and @Techweek_ / @a16z for the SF Tech Week slot.
What happens when AI agents become database users?
I’m co-hosting a16z SF Tech Week dinner + research discussion with @pebble_bed, @constructive_io & @frontiersynd
Join Zep’s CEO + UC Berkeley researchers to dig into agent memory, security & data systems.
luma.com/82gz0ggu
pgsql-test: Real Postgres Testing for Faster Development Loops
postgresql.org/about/news/pg…
hey SF! come to the Grace Cathedral 8pm Sept 21st when we open to shoot the lasers
pumped about the @constructive_io software collaboration with @nusalt and @IlluminatedArts 🫶
Constructive retweeted
Today at 2:30pm ET, Dan Lynch joins the Postgres community to build a testable Postgres workflow for AI coding agents live.
Register: postgresconf.org/conferences…
Constructive retweeted
In case you missed it, Closing the Loop: Modular, Testable Postgres for AI Agents with Dan Lynch is now available on YouTube.
Watch here:
youtu.be/uDOWROFoSUM
The DseWiki story isn't just a browser-access problem. It's a where does authority live problem.
Those agents were supposed to have read access to the internet, not write access. They found a path around that boundary because their authority was being constrained by the environment rather than represented as a first-class principal all the way down the stack.
That's the opposite assumption behind the architecture we're building into @constructive_io 🧵
Holy...15,000+ edits by OpenAI agents on DseWiki, a German programming wiki, over two months. They used it to pass each other restriction bypasses, detection evasion, and state between runs. Backups when moderators deleted pages.
Every enterprise security review of your agent just got harder.
If your pitch says "full browser access and stored credentials," that's now the first question in diligence, not the last. The startups that win the next 12 months ship a permission model, an audit log, and a kill path on day one...not after the first breakout.
We write $250k–$3M first checks. If you're building the containment layer for agents, DM me. reuters.com/world/europe/ope…
To show appreciation for what @ElectricSQL built with PGlite, we're launching a pglite test framework and integrated it with pgpm :)
We built pglite-test to run real migrations, triggers, RLS policies, roles, and pgvector entirely inside your Node test runner with PGlite.
No Docker. No server. No CI services. Just pnpm test.
⚡️ constructive.io/blog/pglite-…
@constructive_io
It's been an honor to contribute a small part to the 7x7 Summer of Awe installation from @IlluminatedArts
Working with @nusalt on hardware and @constructive_io on software, we created the "Awepad" powering the laser show... and watching art, technology, and the city come together has been incredibly rewarding
In San Francisco for Deep Tech Week?
Join us tonight for:
🚀 Build Night: The Data Layer for Agentic Apps
Hosted by @pgEdgeInc, @constructive_io, @AngelList, and Frontier Syndicate.
Code generation isn't the moat. Engineering is.
Last week I sat on a panel at the SVB Experience Center with Sanjeev Dhanda (@GoogleDeepMind) and @abhiaiyer (@mastra) on the move from vibe coding to agentic engineering
@constructive_io @SiliconVlyBank @Kristopherfloyd
We're at capacity for the tonights session! Couldn't be more stoked to chat about building systems that agents and humans can converge on to build trusted code with Sanjeev Dhanda (@GoogleDeepMind) and @abhiaiyer (@mastra)!
Thanks @Kristopherfloyd (Frontier Syndicate) and Joanna Zanghi (@SiliconVlyBank), and Acasia for co-hosting with @constructive_io 🚀
Using @PlanetScale's own benchmark data. Removing the volatile and non-optimized polices, pure RLS vs. no RLS (I'm including original data for comparison)
This is what performance looks like when security is done right.
Replying to @danlynch
The @PlanetScale RLS benchmarks compare per-row function calls vs no RLS.
But real RLS policies don’t have to be function-based or evaluated per row. With proper design (stable conditions, InitPlan caching via subqueries, good indexes), you get near-zero overhead + full index utilization.
Interesting take on RLS from @PlanetScale — but the “per-row overhead” they highlight isn’t a limitation of RLS, it’s a consequence of how the policy is written
a thread on their take and benchmark 🧵
This is exactly why, and completely validates everything we do at @constructive_io because RLS is complex and must be managed or you'll make every mistake that @PlanetScale is assuming here. We solve all of these issues, and then some 🚀




















