What if agentic systems did not have to start from scratch?
We kept rebuilding the same operational machinery around different agents.
The model could reason and the tools could execute, but every system still needed bespoke state, permissions, approvals, action boundaries, and audit. Change the agent and much of that glue had to be wired again. KIFF began with a question: could those repeated parts become a reusable framework?
Could we build agentic systems complete from the beginning?
The intelligence was new. The plumbing was not.
Each system rebuilt the same foundations: entities, events, state, valid actions, permissions, approvals, execution results, and evidence. The repetition was hiding in the glue around the agent.
Define the operational pieces once.
A domain can package the thing being acted on, what is true about it, what may happen next, and who has authority. Those pieces can be composed instead of recreated for every use case.
Let the agent become replaceable.
When agents propose through a stable operational contract, teams can maintain, upgrade, or replace them without rebuilding the surrounding business system each time.
Do not make the agent carry the whole system.
An agent is good at interpreting a situation and proposing a move. It should not also be the only place that knows the current state, the valid actions, the approval boundary, and what must be recorded. When all of that lives inside one agent implementation, maintenance becomes a rewrite.
KIFF does not make the agent smarter. It makes the system around the agent reusable, governable, and easier to maintain.
The same pieces can support different agents and different domains.
KIFF gives these pieces a common shape without deciding what they mean for your business. That stable shape is what makes composition possible: a future agent can enter through the same action contract, and another system can read the resulting state and evidence without a new one-off integration.
Not every action needs KIFF. Three conditions define the fit.
Whether the action is allowed depends on the current state of the entity — not just a rule written in a doc.
Money moves, or the action is irreversible.
An auditor, a regulator, or a cyber-insurer asks what was authorized.
KIFF is a framework for building complete agentic systems from reusable operational domains. A domain defines the entity, events, state, valid actions, authority, approvals, and evidence once. Agents and services can then propose work against that contract without owning or recreating it.
Its vocabulary, business rules, risks, evidence requirements, and definition of success.
How state, actions, authority, approvals, execution outcomes, audit, and replay fit together.
Normalize the mechanics, not the semantics. Reuse the contract, not one agent's implementation.
Reusable infrastructure only helps when the system uses it.
KIFF does not invent your domain's truth, repair missing events, or intercept a path that bypasses it. Your systems must publish reliable facts, and the consequential calls you want governed must pass through the runtime or guard. Inside that path, the operational contract remains stable even as agents change.