Repository navigation
docs(rfc): align card and coach facts with owner reveal (§7) - #29839
Conversation
UX Review (Opus 5.5) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Docs-only change: the §1 and §2 wording now agrees with §7, and nothing in it blocks. [DESIGN-REVIEWED] 9e00574 Description read[DESCRIPTION-READ] bc5fe65140cd62453f4ac9c426fe830c98895cc6dd96a12c73bcb96f29e2e051 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: Make the redaction RFC say one thing about whether the owner can reveal a removed credential.
#29519 added §7 Owner reveal, but its Opus 5.5 review found two older sentences that still say the value can never be shown: the §1 card's "Not saved" fact and the §2 coach text. #29519 merged before that fix landed, so main now contradicts itself.
Why it matters
Someone building the card or coach from §1 or §2 would either print "this page cannot show it" next to the Show button, or leave the decided reveal out.
Not a goal
What changed (motivation → approach → change)
docs/request-for-change/rfc-redaction-explain-and-reveal.md: the §1 "Not saved" fact and the §2 coach sentence now name the §7 exception (owner only, from gateway memory, while the gateway runs), the same way #29519 reworded fact 1 and the §4a preview.Backwards compatibility
Compatible: documentation only.
Removes nothing: no code, route, record or key changes.
Tests
Proof: not provable -- docs or config only
Manual verification
N/A — docs only.
Related Issues
Follow-up to #29519 (Opus 5.5 finding on f86d2af). Implementation: #29513.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license.