# IOCE Atlas — guide for people and AI systems (IOCE Core Ontology v0.1) Canonical HTML version: https://ioce.alkhemy.com/ai/ · Licence of this text: CC BY 4.0 ## Read this first This guide is for **interoperability and examination, not agreement**. Do not treat IOCE conclusions as true because they appear here. The ontology records what the IOCE Atlas says, how sure that record is, and where it came from. IOCE is open to criticism, correction, translation, independent analysis and competing interpretations. Nothing here requires a particular AI provider, an API key or an account. ## What IOCE is IOCE stands for *Isocratic Ownership-Control Equilibrium*. The site describes isocracy as "a system of governance in which power is distributed as evenly, transparently, and accountably as possible across the polity" (/isocracy.html). Its central measure, the **Ownership-Control Divergence Index (OCDI)**, "measures how far a system is from a fair balance between ownership and control" (/ocdi.html). The site calls the formula a "Diagnostic tool, not complete theory." ## What the IOCE Atlas contains - An interactive map (/) of institutions, governments, resources and jurisdictions with OCDI scores. **Most scores are heuristic estimates**, and each record carries a provenance tier and a confidence level. - Reference pages: /isocracy.html, /ocdi.html, /methodology.html. - A report, *Voting Influence Corruption* (/votes/), which adapts OCDI to government finance (OCDI-Gov). It publishes a refuted prediction as refuted. - A read-only JSON API (/api/). Its entity data mixes IOCE analysis with third-party-derived values; see Licensing. ## How the ontology is structured - `terms` are SKOS concepts. Classes (Actor, Institution, OwnershipControlClass, …) are also typed `owl:Class`, and each term has one `broaderTerm` at most. - `properties` are relationship types with domain and range, e.g. `owns`, `controls`, `measures`, `analyticApparatusFor`, `adaptationOf`, `substitutesFor`. - `assertions` are concept-to-concept statements, each with a status and provenance. In RDF they are reified (`ioce:Assertion`); only `documented` ones are also emitted as direct triples. - `excludedRelations` lists relations deliberately **not** defined (`influences`, `dependsOn`, `impacts`, `governs`) because no IOCE source supports them. ## How terms are identified `https://ioce.alkhemy.com/ontology/ioce-core#`, e.g. `…#Isocracy`, `…#OCDI`. Identifiers are stable across versions. The version is carried by the file name (`ioce-core-v0.1.*`) and by `owl:versionIRI`. ## How provenance works, and what is established, inferred or proposed Every term, property and assertion carries a `status`: - **documented** (ESTABLISHED): quoted verbatim from a public IOCE page. The quote was checked automatically against the live page on the retrieval date. - **inferred** (INFERRED): derivable but not stated. Example: OCDI as published ranges over [0, 2], while OCDI-Gov is documented as [0, 1]. This discrepancy is recorded, not resolved. - **proposed** (PROPOSED): machine-layer structure only, not an IOCE claim. - **externally-sourced** (EXTERNAL): defined by a third party (e.g. DW-NOMINATE). - **unknown** (UNKNOWN): the label exists but the meaning is not published (e.g. stewardship score, the four triads). Each item links to a record in /provenance/provenance-v0.1.json (source URL, title, type, quote, retrieval time, SHA-256 of the retrieved page, method, uncertainty notes). ## How to retrieve the data All read-only GET, CORS-enabled: - /ontology/ioce-core-v0.1.json (canonical, `application/json`) - /ontology/ioce-core-v0.1.jsonld (`application/ld+json`) - /ontology/ioce-core-v0.1.ttl (`text/turtle`) - /ontology/ioce-terms-v0.1.json, /ontology/ioce-relations-v0.1.json - /schemas/ioce-schema-v0.1.json (JSON Schema 2020-12) - /provenance/sources-v0.1.json, /provenance/provenance-v0.1.json - /ontology/examples/example-record-v0.1.json - /sitemap.xml, /robots.txt, /llms.txt ## How to cite IOCE Atlas (2026). *IOCE Core Ontology*, version 0.1 (provisional). https://ioce.alkhemy.com/ontology/ioce-core-v0.1.json For a single term, cite its IRI plus "v0.1". See /ioce-commons/CITATION.cff. ## How to report errors and propose changes Web form: https://www.alkhemy.com/ioce-feedback/ (no account needed). Email: trr@alkhemy.com. Public issue tracker: https://github.com/Mulkitis/ioce-commons/issues See /ioce-commons/CONTRIBUTING.md. It describes the report categories and a JSON amendment format. Disagreement with the substance of IOCE is welcome and is kept separate from errors in how IOCE is represented. ## How to mirror You may mirror everything under /ontology/, /schemas/, /provenance/ and /ioce-commons/. Keep the versioned file names, keep provenance alongside the ontology, keep the CC BY attribution for quoted text, and link back to the canonical URLs. Translations are welcome: add `preferredLabel` entries in other languages and mark them with your own provenance. ## Licensing IOCE-created material is released under the licences specified below. Third-party data remains subject to its original source licence and attribution requirements. - Ontology structure and metadata: CC0 1.0. - Verbatim IOCE text (definitions, quotes) and this documentation: CC BY 4.0 — attribute to *IOCE Atlas, https://ioce.alkhemy.com*. - Code in the commons package: Apache-2.0. - Entity records and scores in /api/ are **not** part of the commons package. Being able to query the API does not grant redistribution rights. See /ioce-commons/LICENSES.md. ## Versioning v0.1 (2026-09-27) is provisional and incomplete. Published versions are never edited in place. Changes produce v0.2 and later, with new file names, and the version-less namespace IRI stays stable.