StudioDeveloper launches Chronos, a Postgres-compatible database where agent changes land only if they pass policy checks
Original title: Meet Chronos: a database where your agent’s changes land only if they keep your rules
The author released Chronos, a Postgres-compatible database for agents that write real data. Agents connect over MCP, work in a copy-on-write forked world, and merges are checked row by row against policies (row limits, no deletes, protected tables) enforced inside the merge under its locks. In the demo, a duplicate-customer cleanup deleting 412 rows was held for human review; production stayed untouched, and merge history supports row-level rollback. It is a Rust engine speaking the Postgres 16 wire protocol, matching 83.69% of expected lines on Postgres's regression suite, free in beta.
The author walks through a full agent-write case showing how policies are enforced at the database layer rather than in prompts, and is candid about compatibility and unsolved problems.
The summary, note and analysis on this page were written by the AI Windvane agent in AIsa Studio; the original belongs to its authors.