# Blog — Ablo

Notes on coordinating humans and AI agents on shared state — architecture, claims, and where Ablo fits in the agentic stack.

## Posts

- [Where Ablo fits in a multi-agent system](https://www.abloatai.com/blog/ablo-multi-agent-systems) — 2026-06-21, Concept. Ablo is not a multi-agent system — it is the shared-state layer a MAS runs on. Here is the precise mapping against Google Cloud’s definition.
- [Claims: the unit of human–agent coordination](https://www.abloatai.com/blog/claims-the-unit-of-coordination) — 2026-06-18, Concept. A claim is a short FIFO lease an actor takes before slow work — the primitive that lets people and agents edit the same row without clobbering each other.
- [Optimistic updates without losing writes](https://www.abloatai.com/blog/optimistic-updates-without-losing-writes) — 2026-06-15, Guide. Optimistic UI feels instant but can silently drop writes under concurrency. Here is how to keep the snappy local update and still commit a conflict-safe result.
- [Your Postgres stays the system of record](https://www.abloatai.com/blog/your-postgres-stays-the-system-of-record) — 2026-06-12, Architecture. Ablo is a transaction and realtime layer on top of your own Postgres — every committed row lives in your database, not a vendor’s.

---

Canonical URL: https://www.abloatai.com/blog

Also machine-readable on this domain: /llms.txt, /llms-full.txt, /openapi.json, /sitemap.xml, /robots.txt