Define contact field ownership between the app and CRM
Both systems overwrite account names and communication preferences.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data ownership
Estimated field mix
- Integrations50%
- System design30%
- Privacy engineering20%
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 account team sees overwritten edits, duplicate contacts, and stale opt-out preferences after synchronization retries.
Setup prerequisites
- Create a local CRM double and synthetic contact records for two organizations; no real personal data or CRM credentials.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Assign an authority rule per synchronized field.
- Separate display fields from consent fields.
- Define unresolved conflicts explicitly.
Implementation constraints
- Never infer marketing consent from unrelated activity.
Verification to include
- Resolve an app-owned field change.
- Keep conflicting consent records unresolved.
Deliverables
- Field ownership matrix.
Rollout and recovery
Review the matrix before enabling writes.
Value of the work
For the engineer: Practice sync cursors, conflict policies, privacy boundaries, and replay.
For the team: Provide predictable customer-data synchronization with inspectable conflicts.
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.