Skip to content

Add open question on contractual data-use restrictions and merge scope #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RobGrafrath merged 1 commit into from
Sep 2, 2026
Merged

Add open question on contractual data-use restrictions and merge scope #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions OPEN-QUESTIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,14 @@ Version targets indicate when the item is expected to ship, not when the decisio
**From experience:** What do consumers and clients most often call about that a portal should have answered, and what has stopped your company from giving them one?
**Target:** HiveAR v2. Issue: #13.

### Contractual data-use restrictions and merge scope

**Technical:** Client-level restrictions on data co-mingling applied to entity matching and the golden record. Provenance becomes a rich record carrying not just where a value came from but how it may be used. Merge scope is constrained by client policy: a restricted client's consumer records resolve to an isolated canonical record that neither contributes values to nor draws values from other clients' records, while merging within that client's own records continues. Extends [HIVE-0002](decisions/hivear/HIVE-0002-entity-matching-golden-record-and-locale-aware-identity-resolution.md) and [HIVE-0003](decisions/hivear/HIVE-0003-demographic-history-golden-record-and-contact-intelligence.md).

**From experience:** Which of your clients restrict how their account data may be used, what exactly do the restrictions forbid (discussing other accounts on a call, combined letters, shared contact data), and how does your shop enforce those restrictions today?

**Target:** HiveAR v2. Issue: #20.

## Wax (framework)

### Custom action type sandboxing
Expand Down
Loading