Bind export creation to the current authorized subject
The endpoint accepts any member ID and relies on the UI to submit the current user.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Authorization · Repository boundaries
Estimated field mix
- Security60%
- Privacy engineering40%
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 learning workspace offers a member a portable copy of their own profile, notes and activity settings. Shared documents contain contributions from other people. The product export policy specifies included fields and shared-record handling; this is an engineering exercise, not a legal portability claim.
Setup prerequisites
- Create synthetic members, private notes and shared-document contributions in a local database.
- Provide fake queue and object-storage adapters with controllable expiry and failure.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Resolve export scope from the authenticated subject and approved workspace access.
- Reject substituted IDs and revoked sessions before queueing work.
- Record a safe operation reference without embedding personal fields in job identifiers.
Implementation constraints
- Authorization also belongs at the data-access boundary used by background assembly.
Verification to include
- Create an export as the matching synthetic member.
- Attempt another member’s ID and a revoked membership, checking that no job or artifact is created.
Deliverables
- Scoped export command and cross-subject denial tests
Rollout and recovery
Deploy command and repository checks together before queue activation.
Value of the work
For the engineer: Practice export scoping, consistency, streaming and expiring access without leaking other members’ data.
For the team: Create a reviewable export contract and cross-subject regression suite for an approved product 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.