Repository navigation
fix(pendant): preserve public policy and stable entity names - #59
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.
The release query omitted the public publication-policy catalogue and retained private entity names, preventing a receiver from safely resharing the pendant. Carry the reviewed public catalogue, publish stable w3id entity names, and retain only verified links to each entity’s exact former name. Private policy remains excluded; arbitrary identity assertions still fail.
Synthetic query controls cover the public/private boundary, cross-repository names, literal and class preservation, and rejected former-name links. Repo-owned publication and knowledge controls are included. Exact-source native qualification passed at 7642248: 19,691 accepted triples, README positive control, outward receiver roundtrip, missing/altered catalogue refusals, blocked-byte refusal, and incomplete-rule SHACL refusal. HOME guard clean. This is private source qualification, not production delivery. No release, tag, upload, or runtime admission is part of this change.
Demo transcript: the same isolated RDF dataset contains one README document, four public policy rules and a private-rule negative control. Base 36c244d6 versus head 7642248d:
The fixture suite is repeatable with
python3 scripts/test-repository-share-query.py; its seven controls cover that boundary and exact former-name refusal. This is a measured synthetic-query transcript, not installed-service output. The terminal replay is retained with private qualification evidence; no public embed/playback is claimed. Exact native proof and public release acceptance remain separate.