Freeze the export selection without holding a long database transaction
Notes added midway through an export appear inconsistently, and the worker holds a transaction open while uploading the archive.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Snapshot semantics · Transactions
Estimated field mix
- Database engineering50%
- Privacy engineering30%
- System design20%
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
- Declare the export consistency boundary and record a cutoff or snapshot reference.
- Keep database selection consistent with that boundary while assembling outside an unbounded transaction.
- Expose generation time and the selection boundary in the manifest.
Implementation constraints
- Choose a method supported by the local schema; do not promise a global snapshot across unrelated stores without a protocol.
Verification to include
- Edit and add notes during a paused assembly and verify the documented inclusion rule.
- Slow artifact upload and verify no long-lived database transaction is retained solely for transfer.
Deliverables
- Selection protocol and concurrent-edit export tests
Rollout and recovery
Version the consistency contract; failed assembly may retry against the same frozen selection or start a clearly new operation.
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.