Repository navigation
feat(artifacts): reconcile composite group identities - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Allow
keyed_integer_sum_equalsto identify a group with two to four ordered string columns while preserving the existing single-string key behavior. An organization-local order ID can now be reconciled as[tenant_id, order_id], so a total-preserving transfer between organizations is rejected instead of passing under a shared order ID.Composite components use unambiguous byte-length framing, retain exact string semantics, and each count toward the existing 100,000-cell budget. Reports expose declared column names and aggregate findings without raw keys or values. Invalid, unsafe, or capacity-limited observations remain
unknown.Source version is 0.1.6. GitHub 0.1.4 and npm 0.1.0 remain the existing published artifacts; no package publication is part of this PR.
Safety boundary
Verification
Documentation