The work pushes back.
The agent surfaces a real tension before it becomes a quiet choice in code.
The intent layer for software teams.
Git for code. Igni for intent.
The execution layer is here. The intent layer is missing.
Agents turn direction into code at machine speed.
But every implementation exposes choices: constraints, tradeoffs, patterns, exceptions. Today those choices get buried in runs, memory files, and diffs.
More context helps the agent. More review checks the output. Neither gives the team a way to shape the call while work keeps moving.
Igni does: the work pushes back, humans and agents make the call, and the code moves or the wall does.
Make the call now, or hold it in view. Either way the work keeps moving and the tension never disappears into a diff.
Not better context. Infrastructure for intent.
The loop in motion
Agentic development does not need more places to watch work happen. The agent keeps building; the open choice stays attached to the work until the team makes the call.
The agent surfaces a real tension before it becomes a quiet choice in code.
Made together on the same live surface — not handed back as a diff to approve.
Either can give. Nothing blocks while the team decides — now, or when they are ready.
A call nobody owns is a liability nobody holds.
Read the full argument →What makes it work
The intent layer has to connect judgment to code, let reality push back, and let humans shape the call without stopping the work.
Where decisions meet code.
Decisions, requirements, patterns, and discoveries connect to the code they shape.
Without it: intent is scattered context.
Where reality pushes back.
Agents build from current intent. Igni surfaces the tensions that matter.
Without it: intent falls behind reality.
Where the call gets shaped.
Humans and agents shape the open call while the work keeps moving.
Without it: humans find out too late.
Point Igni at your codebase. The graph builds from real product and code structure. You choose what should guide the work.
Day zero is curation, not data entry.
Charter access
If this is becoming real inside your engineering team, we'd like to hear from you.
Read Ben's essay →