Add composite uniqueness for tenant-owned relationship targets
Globally unique row IDs do not by themselves let a foreign key enforce that case and project belong to the same organization.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Composite keys · Migrations
Estimated field mix
- Database engineering80%
- Security20%
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 case-management application filters most requests correctly, but imports and background commands can connect a case to another organization's project or assignee.
Setup prerequisites
- Create two synthetic organizations with overlapping display names.
- Use repository-level authorization and migration-backed constraints.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Add the composite target keys needed for tenant-bound references.
- Preserve existing globally unique identities.
- Document index duplication and selected constraint names.
Implementation constraints
- Inspect actual migration SQL and query patterns.
Verification to include
- Create identical display names in different organizations.
- Attempt a duplicate target identity within the same composite key and verify rejection.
Deliverables
- Composite-key migration
Rollout and recovery
Apply additive keys first; remove only demonstrably redundant indexes after usage review.
Value of the work
For the engineer: Practice tenant-aware keys, foreign keys and direct-write denial tests.
For the team: Review defense in depth for data isolation across ordinary and privileged writers.
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.