Uh oh!
There was an error while loading. Please reload this page.
docs(standards): tickets always carry a Status; bugs go straight to Ready (backend#1602) - #195
Merged
Merged
Conversation
…eady (backend#1602) Team-consolidation round, requested by Lukas 2026-08-10: every ticket on the board carries a Status — new tickets start in Backlog; bugs are the exception (work-type:bug label, straight into Ready — defects don't wait for refinement). Mechanization candidates once agreed (per the canon's meta-rule, the prose then shrinks): default Status=Backlog on add-to-kanban, and a labeled-trigger hop work-type:bug -> Ready. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
saadqbal
approved these changes
Aug 10, 2026
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Team-consolidation round on the org standards (requested by Lukas): two board-hygiene rules added to the Engineer kanban section of the canon:
Status— no card sits at "No Status". New tickets start inBacklog.work-type:buglabel (the Bug template applies it) and straight intoReady— defects don't wait for refinement.One bullet, placed first in the section (ticket lifecycle precedes pickup). Nothing else changed — diff is the single bullet.
Type
Docs (process/standards).
Test plan
org-standards.mdbyte-identical to live canon before the editcreate-prsdispatch propagates the block to all 19 repos (I'll run it and merge the sync PRs per the standing flow)Note on mechanization
Both rules are automatable later (default
Status=Backlogin add-to-kanban; a labeled-triggerwork-type:bug → Readyhop). Per the canon's own meta-rule, once a check carries a rule the sentence gets deleted here — this PR ships the prose so the team can align on the behavior first.Part of tracebloc/backend#1602.
🤖 Generated with Claude Code
Note
Low Risk
Process documentation only; no runtime, security, or data-handling changes.
Overview
Adds Engineer kanban board-hygiene rules to the org-wide canon in
org-standards.md: every ticket must have aStatus(no "No Status"; new work starts inBacklog), with bugs as the exception—work-type:bug(from the Bug template) goes directly toReadywithout waiting for refinement.The bullet is placed first in that section so ticket lifecycle precedes pickup rules; no other sections or bullets change.
Reviewed by Cursor Bugbot for commit 95365ce. Bugbot is set up for automated code reviews on this repo. Configure here.