Repository navigation
dir-core: identity rules, witness evidence, ruler fold (D-IDENTITY-GUID-HOT-0) - #326
Merged
Merged
Conversation
Hybrid identity correspondence across AD, Entra and Exchange Online, as numbers, without merging nodes. - identity: IdentityRule (declaration) + CompiledRule (numeric slots). Encodings MsGuidBytes16 / Base64MsGuidBytes16 / Labeled / GuidText, strict (renders back or refused), absent / malformed / nil kept apart. Rules: ConsistencyGuid -> ImmutableId, objectGUID -> ImmutableId (separate profile, no fallback), backsync -> Entra id, Entra id -> EXO ExternalDirectoryObjectId. - edge: EdgeEvidence codes 2-4; code 1 keeps its objectGUID meaning. - schema: SchemaFamily::ExchangeOnline = 3 (additive). - correspond: Lanes (boundary decode, once), sort-merge join fold (puts unaligned observations onto the ruler, cold), and fold_aligned: slot i is the same user in every column, so each witness is a position-wise compare into bit planes. Ambiguous or contested counterparts never reach the ruler. - ogar-az sync_edges documented as the objectGUID profile only. - dir-sim SourceAnchor::from_immutable_id reuses the dir-core codec. Tests: F1-F14 through the real ogar-ad / ogar-az encoders, plus a 3,000-world randomized comparison with an independent reference that also checks the ruler fold against the join slot by slot. Bench (1,048,576 slots, release, one thread, Xeon 2.1 GHz): ruler fold 8.2 ms median, 0 allocations; join fold 200 ms; Guid128 equality 1.2 ms; HashMap lookup baseline 95 ms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G22yT6htkcdyXsihxxXdrg
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (11)
✨ Finishing Touches📝 Generate docstrings
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Comment |
AdaWorldAPI
marked this pull request as ready for review
October 9, 2026 20:42
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
Hybrid identity correspondence across AD, Entra and Exchange Online. Ids are compared as
Guid128numbers, and the three directories are never merged into one node.identity: a declaredIdentityRulecompiles to aCompiledRulethat reads numeric slots only.MsGuidBytes16,Base64MsGuidBytes16,Labeled("User_{0}"),GuidText.mS-DS-ConsistencyGuid → onPremisesImmutableId,objectGUID → onPremisesImmutableId, backsync→ id, andid → ExternalDirectoryObjectId.objectGUIDrule is a separate profile. It is never a fallback for the ConsistencyGuid rule.edge: newEdgeEvidencecodes 2–4, one per witness. Code 1 keeps its existingobjectGUIDmeaning.schema:SchemaFamily::ExchangeOnline = 3(additive). The 512-byte record and the 64-byte edge layouts are unchanged.correspond: three stages.fold_alignedis the hot path. Slot i is the same user in every column, so each witness is a position-wise compare written into bit planes.ogar_az::sync_edgesis unchanged; its docs now say it covers theobjectGUIDprofile only.SourceAnchor::from_immutable_idnow reuses the dir-core codec. No behaviour change.The defect
sync_edgescompares the decoded immutable id against ADobjectGUID. When the source anchor ismS-DS-ConsistencyGuidand it differs fromobjectGUID, no correspondence is found (F1).Tests
ogar-ad/ogar-azencoders.Sabotage (each mutation applied alone, then reverted)
User_/Group_label acceptedBenchmark
cargo run --release -p ogar-dir-core --example identity_fold_bench, run on 1,048,576 slots (16 × 65,536), single thread, Xeon 2.1 GHz:Guid128equality onlyHashMaplookupNot covered
There is no Exchange Online ingest crate. EXO lanes are built from
DirRecords of family 3.🤖 Generated with Claude Code
https://claude.ai/code/session_01G22yT6htkcdyXsihxxXdrg