Context
The current make ontology target runs a Python-only build. ROBOT-based validation (ELK reasoning + OBO hygiene) is gated behind the optional make ontology-robot target, which requires Java + obo-robot. The Stage 0 banner prints Validation: Python build (run make ontology-robot for ELK + report).
For the JAXA workshop talk (June 12 2026), we want ROBOT to be part of the canonical build path — not an opt-in — so the integration story holds: the assembled ontology is audited at build time by ROBOT/ELK against the upstream vendored imports.
Current state
make ontology → Python-only build (default)
make ontology-robot → optional ROBOT merge + ELK reason + report
- Stage 0 banner reflects Python build by default
- No CI step runs ROBOT
Proposed change
- Make ROBOT the default validator inside
make ontology when Java + obo-robot are available on the path
- Decide and document failure mode when the toolchain is missing (fail-fast vs. loud-warn-and-fallback)
- Update Stage 0 banner to print the ROBOT result on default builds
- Wire ROBOT into CI on every push and PR
Acceptance criteria
Context
The current
make ontologytarget runs a Python-only build. ROBOT-based validation (ELK reasoning + OBO hygiene) is gated behind the optionalmake ontology-robottarget, which requires Java + obo-robot. The Stage 0 banner printsValidation: Python build (run make ontology-robot for ELK + report).For the JAXA workshop talk (June 12 2026), we want ROBOT to be part of the canonical build path — not an opt-in — so the integration story holds: the assembled ontology is audited at build time by ROBOT/ELK against the upstream vendored imports.
Current state
make ontology→ Python-only build (default)make ontology-robot→ optional ROBOT merge + ELK reason + reportProposed change
make ontologywhen Java + obo-robot are available on the pathAcceptance criteria
make ontologyruns ROBOT/ELK reasoning + OBO report when toolchain presentmainand on PRs