Solution · Change to a shared standard
Rules you write, checked before work counts
Your rules, in your words, versioned, and checked before anything merges.
New rule, then Ana approves, then v13.
Who decides · Ana Okafor · Owner of the rulebook · every change to a rule
How it runs
The rules an engineering organization already has (what needs a rollback plan, what needs a second pair of eyes, what may never leave the company) live in people’s heads and a wiki. Written down once, owned and versioned, they are checked against every change before it counts.
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
- Person decides10:00Ana adds a rule: migrations that drop a column need a backfill window
- Agent carries10:05ENG-R12 drafted, with the changes from last quarter it would have caught
- Rules check10:06
ORG-R03
a rule changes only by a person’s decision, and keeps its versions
- Person decides10:30Ana approves; rulebook version 13
- Agent carries14:00The next migration is checked against ENG-R12
Your repository host · billing-service
Drop the legacy tax column #5120
- TestsPassed
- ENG-R12 · backfill window plannedRequired
- CClrSlate · waiting on Sofia BrandtRequired
Illustration · Halden, a fictional company
- 01Ana Okafor, owner of the rulebookProposes a rule in plain words: migrations that drop a column need a backfill window.
- 02Her agentDrafts ENG-R12, with the changes from last quarter it would have caught.
- 03The rulesA rule changes only by a person’s decision, and keeps its versions (ORG-R03).
- 04Ana OkaforApproves; the rulebook becomes version 13.
- 05Every service’s agentChecks the next migration against ENG-R12 before it counts.
Where the decisions sit
Decision, who decides, up to where, and above that whom.
- A new rule, or a change to oneDecides: the owner of the rulebookUp to: the rulebook as publishedAbove that: the CTO
- An exception to a ruleDecides: the practice leadUp to: recorded, with an owner and a review dateAbove that: the department head
- A change to a shared check or workflowDecides: the practice lead that owns itUp to: a new version; teams adopt on their scheduleAbove that: teams informed, never surprised
How much the agent decides, to start. Asks every time: a rule never changes without a person. The agent drafts the rule and checks every change against the rulebook.
The record it leaves. Every version of the rulebook, who approved it, and every check each rule ran.
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
Rulebook · version 13
Checked before it counts
- ENG-R02Tests pass on the branchPasses
- SEC-R04No new secretsPasses
- ENG-R12 · newMigrations that drop a columnNeeds a window
- ENG-R11Rollback plan attachedPasses
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
- The rules could learnWhen a rule keeps escalating, the agent proposes the change.
- Code review and release that keep pace with coding agentsEvery pull request to its owner; above a limit, up the escalation matrix.
- Security and compliance gatesFindings become requests; critical ones reach the security lead the same day.
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.