Issue a short-lived download capability only after subject authorization
A predictable artifact URL lets one member retrieve another member’s completed export.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Capability security · Access control
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.
- REXPORT-101 · List exportable member fields before serializing database rows
- REXPORT-102 · Define how shared document contributions appear in a personal export
- REXPORT-103 · Bind export creation to the current authorized subject
- REXPORT-104 · Freeze the export selection without holding a long database transaction
- REXPORT-105 · Stream large note exports with bounded intermediate storage
- REXPORT-106 · Validate the export manifest before marking assembly complete
Acceptance criteria
- Authorize every capability request against the current subject and export operation.
- Scope the capability to one object and a declared short lifetime.
- Keep capabilities out of generic logs, analytics and unrelated API responses.
Implementation constraints
- Use a local storage adapter implementing the capability contract; an opaque URL alone is not authorization.
Verification to include
- Request and use a valid capability for the matching export.
- Attempt another subject’s operation, an expired capability and an altered object reference; all must fail without bytes.
Deliverables
- Download capability endpoint and scope/expiry tests
Rollout and recovery
Enable downloads only after complete artifacts exist; disable capability issuance independently during an incident.
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.