Compatibility Lab
Put a pack in a cabinet and see what follows.
A specification sheet can tell you two packs differ. An ontology can tell you that a particular pairing is impossible — and show the steps that make it so.
Pick a pack and a device, then run the test. The answer is derived from the ontology’s own axioms, not from a table of known pairs.
What the test is really doing
Not a lookup table
No pairing is listed anywhere as allowed or forbidden. Each verdict is derived by following what a device’s class says it accepts, and what that class requires of a battery.
Contradiction, not absence
An incompatible pairing does not return an empty answer. It makes the knowledge base inconsistent — a reasoner reports that the configuration cannot hold at all.
Silence is not denial
Where a device’s chemistry was never recorded, the answer is “undetermined”. Under the open-world assumption, what is not said is not thereby false.
The published test scenario
Test scenario: a lithium iron phosphate pack from one ecosystem is inserted into a handling device of the other ecosystem that accepts lithium-ion packs only. Held in its own file, because loading it together with the terminology and population is expected to make the knowledge base inconsistent — that is what the file is for.