Conversation
In a codebase that gates new behavior behind feature flags, "is this flagged?" was a decision no pass asked — it got invented mid-ticket or skipped. New grounding step, same shape as design posture: record once per project whether a rollout mechanism exists (none / flags / staged) and where its convention lives, CLAUDE.md-first. When it does: Pass 1 requires a per-feature Rollout: line; Pass 3 marks each ticket that ships behind the flag 🚩 (soft signal, like 🎨) and, for a temporary flag, adds a cleanup ticket to the DAG blocked by the last flagged one — removing a flag is work, and work gets a node. Ticket detail and Fork A issue descriptions carry a one-line Rollout: field. dstack-ticket calls the marker out; dstack-yolo confirms the flag is wired and defaults per the convention before [x]. Unset → none. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Roadmap item 4 (
meta/roadmap-0.4.md). Based on #6; GitHub retargets tomasteronce #6 merges. Independent of the other feature PRs (if #8 or #9 also land, the spec's principles list needs a one-line renumber — each adds an "18.").The improvement note was app-specific ("this app uses feature flags — dstack should ask"). Built as the general form, with flags as the main case:
none(recommended default; recorded, not skipped) /flags/staged(beta cohort, per-tenant, canary). Forflags/staged, the convention (flag service, naming, add/toggle/remove, cleanup expectation) is locatedCLAUDE.md-first, exactly like the repo profile. Persists asrollout_posture/rollout_convention_location; unset →none.x, default off, visible to … or not flagged, because …. Unknown → a ledger row, never silence.tickets/<id>.mdand Fork A issue descriptions carry a one-line Rollout: field (flag, default, cleanup ticket) — the "guidance for Linear issues" the note asked for.dstack-ticketcalls 🚩 out like 🎨;dstack-yoloStep 6 confirms the flag is wired and defaults per the convention before[x](mismatch → re-spec note, not a silent ship; a flag that turned out permanent drops its cleanup node in the same commit).rollout_posture: nonewith the reason (digest is opt-in per user — the toggle is the gate) and shows the 🚩 legend line. README: walkthrough step 2, Decision guide entry, FAQ fallback.Verification
./install.shinto a scratch repo; greprollout_posture/ 🚩 across spec, skill, commands, example, README.🤖 Generated with Claude Code
https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr