Every change takes the same path to production

Your session and the line's agents ship through the same Check, Review and Decide. Fixes trace back to the change that caused them, and that record sets how much each role may merge without a person.

SignalsTriageBuildNew issuesFailed jobsEval redsTeammate reportsquietJudge mistakesstoppedbugregressionprompt_miss17 queued23 openThe lineFix checkRevise↺ Back to signals2 regressedWork a person startsWork the line startsA person decidesAutomated checkBack to its sessionA regression2,276signals today1,8923117315532 runningfreefreeA person's sessionShips through a flowCheckReviewDecideLandDeployLiveWatch7 days47 watchingClosed clean2 on a person42 live today

Signals

A signal is one piece of evidence: a Sentry error, a red eval, a PostHog alert, a teammate's report. You choose the sources. Every signal goes through one door, signals.ingest, where four rules in order decide whether it joins an open problem, opens a new one, or stays as evidence.

A source that sends nothing for 14 days, or reports erroring or paused, is stopped and turns red. One that is late against its own rhythm is quiet and stays grey.

ct-4182Checkout total throws on an empty cart
  1. Signal
  2. Triage
  3. Build
  4. Checks
  5. Live
  6. Watch
  7. Traced
joined at Fingerprint42 signals
Arrivingsignals.ingest
evalsOnboarding eval red
eval:onboarding-tool-v2
  1. 1
    Fingerprint
    same key on an open problem
  2. 2
    Judge3 closest
    a small model picks one, or unsure
  3. 3
    New
    a person, a lesson, or a finder
  4. 4
    Held
    evidence only, no task
Send one through
Open problems21 open
  • Checkout total throws on an empty cart
    sentry:checkout-total
    41signals
  • Onboarding skips a tool
    eval:onboarding-tool
    6signals
  • Archived docs rank first
    issue:search-archived
    3signals
… 18 more open
Held as evidence
no task
128signals
Loop › Sources to watch2,276 signals today3 feeding2 silent
New issuessentry · 1,892 today
flowing0d ≤ 2×1d
Failed jobsci · 311 today
flowing0d ≤ 2×1d
Eval redsevals · 73 today
flowing0d ≤ 2×2d
Teammate reportsperson
now 6dlimit 2×1d
quiet6d > 2×1d
Judge mistakesjudge
nothing in 14 days
stopped

Triage and build

A person sends finished work with cast flow run change, or Ship in the app. The session's edits freeze into a commit on its own branch, so nothing moves in the shared checkout.

The line builds everything else, starting from the problems signals open. Ground labels each new problem, ready ones queue by score, and each run takes a free slot on a machine.

ct-4182Checkout total throws on an empty cart
  1. Signal
  2. Triage
  3. Build
  4. Checks
  5. Live
  6. Watch
  7. Traced
frozen from a person's sessiona41c9e2
A person's sessionjx7m4q2
ct-4182Checkout total throws on an empty cartrun bound
cast flow run changeorShip
--session (default)--task--branch--pr
  1. editspackages/web/lib/cart/total.ts+2 −4packages/convex/convex/checkout.ts+3 −1
  2. commita41c9e22 files frozen
  3. branchcodecast/change-ct-4182
shared checkoutmain 7c2e1f0unchanged
Findings come back to this session3 visits each
Fix checkAddress reviewReviseResolve conflict
The line
Groundevery 2 min
evalsAgent loops on cast check
goalline
categoryprompt
risklow
readinessready
Queue 17score, findings, age
1Archived docs rank first644f5d
2Export fails in Safari503f1d
3Agent loops on cast check501f0d
50 unscored
Machinesmost free slots wins
mini-11 free
deploy-smokeonboarding
laptop1 free
studiooffline
On a personno slot
billingdocs-404
Check
same checks, every change

Check, Review and Decide

A change written by hand passes the same Check, Review and Decide as one an agent wrote overnight. Every way back runs in the session the change came from and returns to Check on a fresh snapshot.

Each way back may run 3 times; a fourth ends the run. Decide waits on a person: S ships, R sends a note back, D drops it. What lands is the snapshot Review approved and Decide accepted.

ct-4182Checkout total throws on an empty cart
  1. Signal
  2. Triage
  3. Build
  4. Checks
  5. Live
  6. Watch
  7. Traced
