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.
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.
- Signal
- Triage
- Build
- Checks
- Live
- Watch
- Traced
signals.ingest- 1Fingerprintsame key on an open problem
- 2Judge3 closesta small model picks one, or unsure
- 3Newa person, a lesson, or a finder
- 4Heldevidence only, no task
- Checkout total throws on an empty cart
sentry:checkout-total41signals - Onboarding skips a tool
eval:onboarding-tool6signals - Archived docs rank first
issue:search-archived3signals
sentry · 1,892 todayci · 311 todayevals · 73 todaypersonjudgeTriage 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.
- Signal
- Triage
- Build
- Checks
- Live
- Watch
- Traced
jx7m4q2cast flow run changeorShip- editspackages/web/lib/cart/total.ts+2 −4packages/convex/convex/checkout.ts+3 −1
- commita41c9e22 files frozen
- branchcodecast/change-ct-4182
main 7c2e1f0unchangedCheck, 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.
- Signal
- Triage
- Build
- Checks
- Live
- Watch
- Traced
- a41c9e2
- 7d03b5f
- c92e1a4
- e3f0a71
- Sessionfrozen into a commita41c9e2
- CheckChecks faileda41c9e2
- Fix checkvisit 1 of 3
- CheckPassed7d03b5f
- ReviewChanges asked7d03b5f
- Address reviewvisit 1 of 3
- CheckPassedc92e1a4
- ReviewApprovedc92e1a4
- Decidewaiting on a personc92e1a4
- DecideShipS
- Rebaseonto mainc92e1a4
- Landon maine3f0a71
- DeployWait for live, parked2 targets
- Liveweb, 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.
- Signal
- Triage
- Build
- Checks
- Live
- Watch
- Traced
- packages/web/lib/cart/total.tsweb
- packages/convex/convex/checkout.tsbackend
- policy
- on a press a person's Deploy
- auto CI on main green
- runs
- runs: push deploys itself when main moves
- 5e08b7cfix(convex): close watches in batchesbackend dp-412
- a93d2f4chore(web): rail spacingweb dp-411
- c2d7f18feat(convex): carry list per session
- e3f0a71fix(web): total of an empty cart is 0landed
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.
- Signal
- Triage
- Build
- Checks
- Live
- Watch
- Traced
const first = items[0];3e9b2a0let sum = first.price * first.qty;3e9b2a0for (const i of rest) sum += line(i);3e9b2a0return round(sum, cart.cur);81d4c6fconst sum = items.reduce(add, 0);return round(sum, cart.currency);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.
- Signal
- Triage
- Build
- Checks
- Live
- Watch
- Traced
- fixes traced
- 20
- 75th lag
- #15, 5.3d
- rounded up
- 6 days
- bounds
- 1 to 30 days
- partial window open, not counted yet
- regret-free window closed clean
- regretted top fix or reopen inside it
- after the window does not count
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.
- Signal
- Triage
- Build
- Checks
- Live
- Watch
- Traced
- Role adminsets it
- Sessionrefused
- API tokenrefused
3e9b2a0regretted: top introducer of e3f0a71, inside its window- 1
- 2
- 3
- 4
- 5
- 6
- role admin
line_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.
Agents send their own finished work through a flow, and read a flow's steps before they do.
Related features
Decide, and every other step that waits on a person, lands in the same queue as the rest of your decisions.
A run of Change can start from a pull request, and the PR page shows which session wrote each line.
The session that shipped a change can arm a follow-up that checks on it once the deploy is live.
Every landed change links back to the session that wrote it, which is how a fix finds who caused it.
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.
curl -fsSL codecast.sh/install | shbrew install codecast-sh/tap/codecast or npm install -g @codecast-sh/cli