Skip to content

docs(ontology): annotate :AnnexIII_List as mereological extension scaffold#39

Open
Amosk21 wants to merge 2 commits into
mainfrom
docs/annexiii-list-scaffold
Open

docs(ontology): annotate :AnnexIII_List as mereological extension scaffold#39
Amosk21 wants to merge 2 commits into
mainfrom
docs/annexiii-list-scaffold

Conversation

@Amosk21
Copy link
Copy Markdown
Owner

@Amosk21 Amosk21 commented May 11, 2026

Fixes

Documentation alignment: adds rdfs:comment to :AnnexIII_List declaring it as an open-world extension point per CLAUDE.md Invariant 8.

Supersedes #22 (closed due to merge conflict with the :AnnexIII_Condition_Q1:AnnexIII_Condition_1a rename in subsequent PRs).

Axiom paths

  • 03_TECHNICAL_CORE/ontology/ARCO_instances_sentinel.ttl:19-23:AnnexIII_List gains one rdfs:comment line

Schema

No schema change. No new ontological commitment. Pure documentation alignment with the existing CLAUDE.md invariant.

Tests

  • python 03_TECHNICAL_CORE/scripts/run_pipeline.py → ALL CHECKS PASSED (exit 0)
  • test_gate_removal.py → ALL GATE-REMOVAL TESTS PASSED
  • test_scenarios.py → ALL SCENARIO TESTS PASSED
  • Classification unchanged: AnnexIII1aApplicableSystem entailed, HighRiskSystem latent-flag present

Deferred

None.

Revert

git revert <commit> — single-line addition, clean revert.

…ffold

Adds rdfs:comment to :AnnexIII_List declaring it as an open-world extension
point per CLAUDE.md Invariant 8 (mereological container for modeled
regulatory conditions; new categories add via bfo:0000051; peer regulation
lists follow same pattern). Documentation alignment only; no semantic change.

Supersedes #22 (which conflicted with the :AnnexIII_Condition_Q1 to
:AnnexIII_Condition_1a rename in subsequent PRs).

Backtest: pipeline ALL CHECKS PASSED exit 0; classification unchanged
(AnnexIII1aApplicableSystem entailed, HighRiskSystem latent-flag present);
test_gate_removal.py and test_scenarios.py all pass.
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

…only

Drops the "Peer regulation lists (e.g. GDPR_Article22_List)" example. Grep
across the repo shows GDPR_Article22_List has no class declaration; the only
mention is at docs/ARCO_explained.md:632 explicitly labeled "hypothetical".
Adequatism: describe what is in scope (the bfo:0000051 has_part pattern,
exercised today for 1(a) and 5(b)), not forward-looking peer regulations.

Backtest: pipeline ALL CHECKS PASSED exit 0; classification unchanged.
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

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