From 9c5992e04969dfd979fa45abc1e5ea8f80ea88d6 Mon Sep 17 00:00:00 2001 From: Rob Grafrath Date: Wed, 2 Sep 2026 15:38:22 -0500 Subject: [PATCH] Add open question on contractual data-use restrictions and merge scope Signed-off-by: Rob Grafrath --- OPEN-QUESTIONS.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/OPEN-QUESTIONS.md b/OPEN-QUESTIONS.md index d6afc60..ee5085e 100644 --- a/OPEN-QUESTIONS.md +++ b/OPEN-QUESTIONS.md @@ -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