the map

Five things you can verify about an agent you cannot predict — and the layer built for each.

8 parts


  1. You Can't Know What an Agent Will Do

    A map of open-source pieces that stand alone — and only make sense together.

    · 11 min read

  2. The IDE Solved This Twenty Years Ago

    Your IDE already knows code isn't text. Nobody gave agents the same courtesy.

    · 13 min read

  3. Constraint-Driven Development: Why the 60% of Agent Projects That Survive All Look the Same

    Constraints compose. Opinions don't. That's the whole difference between the systems that ship and the ones that don't.

    · 11 min read

  4. Verify by Hash, Not by Trust

    Content addressing is a trust primitive: when a thing's name is the hash of its bytes, checking it stops meaning trusting anyone.

    · 5 min read

  5. Give Tools Calls, Not Keys

    A compromised tool should have nothing to leak — because it was never handed the secret in the first place, only the call.

    · 5 min read

  6. Held, Not Issued

    A bearer token makes the thief indistinguishable from you. Agent identity has to be something possessed, proven, and gone in five minutes.

    · 6 min read

  7. The Math That Didn't Pay Rent

    ley-line-open tested whether cellular sheaves could make cache invalidation smarter than a hash check. A four-rung falsification ladder said no — and showed what does earn its keep instead.

    · 9 min read

  8. The Credential Is Part of the Interface

    ACI got the shape of the call right and left the authority behind it alone. A tool reached three ways has three different credential stories, and the oldest one — ambient secrets in your home directory — is the one agents break.

    · 8 min read