Constraint memory

Without Klio

The expensive lessons — the API that rate-limits at 100/min, the pooler that rejects startup parameters — live in the head of whoever got burned. Agents relearn them by failing.

With Klio in the loop

1. 1

   The moment a constraint is discovered, it is set down as a fact with the incident behind it.

2. 2

   Any agent recalling the affected system gets the constraint alongside the code context.

3. 3

   Exact-match search means pasting the error string finds the memory that names it.

The call an agent makes

remember(
  {
    "content": "Neon’s pooled endpoint refuses libpq startup parameters — apply session settings with SET on connect."
  }
)

Real tool, illustrative payload. The full contract for every tool is in the docs.

What changes

A lesson is paid for once. Every agent after that inherits it for free.