Web4
Canon papers and semantic infrastructure maps.
embed strategy
Every Askander application embeds the same explorer.
Configuration changes by graph, theme, permissions, and plugins. The core explorer stays reusable and does not own application runtime state.
host apps
Thin adapters across Askander apps.
JSOntology
Schema and contract graphs.
CanonLink
Party, agreement, provenance, and relationship maps.
Valgraf
Value, credit, evidence, and incentive graphs.
Incentivis
Mission and incentive relationship graphs.
MissionStack
Mission trees and dependency maps.
CanonDraw
Ontology diagrams that can open in explorer mode.
PipeFlow
Category and operation maps.
plugin contract
Hosts decide which extensions are allowed.
Permissions
Grant only the capabilities a host wants: read graph, read selection, write view, inspect selection, export graph.
Actions
Plugins can add toolbar actions without changing the core explorer or host route.
Hooks
Export hooks and inspector panels extend behavior while preserving the canonical graph contract.
state contract
Host-owned state stays host-owned.
Shareable URL state
Use the default URL sync for shared explorer views where mode, focus, search, and filters should be shareable.
Embedded host state
Use `syncUrlState=` when a host application owns mode, focus, filters, and navigation state.
Selection callbacks
Use `onSelect`, `onExport`, and `inspectorRenderer` to integrate host context around the canonical graph shape.
trial route
Validate cross-app embedding in one place.
Different hosts
Switch between Web4, JSOntology, CanonLink, Valgraf, and MissionStack host contracts.
Same component
Every trial uses `OntologyGraphExplorer` with host-owned graph, theme, permissions, and inspector props.
No app leakage
Core package behavior remains reusable while host routes decide adapter data and product context.