rouse-context/docs/internal
Jason Monk 7c8a91b9f9
Add UX changes rule + decision log + onboarding flow page (#397)
Three pieces, one PR:

1. `.claude/rules/ux-changes.md` — auto-loaded rule listing change categories
   that require explicit user approval before implementation, plus a
   decision-log entry. Filing an issue with a ranked recommendation is
   explicitly NOT approval.

2. `docs/ux-decisions.md` — append-only log of UX flow decisions. Seeded
   with the #389 cert-provisioning-at-Continue decision, retroactively
   approved (was originally landed unilaterally; this rule + log exist
   so that cannot recur).

3. `docs/internal/flows/index.html` — onboarding flow page composed of
   existing roborazzi screenshots, wired together with action labels +
   error-branch screens (Rate limited, Failed). Linked into the existing
   internal dashboard as a new Flows tab.

The motivating incident: #389 moved cert provisioning from "first
integration add" to "right after Continue, before Home". That is a real
UX timing change that an agent picked unilaterally based on a ranked
recommendation in the issue body. The user spotted the change after the
fact ("immediately after the notifications screen its showing
registering, before any integrations are set up") and asked for a
structural check that survives across Claude sessions, not just a memory
entry.
2026-04-24 19:39:08 -04:00
..
flows Add UX changes rule + decision log + onboarding flow page (#397) 2026-04-24 19:39:08 -04:00
index.html Add UX changes rule + decision log + onboarding flow page (#397) 2026-04-24 19:39:08 -04:00
logging.md Fix #379: Scrub sensitive data from production logs + add regression gate (#380) 2026-04-23 12:07:54 -04:00