docs(constitution): add "User-Facing Fixes Ship Live" standard#800
Open
JKHeadley wants to merge 1 commit into
Open
docs(constitution): add "User-Facing Fixes Ship Live" standard#800JKHeadley wants to merge 1 commit into
JKHeadley wants to merge 1 commit into
Conversation
Ratified by Justin (topic 18250, 2026-06-04, "Yes, flip it live and codify the standard"). Earned from the update-noise fixes: the #755 relevance gate was drafted dark-on-fleet, which would have hidden the fix from exactly the agents whose noisy updates Justin reported — he caught it pre-merge. The rule: UX bug fixes ship live fleet-wide by default; the dark/ developmentAgent gate is reserved for new capabilities whose failure could break something. If a fix's judgment needs validating, bake the judgment in production (fail-open, audit logs, off-switch) — not the visibility. Clean docs-only constitution amendment per the established amendment loop (no spec/trace/fragment; docs/ is out of instar-dev scope). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Constitution amendment — ratified by Justin (topic 18250, 2026-06-04)
Adds User-Facing Fixes Ship Live to the Shipping section of
docs/STANDARDS-REGISTRY.md.Rule. A change whose purpose is to fix what the user experiences ships live fleet-wide by default. The dark/developmentAgent gate is for new capabilities whose failure could break something — never for UX bug fixes, whose worst case is the bug persisting.
Earned from. The update-noise fixes (#698/#755): the relevance gate was drafted dark-on-fleet, so the user whose screenshots of noisy fleet agents motivated the fix would have seen zero improvement on the agents he was watching. Caught pre-merge, by him.
Clean docs-only amendment per the established amendment loop (no spec/trace/fragment — docs/ is out of instar-dev scope, precedent PR #731). Companion to the #755 rollout flip, which applies this standard.
🤖 Generated with Claude Code
ELI16 — fixes to what you experience don't ship hidden anymore
We have a habit of shipping new features "dark" — built and merged, but switched off everywhere except the development agent, so they can be watched safely before the whole fleet gets them. That's right for risky new capabilities. But we applied it to a bug fix — the update-noise fix — and that meant the person who reported the noise would have seen zero improvement on the agents he was actually watching: the fix existed, but was invisible exactly where it was needed. This amendment writes the lesson into the constitution: if a change exists to fix what the user experiences, it ships live everywhere by default. The dark switch is reserved for new capabilities whose failure could actually break something. And if a fix's judgment really needs a trial period, you keep the safety rails (it fails open, logs every decision, has an off-switch) — you don't keep the fix invisible.