Separate attachment display names from blob identities
Renaming an attachment currently moves its physical file and breaks another reference. Store display names on references.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data modeling · Storage
Estimated field mix
- Storage systems60%
- Database 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
Fictional archive Moss deduplicates generated attachments across documents within each organization. Use local files and transactional metadata stubs.
Setup prerequisites
- Generate duplicate and unique local byte fixtures.
- Create synthetic document references across two organizations.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Rename changes only reference metadata
- Blob identity stays stable
- Other references keep their names
Implementation constraints
- Content identity cannot depend on a user-facing filename.
Verification to include
- Rename shared attachment
- Fail metadata write and inspect file identity
Deliverables
- Reference schema and rename cases
Rollout and recovery
Disable rename if it touches physical blobs.
Value of the work
For the engineer: Practice reclamation races and explicit data-lifecycle guarantees.
For the team: Inspect whether storage cleanup avoids broken references and hidden retention.
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.