docs: README cleanup follow-up to PR #24 (numbers, duplicates, CI triggers)#25
Merged
docs: README cleanup follow-up to PR #24 (numbers, duplicates, CI triggers)#25
Conversation
README review pass after the IAO + RO promotion: 1. Update the headline framing (line 9) to acknowledge that BFO, RO, and IAO are now full upstream imports rather than just calling out BFO + CCO. 2. Update the certificate sample's "ENTAILED TRIPLES ADDED" from the previous stub-state value (+3473) to the current full-imports value (+47888) so the advertised proof matches what the pipeline actually emits. 3. Update the "Getting started" section's asserted-vs-post-reasoning numbers from the stub-state baseline (1434 -> 4907) to the current values (17266 -> 65154) and explicitly note that this is over the full BFO + RO + IAO + ARCO union. ROBOT validation workflow trigger tightening: - Drop push triggers on tooling/** and experiment/**. With the full-import HermiT step taking ~30-40 minutes, running it on every WIP commit is noisy without adding signal. Independent DL verification still runs on every push to main and every PR targeting main, which is exactly what the README has always promised. Manual workflow_dispatch is retained. No ontology, gate, SHACL, SPARQL, or pipeline-logic change. Documentation accuracy and CI ergonomics only. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The "Why full upstream imports" subsection now answers two follow-up questions a reader is likely to ask after seeing the +47888 entailed-triples number: 1. "Where do all those derived triples come from?" The overwhelming majority is OWL-RL closure over upstream axiomatization (BFO upper-level subclass propagation, RO property chains and inverses, IAO ICE hierarchy), not ARCO-specific reasoning. Slim MIREOT modules would shrink the post-reasoning graph by roughly an order of magnitude without changing the classification outcome. 2. "What does this mean for adding a new Annex III category or peer regulation?" Full imports leave whatever BFO/RO/IAO terms the new category needs already in scope; the only engineering work is the new gate axioms and ARCO-side classes. MIREOT modules would add a per- addition module-rebuild step that tends to rot if forgotten. Documentation only; no code or ontology change. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Three sections were restating content already covered in the hero paragraphs and TL;DR. Removed: - "The problem ARCO solves": repeated the hero almost verbatim (same "moves the risk decision upstream" framing). - "Beyond a single regulation": repeated the TL;DR and "How it works" generalization claim a third time. - Blockquote "The core value: ...": rephrased TL;DR bullet 2 with a flowery "ontologically disciplined structure" tag. Also tightened "How it works" step 4 by dropping the "downstream documentation layer" phrase in favor of plain "audit queries." No technical content cut. The unique sections (proof certificate, how it works, structural-vs-behavioral framing, foundational ontology versions and full-imports rationale, getting-started) are unchanged. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
This was referenced Apr 30, 2026
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
1 participant
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.
Three stranded doc commits from PR #24's branch that didn't land in the merge window. Shipping them as a follow-up so
mainreflects the post-IAO-and-RO-promotion state accurately.What this fixes on main
ENTAILED TRIPLES ADDED: +3473in the certificate sample ->+47888(current full-imports value)1434 asserted -> 4907 post-reasoning->17266 -> 65154(current numbers)BFO/RO/IAO-aligned, CCO-informedinstead ofBFO-aligned, CCO-informed(matches the new full-imports state)The problem ARCO solves,Beyond a single regulation,The core value:blockquote)tooling/**,experiment/**push triggers — README has always promised this; reality now matches)What does NOT change
No ontology, gate, SHACL, SPARQL, instance data, or pipeline-logic change. Documentation accuracy + CI ergonomics only.
Verification
python 03_TECHNICAL_CORE/scripts/run_pipeline.py: PASS (already verified on PR experiment: promote IAO 2026-03-30 and RO 2025-12-17 from stubs to full upstream imports #24's combined branch CI run 25144006569).🤖 Generated with Claude Code