approved, shipped at Decidec92e1a4
Checkout total throws on an empty cartct-4182Changefix(web): total of an empty cart is 0Live
SessionCheckReviewDecideLandRebaseLandDeployLive↺ Checks failed↺ Changes askedRejected↺ ReviseDroppedAlready landed↺ ConflictNot shippedDeploy failedFix check 1/3Address review 1/3Revise 0/3Resolve conflict 0/3
Liverun complete
Live: e3f0a71 on web dp-411, backend dp-412.
webdp-411backenddp-412climobiledesktop
Review approved c92e1a4=Decide accepted c92e1a4rebased onto maine3f0a71
nextct-4182 watchedNov 4 to Nov 11Ship and watch
Snapshotseach way back checks a new one
  1. a41c9e2
    frozen
  2. 7d03b5f
    after Fix check
  3. c92e1a4
    approved
  4. e3f0a71
    rebased onto main
Run log14 / 14
  1. 01Sessionfrozen into a commita41c9e2
  2. 02CheckChecks faileda41c9e2
  3. 03Fix checkvisit 1 of 3
  4. 04CheckPassed7d03b5f
  5. 05ReviewChanges asked7d03b5f
  6. 06Address reviewvisit 1 of 3
  7. 07CheckPassedc92e1a4
  8. 08ReviewApprovedc92e1a4
  9. 09Decidewaiting on a personc92e1a4
  10. 10DecideShipS
  11. 11Rebaseonto mainc92e1a4
  12. 12Landon maine3f0a71
  13. 13DeployWait for live, parked2 targets
  14. 14Liveweb, backenddp-411, dp-412

Land, deploy and watch

A change that passes lands on main and goes out with the next deploy of each target whose paths it touches. The run parks, holding no slot, until every one of them is live. The problem it fixed is done after 7 quiet days counted from that moment.

ct-4182Checkout total throws on an empty cart
  1. Signal
  2. Triage
  3. Build
  4. Checks
  5. Live
  6. Watch
  7. Traced
watched Nov 4 to Nov 11dp-411, dp-412
Landed on main, Nov 3
e3f0a71 fix(web): total of an empty cart is 0
  • packages/web/lib/cart/total.tsweb
  • packages/convex/convex/checkout.tsbackend
