Axon 911 Frontend DocsAxon 911 Frontend Docs
Axon 911 Frontend Docs
    Loading navigation…
U
User
Switch to light mode
  1. Working With Data
  3. Axonmundi
  5. Getting Started

AxonMundi onboarding

Get oriented to the federated graph, Studio, and the Cosmo registry

AxonMundi is a federation prototype that allows different services to bring their own GraphQL APIs (subgraphs) together into a single, unified graph. It runs alongside Prepared911's established GraphQL stack so we can evaluate multi-service composition with the Cosmo Router safely without replacing the canonical API or changing the default integration path. Three parts work together:
  • Mundi is the router and prototype graph endpoint for participating clients.
  • Cosmo Studio is the UI for inspecting graph configuration, composition, schemas, checks, and observed usage.
  • The Cosmo registry is the control plane that accepts subgraph schemas, composes the graph, and delivers the latest valid router configuration.
For the full platform and operator documentation, start with the AxonMundi repository.
Choose your starting point
  • Frontend developer working on the prototype: read Registry and schema workflow to refresh @prepared911/data-gql from the composed client schema. Then follow the existing GraphQL guides for operations and code generation.
  • Subgraph owner: use Studio to inspect checks and compositions, then follow the AxonMundi add a subgraph and subgraph CI runbooks in the owning service repository.
  • Anyone adding or consuming live data: read Real-time data and WebSockets for architecture, protocol contracts, environment limits, and integration requirements.
  • Platform or registry operator: start with the Studio access runbook and the registry cutover runbook. The latter includes privileged environment and credential operations.
Access and credentials
These credentials have different purposes. They are not interchangeable.
Credential or sessionWhat it authorizesWhere it belongs
Studio SSOStudio and registry UI featuresYour browser session
wgc auth loginA human's interactive CLI administration sessionYour local terminal after loading .env.wgc
Prepared access tokenAn end-user request to Mundi and the Prepared911 subgraphAn ephemeral Authorization request header
COSMO_API_KEYNon-interactive CI schema fetch, check, and publicationThe approved CI secret store only
GRAPH_API_TOKENRouter access to the Cosmo control plane and CDNThe router runtime Secret only
Do not save, share, commit, or paste tokens into documentation, PRs, tickets, or long-lived Studio Playground sessions. If Studio login or the CLI device flow does not work, contact the Studio or Platform owner instead of using a shared credential.
Local development and live-dev
Local AxonMundi development can compose the graph from checked-out source without using a registry. The deployed live-dev router, however, receives the latest valid composition from the self-hosted Cosmo registry. In short: if you are building a frontend feature participating in the prototype, you always sync against the registry's composed client schema. You only need local static composition if you are actively testing unmerged router or subgraph changes. The AxonMundi getting-started guide has the complete source-of-truth matrix and local setup instructions.
Next steps
  • Use Cosmo Studio to inspect the graph and safely run a query.
  • Registry and schema workflow to update frontend types from the composed client schema.
  • Real-time data and WebSockets for live updates through Mundi.
  • GraphQL overview for frontend operation and codegen conventions.
Previous
Working with data / Local Storage
Next
AxonMundi / Use Cosmo Studio
On this page
Choose your starting point
Access and credentials
Local development and live-dev
Next steps