Decision archaeology

Without Klio

Code answers what. It never answers why, what else was on the table, or when the answer changed. Git blame gives you a commit message if you are lucky.

With Klio in the loop

1. 1

   Decisions accumulate with rationale as you work — each one a dated, attributed record.

2. 2

   When a decision is reversed, the old one is superseded by the new one, not erased.

3. 3

   Ask an agent why something is the way it is, and explore walks the record: current belief, what it replaced, when.

The call an agent makes

explore(
  {
    "entity": "auth service"
  }
)

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

What changes

The project’s reasoning becomes queryable. New answers point back at the old ones they retired.