Enterprise week-2 playbook¶
Continue after the first-week Protégé migration and production readiness pilot criteria. This page assumes week 1 already covered install, First success, and basic validate CI.
Goals¶
- Prove DL / realize / SWRL / DL Query on a representative corpus (not only fixtures).
- Define rollback criteria before wider rollout.
- Keep Protégé for workflows OntoCode still marks as not supported (byte-identical XML, HermiT identity, Protégé-only plugins) — see known limitations and DL Query honesty.
Day plan (suggest ~5 working days)¶
| Day | Focus | Exit when |
|---|---|---|
| 1 | Pin CLI/VSIX to 0.26.2; confirm Versions & channels | Same version in IDE + CI |
| 2 | ontocore classify --profile dl (or auto) on your corpus | Exit codes understood; profile warnings reviewed |
| 3 | ontocore realize + sample check-instance in CI | realize cookbook |
| 4 | SWRL: load a known rule set; classify with materialize; dual-check in Protégé if critical | SWRL examples; no surprise consequents |
| 5 | Review known limitations; write rollback note; DL Query honesty decision | Go / no-go for week 3+ |
CI recipes to add¶
ontocore validate ./ontologies
ontocore classify ./ontologies --profile dl --format json
ontocore realize ./ontologies --profile rl --format json
Optional dual-check: re-run critical unsatisfiable / realization cases in Protégé + HermiT and record deltas.
Rollback criteria (examples)¶
Fail the pilot (or pause IDE-only edits) if any of:
- Unsatisfiable-class false positives vs dual-tool baseline on agreed corpora
- SWRL materialize changes ABox/TBox in ways reviewers cannot explain
- Workspace exceeds limits or CI timeouts become routine
- Authors need Protégé DL Query daily and cannot accept OntoCode’s DL Query honesty limits / HermiT dual-check plan