Skip to content

Signatures reach across packs, and direction is judged by range too - #233

Merged
WaylandYang merged 3 commits into
devfrom
fix/cross-pack-domains-and-range-direction
Sep 2, 2026
Merged

Signatures reach across packs, and direction is judged by range too#233
WaylandYang merged 3 commits into
devfrom
fix/cross-pack-domains-and-range-direction

Conversation

@WaylandYang

Copy link
Copy Markdown
Contributor

Closes #222.

Three things, all found through the same reversed fact (Project Aurora head_of Li Ting):

  • Pack import now resolves domain / range IRIs against classes already in the base, and install_packs runs a second relink_domains_ranges pass once every pack is in, so org:headOf gets its foaf:Agent domain no matter which pack came first.
  • judge_direction looks at the range as well as the domain: Keep only when neither declared end is violated, Swap when the reverse reading satisfies both, Neither otherwise. Untyped entities do not count as violating the range.
  • After extracting a document, the facts it touched go through signature_breaks and any violation is queued under Review > Axioms immediately, instead of waiting for someone to press Run check.

🤖 Generated with Claude Code

Closes #222

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@WaylandYang
WaylandYang force-pushed the fix/cross-pack-domains-and-range-direction branch from b3de7fb to 4283831 Compare September 2, 2026 21:43
@WaylandYang
WaylandYang merged commit 848e4ab into dev Sep 2, 2026
3 checks passed
@WaylandYang
WaylandYang deleted the fix/cross-pack-domains-and-range-direction branch September 2, 2026 21:56
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.

Cross-pack domain and range references are dropped at import, so direction is never judged for them

1 participant