Skip to content

fix: use published vocabulary in graph writers and dual readers - #71

Merged
scbrown merged 2 commits into
mainfrom
ellie/m5s3-writers-20261113
Nov 14, 2026
Merged

scbrown merged 2 commits into
mainfrom
ellie/m5s3-writers-20261113

Conversation

@scbrown

@scbrown scbrown commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

Graph exports currently derive vocabulary from the instance namespace, and mapped GitHub readers miss the published w3id spellings. This uses the exact published ownership mappings for 14 writer terms, accepts old and new reader spellings, and keeps existing instance identities intact.

Historical recovery retains its actual completed predicate; duplicate identity/completion aliases and partial answers refuse. A vocabulary version in the receiver scope fences bound retained deliveries across the upgrade. Runtime adoption remains held: old unbound attempted rows require explicit disposition, and instance identity policy plus native shape/reader acceptance remain separate prerequisites. This PR grants no runtime activation, drain or replay.

Validation: locked full suite 741 tests plus 48 subtests passed; Ruff passed; HOME guard clean (163 paths and five UID resources). Independent published-crosswalk fixture, lost-original-answer/recovery controls, old/new catalogue routing and malformed/ambiguous response controls pass.

Demo: recording and repeat command, output. Same private builder input at base64e4845 versus candidate; instance-base-derived vocabulary disappears while the firing IRI stays identical. Source-builder evidence only; no graph writes or native deployment acceptance.

Task: aegis-m5s.3. Vocabulary ownership and instance identity gaps are tracked separately; one non-author review follows complete hosted green.

@scbrown
scbrown merged commit 82cef2f into main Nov 14, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant