ProductsPlan and share
Planning
Plan work. Track it through release.
Issues connected to branches, reviews, and builds.
Work
IssuesCyclesProposals
Cycle 14
ActiveSep 15 – Sep 28CHK-41Retry storms on 5xxfeat/retry-budget#418SC
CHK-44Backoff ignores Retry-After#419VP
CHK-46Ledger double-append◆
CHK-47Budget per-tenant retries
CHK-49Surface retry budget in adminVP
CHK-38Idempotency key on /charge#412SC
CHK-39Timeout budget per hopVP
For teams whose board drifts from the code
Issues are updated by hand, so the board is always a step behind what actually shipped.
How ReasonOS fixes it
01
Status from the code
An issue starts when its branch opens and completes when its change merges.
02
Cycles and initiatives
Plan in cycles, group work into initiatives and follow progress on a burn-up chart.
03
Hand issues to agents
Assign an issue to a coding agent and it works on a branch of its own.
Try it on your next branch.
Your team and your agents join with a link.