Why Not Just a Framework

What this means for you

The honest competitor is a folder full of glue code that started as a notebook. Generic frameworks give you primitives; IRIS gives you a contract that survives a rewrite.

The pitch

A framework lets you wire agents together. IRIS draws the line between an agent, a council, and a chain — and writes that line down once so the next engineer on the team does not have to guess.

Who it’s for

The team that has already built one agent system in a generic framework and now wants the second one to look like the first on purpose.

Proof points

• Single contract file shared by both SDKs — rewrite the runtime without rewriting your agents
• Every agent has a hash for an identity — change a prompt by one character, the identity changes, and the run log shows it
• Veto checkpoints are a first-class concept, not a callback you remember to add

quadrantChart
  title IRIS vs. generic agent tools
  x-axis "Glue code" --> "Versioned contract"
  y-axis "Single run" --> "Reproducible run"
  quadrant-1 "IRIS"
  quadrant-2 "Hosted runners"
  quadrant-3 "Notebook glue"
  quadrant-4 "Generic agent frameworks"
  "Notebook glue": [0.15, 0.2]
  "Generic framework": [0.7, 0.3]
  "Hosted runner": [0.35, 0.75]
  "IRIS": [0.9, 0.9]