Examples

CIRK in practice.

Each vector maps to concrete execution behavior, with reasoning for each dimension.

Backend

Frontend

Agent

C1 I1 R1 K1 → 4 Trivial

Fix null check in cart total

C1 single function, local fix I1 deterministic fix R1 low review burden K1 safe, localized fix
✓ Autonomous execution ✓ Auto-approval allowed
C1 I1 R1 K1 → 4 Trivial

Update button color token

C1 local visual change I1 deterministic implementation R1 minimal review burden K1 low rollout risk
✓ Autonomous execution ✓ No checkpoints needed
C1 I1 R1 K1 → 4 Trivial

Rename internal variable and update references

C1 local, contained change I1 deterministic, no ambiguity R1 lightweight validation enough K1 no release risk
✓ Agent executes directly ✓ Lightweight validation only
C2 I2 R3 K1 → 8 Medium

Login API

C2 moderate context across auth components I2 validation and edge cases require iteration R3 security-sensitive — strong review required K1 rollout can remain contained
✓ Agent can prepare implementation ⚠ Human review mandatory ⚠ Auto-merge disabled
C2 I3 R2 K2 → 9 Medium

Dashboard layout revision

C2 touches multiple components I3 UX refinement requires iteration R2 functional review, not architectural K2 changes existing behavior
⚠ Draft-first required (I3) ⚠ Human review before merge
C2 I3 R2 K2 → 9 Medium

Refactor repository layer for shared patterns

C2 shared patterns across modules I3 exploratory, convergence uncertain R2 review before full implementation K2 changes existing behavior
⚠ Agent proposes plan first (I3) ⚠ Review before implementation
C2 I2 R3 K3 → 10 Complex

Billing webhook change

C2 touches business-critical logic I2 correctness may require several cycles R3 review is mandatory K3 bad rollout can create financial issues
× Supervised execution × Approval per step × Deploy runbook required
C3 I3 R3 K2 → 11 Complex

Auth UI redesign (login + recovery flows)

C3 cross-flow understanding required I3 multiple design and functional iterations R3 UX + correctness review required K2 changes a critical entry point
× Supervised execution × Approval per step × Architect sign-off required
C3 I2 R3 K3 → 11 Complex

Migrate payment gateway provider

C3 cross-system payment flow understanding I2 multiple verification cycles expected R3 mandatory human review K3 rollout must be staged and monitored
× Supervised execution × Staged rollout required × Deploy runbook mandatory

Template

Copy-paste scoring template.

Use this template when scoring a task with your team.

Task: [describe the task]

C: _ (1-3)  Context — how much system understanding?
I: _ (1-3)  Iteration — how many cycles to converge?
R: _ (1-3)  Review — how much human validation?
K: _ (1-3)  Integration Risk — how risky is rollout?

Score: _  (C + I + R + K)
Policy: _ (autonomous / guided / draft-first / supervised / blocked)