Skip to main content
ClrSlate
Request a demo

Solution · Change to a shared standard

Your procedure, run by the agent

The procedure you already follow, with an owner and a version, run step by step, with you at the step that decides.

Request a demo

Key due, then Priya decides, then Rotated.

Who decides · Priya Nair · Security lead · the production cutover

How it runs

A runbook that lives in a wiki becomes a procedure with an owner, numbered steps and versions. The agent runs the steps it may; the person takes the step that decides; the run is on the record.

A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.

  1. Agent carries09:00
    Calendar: the signing key for payouts is due for rotation
  2. Agent carries09:02
    Procedure “Key rotation · version 2” started: new key generated, staged, verified on staging
  3. Rules check09:20

    SEC-R07

    a production key cutover is decided by the security lead

  4. Person decides11:00
    Priya approves the cutover; the agent completes the run
  5. Agent carries11:05
    Version 2 ran clean; one step proposed for version 3
up the escalation matrix, by rule a person decides

Your calendar

Tuesday 09:00

Key rotation due · payouts signing key

Procedure “Key rotation · version 2” starts on the security seat

Drawn as your tool shows it; ClrSlate adds the line that names the owner.

Illustration · Halden, a fictional company

Step by step

Who takes each step, in order.

For

  1. 01The calendarA trigger starts the procedure at its current version: the payouts signing key is due for rotation.
  2. 02The security seat’s agentRuns the steps it may: a new key generated, staged and verified on staging.
  3. 03The rulesA production key cutover is decided by the security lead (SEC-R07).
  4. 04Priya Nair, security leadApproves the cutover with the verification results in front of her.
  5. 05The agentCompletes the run, and proposes one step for version 3.

Where the decisions sit

Decision, who decides, up to where, and above that whom.

  • A step that touches stagingDecides: the agentUp to: the procedure as versionedAbove that: the procedure’s owner
  • The step that decides: a production key cutoverDecides: the security leadUp to: the procedure as versionedAbove that: the CTO
  • A change to the procedureDecides: the procedure’s ownerUp to: a new versionAbove that: the next seat up

How much the agent decides, to start. Within limits: steps that touch staging run alone; the production step asks the procedure’s owner every time.

The record it leaves. The run, each step and who took it, and every version of the procedure.

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

Procedure · owner Priya Nair

Key rotation · version 2

  • 1 · Generate the new keyAgentDone
  • 2 · Stage and verify on stagingAgentDone
  • 3 · Production cutoverSEC-R07Needs Priya
  • 4 · Retire the old keyAgentNext
The procedure, its version and the step that asks.

The tools it runs through

We connect to the systems you run, and build the connection before the demo.

What it uses

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.

Request a demo