Skip to main content
Your AI Operating Model is the map of how your organization actually works, and how much of it AI could support. The connector puts that map inside Claude, so you can interrogate it, talk a process through, and keep it true, without opening the platform. This is the biggest thing the connector does that isn’t just reading programme status. Everyone in your organization can read the whole map. What you can change depends on where you sit.

​
Start with the world view

Claude returns your unit tree with coverage rolled up on every node: coverage percentage, how many processes sit under it, how many carry a redesign gap, and how many are constrained. Rollups cover each unit’s whole subtree, so a top-level number already accounts for everything beneath it. This is the conversation to have before a steering meeting. Ask follow-ups in the same thread:

​
Drill into a function

You get that unit’s rollup, the processes it owns directly with their own rollups, its child units, and the top redesign-backlog steps across its processes, ranked by constraint and coordination burden. That ranking is the answer to “what would we fix first”, computed the same way the platform computes it, so the two never disagree.

​
Talk a process through

This is the richest response the connector gives. Claude gets:
Every step in order, with its current disposition (how it’s done today) and its target (where it should head). The distance between those two is the redesign gap, and it’s what puts a step on the backlog.
Acceptance criteria (the bar the step’s output has to meet), the input artifact, and the output artifact. This is what makes a step specifiable rather than just named.
The checks that prove a step is meeting its acceptance criteria, with target versus current scores. A gate blocks the step until it passes; a monitor samples it. This is how you answer “how would we know if the AI got it wrong?”
The handoffs and feeds between this process and others, projected from this process’s point of view, so you can see what breaks upstream and downstream if you change it.
The opportunities, deliverables, and projects linked to the process, or pinned to one specific step. Useful before you raise anything: the work may already be in flight.
Because it’s a conversation, the useful questions are the ones a document can’t answer:

​
Change what you own

If the map is wrong, fix it in the conversation:
Claude already knows whether you’re allowed to make that change, because the process read tells it up front. So it either makes the edit, or offers to propose it, without you having to find out by being refused.
1

Claude checks your access

Every process response carries what you may do to it: edit, create, or propose.
2

It edits, or it offers to propose

If the process is yours, or sits below you in the org tree, the change lands. If not, Claude offers the proposal route instead.
3

You confirm

Nothing is written until you say so. Writes are always an explicit user action.

​
The Jidoka rule

If you set a step’s target to fully autonomous, you must also give it an escalation trigger: the stop-condition that hands control back to a human. The server rejects an autonomous step without one, so you can’t accidentally describe a process where AI runs unsupervised with no defined way to stop it.

​
Setting the quality bar

Evals are how a business owner says what “good” means, in their own terms:
Once an eval exists, its owner can keep maintaining it even if the process sits above their altitude. A function lead can own the quality bar on a process they don’t otherwise control.

​
Propose a change to something that isn’t yours

Most people run processes they don’t own. That’s normal, and the connector treats it as the common case rather than an error:
Claude files an Opportunity linked to the process, and pinned to the step if you named one. The process itself is untouched. Your proposal then shows up as an initiative against that process, so the next person who asks Claude to walk through it sees your input in context. Anyone in the organization can propose against any process they can see.

​
Who can change what

Admins and core team can edit anywhere in their own organization. Creating a new root unit reshapes the top of the org chart and is restricted to them.
If you should be able to edit but everything routes to a proposal, your home unit probably isn’t set. Ask your organization admin to set it. See ownership and governance.

​
What the connector won’t do here

  • Delete anything. No process, step, eval, or unit can be deleted through the connector
  • Link a process to a deliverable or project, or wire up connections and implementation links. Those are structural edits your Kowalah team makes
  • Set Kowalah-side ownership on anything, even on records you create
  • Approve a proposal. Proposals land as opportunities for the owner and your Kowalah team to triage

Operating model in the platform

The full picture: the map, the cockpit, and delivery

Owning and improving a process

The same job, done in the web platform

Available tools

Every connector tool and what it returns

Set up in Claude

Add the connector to your Claude workspace