442 auto commit inverse smartlinks during relationship persistence commit pass 2#445
Open
owleyeview wants to merge 6 commits intomainfrom
Conversation
…er_ref_resolver.rs
7 tasks
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.
Auto-commit inverse SmartLinks during relationship persistence (Pass 2)
Summary
commit_functions::commit()Pass 2 to automatically resolve and persist inverseSmartLinks whenever a declared forward relationship is committed, enforcing the MAP schema contract that all declared relationships are bidirectional and materializedresolve_inverse_relationship_name()which traverses the type graph (DescribedBy → InstanceRelationships → match TypeName → HasInverse → inverse TypeName) to derive the inverse relationship name from staged or persisted schemacommit_inverse_smartlinks()which writes reversed-endpoint SmartLinks for each local target, skipping external targetsAssertRelatedHolonstest step as the preferred replacement forQueryRelationshipsbody assertions, comparing related-member sets by sorted identity (key + HolonId)inverse_smartlink_fixtureend-to-end test proving bidirectional traversal after commit with staged schemaTest plan
inverse_smartlink_testvalidates forward (Book → AuthoredBy → [Person1, Person2]) and inverse (Person1 → Authors → [Book], Person2 → Authors → [Book]) traversal after commitnpm run sweetestsuite passes — no regressions insimple_add_remove_related_holons_fixture(undescribed holons) orloader_client_fixture(bootstrap schema)Out of scope
Closes #442