The graph database is the relationship-analysis access pattern. The project generates no Cypher of its own. just fetch-cypher, or ./ai graph cypher --export, downloads the Cypher export that ai-atlas-nexus publishes at the release tag of the installed package to graph/cypher/ai-risk-ontology.cypher, which is not committed. A person imports that file into a Neo4j container (podman or docker) with cypher-shell (:source /examples/ai-risk-ontology.cypher). docs/neo4j.md gives the steps. The Neo4j Browser on port 7474 then shows the schema (CALL db.schema.visualization()) and answers cross-taxonomy relationship queries.

The artefact is built upstream from the packaged ontology, so the graph shows the open frameworks and never the files under byo/data/. --byod on the Cypher export is refused with a 400 rather than ignored. docs/neo4j.md also lists defects in the upstream artefact, such as edge statements that match no node, which are upstream’s to fix.

This service is short-lived: it is rebuilt from the knowledge-graph export dataset rather than being a system of record.