Graph Explorer

The graph surface in the current app is centered on /graph.

Two Live Modes

Standard Mode

Route: /graph

This is the default interactive graph explorer used for:

• general exploration
• graph-linked identity and entity context
• filtering and traversal
• standard graph operations

Advanced Mode

Route: /graph?mode=advanced

This is the successor to the older “cartography” framing.

Use it when you want:

• advanced graph controls
• deeper exploratory workbench behavior
• richer graph-analysis workflows

Important Redirect

/cartography now redirects to /graph?mode=advanced.

That means current docs should stop treating cartography as a separate primary route and instead explain it as advanced graph mode.

Querying the Multiplex Graph

The /graph surface exposes the "Graph-Native" architecture. Rather than relying on rigid relational tables, every financial entity (Stablecoins, CBDCs, Members, Legal Entities) and its connections are stored in Neo4j and mapped to the FIBO (Financial Industry Business Ontology) standard.

Natural Language via Fixies

For dynamic or deeply nested queries, Fixies (Letta-powered AI agents) can translate natural language into Cypher queries directly within the explorer.

Example Prompt:

"Show me all cross-border CBDC projects that are currently in the Pilot phase."

The agent translates this to Cypher, executes it against the Neo4j backend, and updates the graph visualization automatically.

GraphQL API

For structured application development, the GraphQL API (@neo4j/graphql) natively traverses relationships without complex JOIN statements. Querying for rwaStablecoins instantly traverses the [:ISSUED_ON] relationships to return supported networks.

Public GraphQL Explorer

For developers looking to inspect and experiment with the network data model, we expose a public, read-only GraphiQL interface at:

https://api.fxyz.network/graphql-explorer

This interactive playground supports full schema introspection, autocomplete, and documentation browsing. For security, it runs in a sandboxed, unauthenticated context and is restricted:

• Read-Only: Any mutation or subscription operations are blocked.
• Whitelist Enforcement: Execution is restricted to public data models such as stablecoin pegs, central bank digital currency (CBDC) projects, and ontology schemas. Private member/user queries are rejected.

Example Sandbox Query:

query PublicAssetStatus {
  ping
  healthCheck {
    status
    environment
  }
  cbdcStats {
    totalProjects
    pilotCount
    launchedCount
  }
  stablecoinPegHealth(limit: 3) {
    name
    symbol
    price
  }
}

Graph Editing

The /graph and /humans?tab=graph surfaces support structural graph editing for members with sufficient permission (NAVIGATOR+ for most operations).

Available actions:

• Click a node and toggle to edit mode to modify its properties inline
• Right-click a node to access type-aware context menu actions (edit, navigate, advance pipeline)
• Backend enforces permission levels per node type (e.g., editing a Circle requires NAVIGATOR, editing a Member requires FOUNDER)

Editing is opt-in per surface. All other graph views (dashboard, profile, mini widgets) remain read-only. The full permission model and architecture are maintained in the engineering repo at docs/architecture/GRAPH_EDITING_SYSTEM.md.

Where Graph Context Shows Up Elsewhere

The graph is also part of:

• /profile
• /circles
• /legal-entities
• /markets/algorithms
• /network/validation

So graph docs should explain both the standalone explorer and the way graph context appears across the wider product.

Documentation Rule

When writing or updating docs:

1. document /graph as the primary route
2. document /graph?mode=advanced as advanced mode
3. refer to old cartography language only as historical context