The readme seems to be written for enterprise project managers. Does anyone know what philosophy or academic ontology work this ties to, if any? I’m having trouble understanding the specifics, I’ll be honest…
In software, an ontology is just a machine-readable definition of the entities in a system - their names, properties, relationships etc. This tool analyzes a system and produces such a definition for agents to use.
Imagine if you will, 10 groups inside a broader org. Each of those groups have teams that work on different stuff, but at the org level and cross team level managers and leadership still need to make sense of it all and if you ever want to connect the dots across work you need a common language.
Now multiply that problem across a large enterprise if you want a company brain or any of the context to be trustworthy for usage at scale or for high accuracy and trust work.
This is a a tooling solution for the schema and government layer that enables that so you can have an empowered human say "what team X calls Foo, and what team Y call Bar should map to our approved definition for Baz and here is how we validate their data against that shared classification."