Prevent cross-context false matches in an evidence join — what should the operator record?
Even a context-qualified identifier may be unsafe if one table holds accounts and another holds posts under a similar field name. Inspect object type and namespace on both sides. A join should connect the intended evidence objects, not merely values that happen to occupy columns called id.
Require compatible source context and object type before accepting an identifier match.
Record source_context, object_type and native_id definition for each input, preserving unknown meanings as unresolved schema questions. An account id and a post id can both be strings named id without sharing identity semantics; the field label alone provides no reliable join contract.
State what the join establishes and what it does not, retaining unresolved references without inferring a private or cross-platform identity. The final output can describe a documented source relationship while explicitly withholding unsupported claims about ownership, identity continuity or access to nonpublic information.Inventory key meaning
Record source_context, object_type and native_id definition for each input, preserving unknown meanings as unresolved schema questions. An account id and a post id can both be strings named id without sharing identity semantics; the field label alone provides no reliable join contract.
Require compatible namespaces
Accept a match only when the declared object types and source contexts agree or an authorized explicit crosswalk supports the relationship. An explicit parent-account field can establish a supported post-to-account relationship, but it still does not make the post and account the same evidence object.
Test misleading equality
Use fixture rows sharing the same string across account and post types and confirm they remain distinct despite the equal text. Keep these fixtures artificial and clearly labeled; their role is to test namespace handling, not demonstrate an observed cross-context collision in the real research evidence.
Review crosswalk exceptions
Where a legitimate relationship uses different object types, preserve its explicit relationship field rather than relabeling both objects as identical. The crosswalk should name relationship_type and its actual evidence basis, preserving uncertainty rather than turning a plausible association into a confirmed private identity link.
Publish the identity boundary
State what the join establishes and what it does not, retaining unresolved references without inferring a private or cross-platform identity. The final output can describe a documented source relationship while explicitly withholding unsupported claims about ownership, identity continuity or access to nonpublic information.
Keep the boundaries clear.
- Require compatible source context and object type before accepting an identifier match.
- Operational record: Inventory key meaning. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.