Kiket docsBuild your first monitored process
Author a contract-review process in the Modeling Cockpit, simulate before merge, and ship file-backed YAML in about 15 minutes.
By the end of this walkthrough you'll have a three-state monitored process with an SLA, a two-person approval chain, and an automation that posts to Slack on breach. Every step is doable in the Modeling Cockpit — we'll also show the YAML so you can see what the editor writes.
Prefer YAML-first? Paste the workflow at the bottom of this page into .kiket/workflows/contract_review.yaml in your workspace configuration repository and open it in the Modeling Cockpit to verify structure and run simulation.
Goal: a contract-review process
You need legal to review every contract, CFO to co-sign anything over $100k, and the team to be paged if review drags past 48 hours.
Open the Modeling Cockpit
From the workspace sidebar, open Processes and click New process (or open an existing process and choose Edit in Modeling Cockpit). Enter a key (contract_review), a name (Contract Review), and confirm.
You'll land in the Modeling Cockpit with an empty canvas and a single Intake state pre-dropped. The editor opens .kiket/workflows/contract_review.yaml in your linked configuration repository.
Add the Legal Review state
Click + Add state in the toolbar. Name it Legal Review. The canvas places it to the right of Intake; drag it wherever you like.
Click the state to open its inspector. In the Category dropdown, leave it as Active.
Connect Intake → Legal Review
Hover Intake; a small arrow appears on its right edge. Drag from the arrow to the Legal Review state. A transition is created. Click the transition itself to name it — Start review.
Add the SLA
Back in the inspector for Legal Review, scroll to SLA. Set:
- Warning:
24h(notify team early) - Breach:
48h(escalate to on-call)
Save the file. Autosave commits YAML to your workspace repository; you'll see a brief save indicator in the header.
What just happened?
The Modeling Cockpit wrote .kiket/workflows/contract_review.yaml in your configuration repository. Open the repo on GitHub to inspect the diff — canvas and YAML are the same source of truth.
Add the approval chain
Still in the Legal Review inspector, scroll to Approval. Click Add approver. Pick counsel (the counsel group in your org). Add another approver: cfo. Leave the type as Sequential.
Now any transition out of Legal Review requires counsel → CFO sign-off in order.
Add the Approved state
Click + Add state. Name it Approved. In the inspector, set Category to Final. Drag a transition from Legal Review to Approved and name it Approve.
Wire the breach automation
On the Legal Review state, open the inspector's Automations tab. Click Add automation and pick the trigger on_sla_breach. For the action, pick Send notification and choose your Slack channel from the dropdown (if you haven't connected Slack yet, do that first — see Your first extension).
Save. Now when a case sits in Legal Review past 48h, Slack gets a message.
Simulate before merge
Open Check change in the Modeling Cockpit toolbar (or add ?simulate=1 to the editor URL). The Impact tab forecasts guard blockers; use Cases and History to replay open cases against your edits.
Click Re-run after each change. You'll see:
- Green check when a transition is allowed.
- Red cross + reason when it's blocked (missing approval, SLA not expired, missing evidence, etc.).
Simulation is read-only against live case data using the saved workflow file — unsaved buffer edits preview until you save. Resolve blockers on the Ship tab before merging process changes to production.
Ship the process
When the Ship tab shows ready, save (if needed) and merge your configuration change through your normal git workflow. The monitored process becomes active for the workspace: operators can open cases against it, evidence adapters can link proof, and scanner runs evaluate compliance.
Your repo's .kiket/workflows/contract_review.yaml now contains everything you configured in the Modeling Cockpit.
The YAML the Modeling Cockpit wrote
key: contract_review
name: Contract Review
states:
intake:
category: initial
legal_review:
category: active
sla:
warning: 24h
breach: 48h
approval:
type: sequential
chain: [counsel, cfo]
on_sla_breach:
- notify:
channel: slack:#contracts
approved:
category: final
transitions:
- from: intake
to: legal_review
name: Start review
- from: legal_review
to: approved
name: Approve
approval_required: trueWhat's next?
Simulation cockpit
Impact, Cases, History, Tests, and Ship tabs before you merge process changes.
Editor modeling cockpit
Live lens, branch compare, and Ship verdict reference.
Workflows reference
Full YAML anatomy for monitored processes.
Connect evidence
Install an adapter so scanner runs have proof to evaluate.