Skip to content

docs(constitution): add "User-Facing Fixes Ship Live" standard #800

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JKHeadley wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(constitution): add "User-Facing Fixes Ship Live" standard #800

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/STANDARDS-REGISTRY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,6 +286,12 @@ The Root says *enforce behavior in structure, not willpower.* This family is **w
**Earned from.** "Simple" fixes that quietly broke neighboring behavior because no one looked past the immediate change.
**Traces to the goal.** A self-evolving system changes itself constantly; uninspected change is how it fragments.

### User-Facing Fixes Ship Live
**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.
**In practice.** Before reaching for the dark gate, ask: is this a new capability, or a correction to a surface the user already sees? A correction shipped dark is invisible on exactly the agents whose behavior was reported — the reporter concludes nothing improved while the system believes it's fixed. If the fix's judgment genuinely needs validating, bake the *judgment* in production (fail-open, audit logs, per-agent off-switch) — not the *visibility*.
**Earned from.** The update-noise fixes (#698/#755, 2026-06-04): 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.
**Traces to the goal.** A fix the user can't see doesn't close their loop — coherence includes the user's experience of the system actually changing when they ask it to.

---

## Interaction — the agent's surface to the user and the world
Expand Down
Loading