Solution · Change to a shared standard
The rules could learn
When a rule keeps escalating, the agent proposes the change. A person decides.
Pattern, then Daniel decides, then Rule v13.
Who decides · Daniel Ruiz · CTO · a change to a rule
How it runs
The record shows which rules keep sending the same kind of change up the escalation matrix. The agent proposes the change to the rule, with the escalations that prompted it; the person who holds the decision takes it; the rule gets a new version.
A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.
ORG-R03
a rule changes only by a person’s decision, and keeps its versions
- Agent carries08:30ENG-R08 sent nine additive, reversible migrations up the escalation matrix this quarter; all nine were approved
- Agent carries08:35Proposed: additive changes with a rollback plan within the service owner’s limit
- Rules check08:36
ORG-R03
a rule changes only by a person’s decision, and keeps its versions
- Person decides12:30Daniel approves; ENG-R08 version 13; Ana Okafor told
Your team chat · #platform
Office of the CTO agent Agent
ENG-R08 sent nine additive, reversible migrations up this quarter; all nine were approved.
Waiting on Daniel Ruiz · CTO
Additive changes with a rollback plan within the service owner’s limit
Illustration · Halden, a fictional company
- 01The CTO office’s agentReads the record: ENG-R08 sent nine additive, reversible migrations up this quarter, and all nine were approved.
- 02The agentProposes the change: additive changes with a rollback plan within the service owner’s limit.
- 03Daniel Ruiz, CTODecides, as the next seat up from the rulebook’s owner (ORG-R03).
- 04The agentENG-R08 gets a new version; the rulebook’s owner is told.
Where the decisions sit
Decision, who decides, up to where, and above that whom.
- A change to a ruleDecides: the next seat up from the rulebook’s ownerUp to: the rulebookAbove that: the CEO
- A seat’s limits widenedDecides: the seat’s personUp to: the limits written in the seatAbove that: the next seat up
How much the agent decides, to start. Asks every time: the agent proposes, never changes a rule.
The record it leaves. The escalations, the proposal, the decision and every version of the rule.
How it plugs in
No new inbox, no new tool to learn.
- 01
An app in your tools
Connects to your repositories, trackers and chat as an app
- 02
A check, not a meeting
Holds a decision as a check the owner clears
- 03
Where people already work
Asks the owner where they already work, and carries out what was decided
The record
A rule that keeps escalating
- Rule
- ENG-R08 · version 12
- Escalated this quarter
- Nine additive, reversible migrations
- Decided
- All nine approved
The tools it runs through
- Business systems
ServiceNow
We connect to the systems you run, and build the connection before the demo.
Where it leads
Start with howyou run today.
Bring one piece of work that breaks at the handoffs: a pull request waiting on three reviewers, an initiative spread across twelve tools, a release nobody owns. We model the seats it crosses, give one of them an agent, and follow one decision to its record.