List exportable member fields before serializing database rows
A prototype exports complete ORM objects, including internal moderation flags and provider tokens.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data minimization · Serialization
Estimated field mix
- Privacy engineering80%
- Backend20%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Create an explicit allowlist for profile, private-note and settings fields.
- Exclude credentials, internal operational fields and unrelated-member data.
- Version the export schema and document omitted field categories.
Implementation constraints
- Build export DTOs independently of database model serialization.
Verification to include
- Export a synthetic row containing token-like and internal fields and verify they are absent.
- Add an unknown database column and confirm it does not enter the artifact automatically.
Deliverables
- Export field contract and allowlist tests
Rollout and recovery
Review the field contract before enabling generation; new fields require an explicit schema change.
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.