Expose preference history only to its subject and scoped support role
A support page returns all members’ preference histories after checking only that the requester has any staff role.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Access control · Minimal disclosure
Estimated field mix
- Security50%
- Privacy engineering50%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional event workspace offers optional product announcements and operational booking messages. Its product policy treats these as separate purposes. A stale audience cache currently sends optional messages after a member opts out. The brief implements fictional preference rules and makes no legal-consent certification.
Setup prerequisites
- Create synthetic members, versioned notice text and two purpose-tagged message types.
- Use a fake dispatch provider with controllable queueing and acknowledgement; send no real messages.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- RCONSENT-101 · Separate optional announcements from booking operations
- RCONSENT-102 · Record the notice version shown when a preference changes
- RCONSENT-103 · Make the preference form submit the user’s explicit final choice
- RCONSENT-104 · Recheck optional-message eligibility immediately before provider dispatch
- RCONSENT-105 · Bind a queued announcement to its purpose and content revision
- RCONSENT-107 · Explain which queued messages an opt-out can still prevent
Acceptance criteria
- Apply subject or tenant-scoped support authorization at the repository boundary.
- Return purpose, choice, notice version and time without unrelated contact details.
- Audit privileged history access using safe identifiers and bounded reason categories.
Implementation constraints
- An audit event records access, not an inference about why a person made their choice.
Verification to include
- Read the matching subject’s history and an authorized support fixture.
- Attempt a foreign-tenant subject and an unscoped staff role; verify denial and no history leakage.
Deliverables
- Scoped history endpoint and access regressions
Rollout and recovery
Enable the history view after repository-level checks pass; keep analytics separate from preference content.
Value of the work
For the engineer: Practice purpose modeling, versioned user choices, dispatch-time checks and consistency under retries.
For the team: Create an inspectable preference workflow that can be reviewed against a company-approved communication policy.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.