Skip to content

Keep unmatched research rows in an operational ledger

Preserve left-only, right-only and invalid-key states instead of silently losing rows during joins.

Guides

Keep unmatched research rows in an operational ledger — what should the operator record?

An inner join can hide useful evidence simply because one side lacks a matching key. That may be intentional, but the omissions still need explanation. Keep an unmatched ledger alongside the derived table so recipients can distinguish a known scope difference from a key error or an unresolved access limitation.

Practical operations check
Preserve left-only, right-only and invalid-key states instead of silently losing rows during joins.
Use left-only, right-only, invalid-left-key and invalid-right-key with input_revision references, avoiding one generic missing label. An invalid-left-key state differs from left-only: the former could not be compared safely, while the latter was validly keyed but found no eligible match.
Attach unresolved categories and owners to the joined revision, making intentional exclusions explicit instead of allowing an inner join to erase operational uncertainty. If intentional exclusion is approved, keep the reason and scope in the manifest so a smaller joined table does not appear to be the full returned evidence set.
01 / Guides

Define unmatched categories

Use left-only, right-only, invalid-left-key and invalid-right-key with input_revision references, avoiding one generic missing label. An invalid-left-key state differs from left-only: the former could not be compared safely, while the latter was validly keyed but found no eligible match.

02 / Guides

Preserve minimal references

Keep qualified keys or permitted operational aliases and the reason for exclusion without copying unnecessary source content into the exception ledger. A ledger can use row aliases and input manifest references when actual keys would expose withheld identities to reviewers who only need to triage the operation.

03 / Guides

Test outer coverage

Use fixtures with one match and separate unmatched rows on each side to confirm all input membership remains explainable. Verify that an inner-join view plus the unmatched ledger explains all eligible input keys, without counting invalid-key rows as confidently unmatched objects in the other source.

04 / Guides

Investigate supported causes

Check key formatting, declared scope and current visibility before concluding that a record disappeared or another input was incomplete. A key formatting bug may be locally fixable, while an access-related omission must remain governed by current policy; the operational categories should lead to different next actions.

05 / Guides

Publish the ledger with output

Attach unresolved categories and owners to the joined revision, making intentional exclusions explicit instead of allowing an inner join to erase operational uncertainty. If intentional exclusion is approved, keep the reason and scope in the manifest so a smaller joined table does not appear to be the full returned evidence set.

Keep the boundaries clear.

  • Preserve left-only, right-only and invalid-key states instead of silently losing rows during joins.
  • Operational record: Define unmatched categories. 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.

Know what social media shows about you.
Start with a question.

Get started
montage