Deploy targets
webon a pressruns: pushlivedp-411
packages/web/**packages/shared/**platform/**
backendon a presslivedp-412
packages/convex/**packages/shared/**platform/**
Deploy 3 commitse3f0a71c2d7f185e08b7ca93d2f4 is web only
clion a pressnot touched
packages/cli/**packages/shared/**platform/**
mobileon a pressnot touched
packages/mobile/**packages/shared/**
desktopon a pressnot touched
packages/electron/**
policy
on a press a person's Deploy
auto CI on main green
runs
runs: push deploys itself when main moves
main, newest first
  1. 5e08b7cfix(convex): close watches in batches
    backend dp-412
  2. a93d2f4chore(web): rail spacing
    web dp-411
  3. c2d7f18feat(convex): carry list per session
  4. e3f0a71fix(web): total of an empty cart is 0landed
deploys whose sha has e3f0a71 as an ancestor
cast flow await-deploydone
Live: e3f0a71 on web dp-411, backend dp-412.
Live
The watch, 7 days from live
Landed Nov 3Live dp-412 Nov 4until Nov 11
LandedNov 3
Live dp-412Nov 4
Nov 5
Nov 6
Nov 7
Nov 8
Nov 9
Nov 10
Nov 11
set at landinguntil Nov 10
re-anchored at live
watch_from7 days, never shortenedwatch_until
If production stays quiet Closed clean
ignored
Watch ended quiet
If a report arrives Nov 7 Open, back in the queue
watch cleared
Reopened during watch

Tracing a fix back to the change that caused it

Every night at 03:30 UTC codecast reads what landed on main and blames the lines each fix removed or changed at the commit before it. The commit that gave the fix the most lines is the top introducer. It counts as regretted when the fix lands inside that change's window.

A weekly routine files confirmed causes as signals. The Loop's Back to signals counts come from somewhere else. They count shipped problems a finding reopened in the last 14 days.

ct-4182Checkout total throws on an empty cart
  1. Signal
  2. Triage
  3. Build
  4. Checks
  5. Live
  6. Watch
  7. Traced
blamed 3 lines to 3e9b2a03e9b2a0
Nov 4, the night after e3f0a71 landed
cast line fixloop03:30 UTCmainfeat(web): totals from line items3e9b2a0refactor: currency81d4c6ffeat(web): couponsd05a7b3fix(web): total of an empty cart is 0e3f0a71bug task · fix story · fix subjecttotal.ts +2 −4, blamed at e3f0a71^-const first = items[0];3e9b2a0-let sum = first.price * first.qty;3e9b2a0-for (const i of rest) sum += line(i);3e9b2a0-return round(sum, cart.cur);81d4c6f+const sum = items.reduce(add, 0);+return round(sum, cart.currency);3 linestop introducer, regretted1 linenot top3e9b2a0.fixed_by += { e3f0a71, lines: 3, top: true }Totals from line itemsjx7k2qaCodecast-Session, the Checkout line
cast line fixloop03:30 UTC
e3f0a71 fix(web): total of an empty cart is 0
bug taskfix storyfix subject
total.ts +2 −4, blamed at e3f0a71^
-const first = items[0];3e9b2a0
-let sum = first.price * first.qty;3e9b2a0
-for (const i of rest) sum += line(i);3e9b2a0
-return round(sum, cart.cur);81d4c6f
+const sum = items.reduce(add, 0);
+return round(sum, cart.currency);
blame
3e9b2a03 lines, top, regretted
81d4c6f1 line, not top
Totals from line items jx7k2qaCodecast-Session, the Checkout line
The Loop
Back to signals2 regressed2 reopened by a findinglast 14 days
Weekly fix-loop routine
confirmed causeszz:3e9b2a0 Signals, same door

The regret-free rate

Each change gets a window: the 75th percentile of how long fixes took to follow a live change, over the last 60 days, rounded up to whole days, between 1 and 30. A change is regretted if a fix naming it as top introducer lands, or its problem reopens, inside that window. The rate is regret-free over settled changes, kept apart for Line, Person and No flow.

ct-4182Checkout total throws on an empty cart
  1. Signal
  2. Triage
  3. Build
  4. Checks
  5. Live
  6. Watch
  7. Traced
Checkout's rate after the trace89% < 90%
days from going live to its top fix, last 60 days
window
6days
fixes traced
20
75th lag
#15, 5.3d
rounded up
6 days
bounds
1 to 30 days
day 30 of 30each change waits 6 days from going live
Regret-free share of settled changes, last 60 days
Line
92%
of 164 settled, 3 partial
Person
90%
of 120 settled, 1 partial
No flow
84%
of 912 settled, 3 partial
  • partial window open, not counted yet
  • regret-free window closed clean
  • regretted top fix or reopen inside it
  • after the window does not count
The last 30 days, change by change; earlier settled changes count in the rates above
Linea role's run+160 settled earlier
Persona session's flow+113 settled earlier
No flowno check flow+895 settled earlier

How much a role merges without a person

A role's merge step decides by Count, a daily limit, or by Rate. On Rate the role merges without a person only while its own regret-free rate clears a bar over enough settled changes, and the daily limit still applies. Only a role admin, from the role's settings, switches between them.

Checkout merges on Rate, 90% over at least 20. The trace made 3e9b2a0 regretted, its rate fell to 89%, and its next changes wait In Review for a person.

ct-4182Checkout total throws on an empty cart
  1. Signal
  2. Triage
  3. Build
  4. Checks
  5. Live
  6. Watch
  7. Traced
Checkout's next changesIn Review
Checkout merge step
On
merge grant, 5 a day, expires in 90 days
Decides by
role admin, either way
Who sets the mode
  • Role adminsets it
  • Sessionrefused
  • API tokenrefused
Only a person sets how the merge step decides, from the role's settings
Checkout line changes
settled37
min 20
regret-free, 4 regretted89%
bar 90%
3e9b2a0regretted: top introducer of e3f0a71, inside its window
Today, asking to merge
0 merged, limit 5
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
In Review
the role's regret-free rate is 89%, under its bar of 90%
changes 1 to 6 wait for a person; the runs are not failed
  1. role adminline_merge_rate: count → 0.9/20

The flow library

Flows are built from segments. Change is Check, Review, Decide, Land and Deploy in a row, and Quick is Change without Decide. A team can extend any flow with its own steps or write a new one.

line17 steps, 8 ends
Ground
Park
Plan
Analyze
Prove
Red
Implement
Verify
Green
Eval
Unscored
Review
Rejected
Card draft
Present
Card
Decide
↺ ReviseDrop
Rebase
Ship
Watch
Exit
DissolveUnprovenStopped

Run your first change through a flow

Checkout
Checkout: 89%
under its 90% bar, so its next changes wait for a person
3e9b2a0 settled as regretted, 33 of 37 regret-free
Roles
7 of 17
roles merge without a person, Checkout waits

Install codecast and open Flows in your workspace. The Library holds the standard flows. Send the next change you finish through Change, and the Loop fills in as your team's work moves through it.

Script
curl -fsSL codecast.sh/install | sh
Also via brew install codecast-sh/tap/codecast or npm install -g @codecast-sh/cli
Taking longer than usualOffline · reloads when back