Chrome DevTools for ontologies
The Universal Ontology Explorer
See your ontology. Trace authority. Understand relationships. GraphOntology makes semantic graphs explorable across Web4, JSOntology, CanonLink, Valgraf, MissionStack, and future AI systems.
Start with a guided graph, inspect the relationship evidence, export a report, then copy the host contract into another app.
focus
Edges
Relationships are modeled as inspectable semantic evidence.
surface
Graph
Entities, paths, context, provenance, and confidence.
mode
Public
Synthetic demos and generalized infrastructure patterns.
core thesis
Intelligence does not live only in data. It lives in relationships.
Topology changes retrieval
Reasoning needs traces
product workflow
A reusable inspection surface, not a one-off demo page.
Explore
Open the Cytoscape ontology surface with modes, filters, focus trail, inspector, and shareable URL state.
Adapt
Paste JSON, JSON-LD, Cytoscape JSON, or CSV and validate the canonical graph contract before embedding.
Report
Generate Markdown, HTML, and structured JSON reports with diagnostics, authority traces, and validation notes.
Embed
Use the package surface across Web4, JSOntology, CanonLink, Valgraf, MissionStack, and future apps.
v0.1 launch path
Three demos that explain the product in the first minute.
demo 1
Web4 authority and provenance
Show how authority claims, registries, schemas, missions, value flows, and evidence ledgers sit in one inspectable semantic infrastructure graph.
A visitor can trace who asserts authority, what delegates it, and which evidence supports the claim.
inspect: Authority Registry / Canon Paper / Evidence Ledger
demo 2
CanonLink agreement graph
Show that parties, agreements, proofs, and provenance relationships can render through the same app-neutral explorer shell.
A visitor can inspect an agreement relationship without any CanonLink-specific UI living inside the core package.
inspect: Party / Agreement / Proof
demo 3
Valgraf and Incentivis value graph
Show how missions, incentive policy, participants, evidence, rewards, contributions, and value allocation become inspectable graph structure.
A visitor can see how value and evidence move through a mission system instead of reading an opaque score.
inspect: Mission / Incentive Policy / Completion Evidence / Reward
verified deep links
Shareable ontology states should reopen exactly where they point.
CanonLink adapter example
Adapter fixture selected without colliding with the canonical CanonLink sample graph.
/examples?graph=adapter-canonlink
Incentivis sample example
Canonical value and incentive graph selected from the examples catalog.
/examples?graph=incentivis
Canon relationship filtered example
Examples route recreates explorer mode plus node and edge filters without requiring a graph key.
/examples?mode=canon-relationship-map&nodes=organization%2Clegal%2Cevidence&edges=canon%2Cprovenance
CanonLink adapter report
Report route recreates selected adapter graph and print format from URL state.
/reports?graph=adapter-canonlink&format=print-html
Registry playground filter
Playground route recreates adapter format plus node and edge filters from URL state.
/playground?format=registry-api&nodes=registry%2Cschema%2Csystem%2Cevidence%2Clegal&edges=registry%2Cauthority%2Cdependency%2Cprovenance
Playground mode layout filter
Playground route recreates explorer mode, layout, node filters, and edge filters from URL state.
/playground?mode=authority-chain&layout=concentric&nodes=agent%2Cregistry%2Cmission&edges=authority%2Cdelegates
CanonLink adapter report JSON
Report API resolves adapter-prefixed graph IDs and emits structured JSON.
/api/report-demo?graph=adapter-canonlink&format=json
semantic playground
Convert synthetic domain text into an inspectable ontology graph.
input
A public transit hub connects a microgrid, emergency services, water sensors, and maintenance teams through shared incident reports.
graph-native ontology model
{
"domain": "City Infrastructure",
"provenance": "synthetic/example",
"extracted": [
{
"entity": "Transit Hub",
"type": "System",
"attribute": "operational-node",
"relationship": "connects_to",
"target": "Microgrid",
"confidence": 0.74
},
{
"entity": "Microgrid",
"type": "System",
"attribute": "context-node",
"relationship": "reports_to",
"target": "Emergency Services",
"confidence": 0.775
},
{
"entity": "Emergency Services",
"type": "Organization",
"attribute": "operational-node",
"relationship": "depends_on",
"target": "Water Sensors",
"confidence": 0.81
},
{
"entity": "Water Sensors",
"type": "System",
"attribute": "context-node",
"relationship": "monitors",
"target": "Maintenance Team",
"confidence": 0.845
},
{
"entity": "Maintenance Team",
"type": "Organization",
"attribute": "operational-node",
"relationship": "dispatches",
"target": "Transit Hub",
"confidence": 0.88
}
]
}Transit Hub
74%
connects_to
Microgrid
System / operational-node
Microgrid
78%
reports_to
Emergency Services
System / context-node
Emergency Services
81%
depends_on
Water Sensors
Organization / operational-node
Water Sensors
85%
monitors
Maintenance Team
System / context-node
Maintenance Team
88%
dispatches
Transit Hub
Organization / operational-node
relationship explorer
Inspect entities, edges, properties, provenance, and confidence.
entities
entity-edge-property browser
Ontology
type
concept
identity
go:ontology
weight
1.00
| source | edge label | target | provenance | confidence |
|---|---|---|---|---|
| ontology | defines | entity | synthetic/public-demo | 94% |
| ontology | constrains | edge | synthetic/public-demo | 91% |
| translation | preserves | ontology | synthetic/public-demo | 86% |
path reasoning
Traverse explanation chains instead of accepting opaque association.
path reasoning demo
Every answer keeps the relationship chain visible.
hop 1
Ontology
hop 2
Semantic Edge
hop 3
Relationship Reasoning
hop 4
Explainable Claim
Inferred links remain labeled separately from extracted relationships. The public demo shows the pattern, not private weights or operational heuristics.
semantic topology map
A graph lab should feel precise, technical, and alive.
Force-directed ontology graph
Topology-aware intelligence
site architecture
A full platform for graph-native semantic infrastructure.
Graph-Native Ontology
A graph-native ontology treats meaning as a connected system of typed entities, semantic edges, context, and constraints.
Semantic Topology
Semantic topology studies the structure of relationships: hubs, bridges, clusters, paths, gaps, and boundary conditions.
Knowledge Graph Intelligence
Knowledge graph intelligence combines graph construction, traversal, inference, and explanation into a computable meaning layer.
Relationship Reasoning
Relationship reasoning evaluates paths between entities, detects inferred links, and keeps the explanation chain visible.
Entity Mapping
Entity mapping translates messy references into stable graph identities with types, aliases, attributes, and provenance.
Ontology-to-Graph Translation
Ontology-to-graph translation converts classes, properties, and constraints into nodes, edges, and queryable relationship patterns.
Graph Memory Systems
Graph memory systems store durable relationships so intelligent systems can recall context through paths, not isolated snippets.
Graph Query Patterns
Graph query patterns define how builders ask questions about paths, neighborhoods, constraints, and relationship evidence.
Graph Visualization Lab
The visualization lab renders graph structures as precise maps for entities, semantic edges, confidence, and topology.
Semantic Relationship Explorer
The explorer lets readers inspect synthetic entities, edge labels, attributes, provenance, and confidence values.
Graph Intelligence Demos
Demos transform example domain text into entity maps, relationship paths, inferred links, and traversal explanations.
Research Library
A curated library of public concepts, design notes, and reading paths for graph-native semantic infrastructure.
Developer Notes
Developer notes describe practical graph model patterns, schema snippets, traversal logic, and validation boundaries.
GraphOntology Manifesto
The manifesto states the operating principles for graph-native meaning without vague claims or implementation jargon.
Ecosystem Boundary Page
The boundary page separates GraphOntology from adjacent semantic projects and defines its implementation-layer role.
Semantic Infrastructure
Semantic infrastructure connects ontology design, graph persistence, query patterns, and reasoning interfaces into one durable layer.
what we publish
The published surface is educational by design.
Never exposed
Allowed
Differentiated from adjacent projects
GraphOntology is the visual graph inspection and reporting layer.
JSOntology is semantic runtime and schema APIs.
CivilOntology is governance and institutional coordination.
Web4 is the broader semantic infrastructure category.
reusable graph explorer
Inspect, adapt, report, and embed ontology graphs from one shared package.
GraphOntology.com is the public shell. Host apps keep ownership of their data, adapters, permissions, and runtime state while the explorer provides a consistent inspection surface.