🕸️ Architecture Knowledge Graph

Your codebase as a queryable knowledge graph

← Back to GREEN

Nodes…

Edges…

Relationship Types…

Last Generated…

depends_oncontainsownscauses_driftpart_of_cycletagged_as

capabilityriskcycleteamfile

Use as API

Compatible with Cytoscape.js, D3.js, and Neo4j (GraphML) export format

# Get full knowledge graph
curl "https://your-prism/api/green/knowledge-graph"

# Get all drifted capabilities
curl -X POST "https://your-prism/api/green/knowledge-graph" \
  -H "Content-Type: application/json" \
  -d '{"pattern": "all_drifted"}'

# Traverse from a node
curl -X POST "https://your-prism/api/green/knowledge-graph" \
  -H "Content-Type: application/json" \
  -d '{"traverse":{"from":"cap:auth","direction":"outbound","depth":2}}'

# Cytoscape.js format
curl "https://your-prism/api/green/knowledge-graph?format=cytoscape"

# GraphML export (Neo4j-compatible)
curl "https://your-prism/api/green/knowledge-graph?format=graphml"

GET/api/green/knowledge-graph

Full graph (JSON / GraphML / Cytoscape)

POST/api/green/knowledge-graph

Query by filter / traverse / pattern

GET/api/green/knowledge-graph/mcp

Additional MCP tool definitions (graph_query, graph_traverse, graph_neighbors)

POST/api/green/knowledge-graph/mcp

Execute MCP graph tools via JSON-RPC

🕸️

Google's Knowledge Graph powers Search.

Your architecture knowledge graph powers PRISM. Same concept, your codebase. Capabilities are entities. Dependencies are relationships. Drift and cycles are first-class graph properties — queryable, traversable, and exportable to any tool that speaks Cytoscape.js, D3.js, or Neo4j's GraphML format.