Platform

One knowledge graph, one methodology, one API.

Praxis keeps one knowledge graph filled only from cited sources, assesses it with a published, versioned methodology and serves every result through one versioned API.

Sources, ingestion, versioned storage, assessment engines and the API, with the clients they serve.
How it works

From publisher to every client, without a manual step.

Every record travels the same path from its publisher to every client, and each stage keeps what the next one needs to reproduce it.

  1. 01

    Source catalog

    Every source is listed in code with its publisher, license and citation, and changes only through a reviewed change.

  2. 02

    Ingestion

    On the scheduler's request, each due source delivers one document, validated whole before anything is written.

  3. 03

    Versioned storage

    Every change becomes a new data revision. Past versions are retired, never overwritten, so every past state stays readable.

  4. 04

    Assessment

    Engines compute every assessment from a revision, an as-of date and a methodology release, and from nothing else.

  5. 05

    Delivery

    One versioned API serves every result with its provenance; its OpenAPI document and its agent tools derive from the same definition.

Knowledge graph

Every source placed on the same objects.

A reference registry gives every state, organization and maritime corridor one identity, and connectors place each statistic, conflict party, trade partner and news report on it. A state means the same thing in every source and every model.

  • States and organizations, with their memberships
  • Maritime chokepoints and ports
  • Armed conflicts and armed-conflict risks
  • Sanctions regimes and their targets
  • Statistical indicators, by period and release
  • News reports and forecasting questions
The data behind it
The North Atlantic Treaty Organization selected on the globe, with its member states highlighted and its connections listed in the inspector.
Time discipline

Any date, any revision, the same answer.

When something happened, when it became known and when the platform recorded it are kept apart, so a read can be fixed in time and repeated.

  • As of any date

    An assessment as of a date uses nothing dated or published after it, including later revisions of a statistic.

  • At any revision

    Each change set is a numbered data revision, and every past revision stays readable in full.

  • Again, identically

    Name the date, the revision and the methodology release, and the platform computes the same result.

Guarantees

What the platform guarantees, and how.

Each guarantee is enforced by code and tests that fail without it.

  • Cited sources

    Every record comes from a cited source of a reviewed catalog. No client can submit source data.

  • Published method

    Every number comes from a cited, versioned model applied to data that names its source.

  • Reproducible results

    Name the data revision, the date and the methodology release, and any assessment is computed again, identically.

  • No look-ahead

    Nothing dated or published after the as-of date influences a result at it.

  • Nothing overwritten

    Every change is a new data revision, so every past state of the data stays readable.

  • One API for every client

    The workbench, your systems and AI agents read the same API. The interface computes nothing itself.

  • Denied by default

    Every operation except the readiness probe is authenticated and authorized.

  • Enforced, not promised

    Module boundaries, determinism and published outputs are enforced by tests, not by convention.

Interfaces

People, systems and agents read the same API.

  • Workbench

    Monitor, assess and brief in the browser: modules over one lens, a globe, a time machine and a command bar.

    • Links that reopen a view with the same numbers
    • Alerts and watchlists that follow you across devices
    • Briefs and dossiers exported as Markdown
  • HTTP API

    One versioned API with an OpenAPI 3.1 contract. Every response states the data revision, the lens and the methodology release behind it.

    • Generate clients in any language
    • Conditional reads and stable error codes
    • Briefs and dossiers as JSON or Markdown
  • Model Context Protocol

    The read operations of Praxis as tools for AI agents, with the same credentials and the same answers as the API.

    • Tools generated from the API's own definition
    • Read-only by construction
    • Answers pinned to a date and a revision
Deployment

Hosted for you, or run in your infrastructure.

Praxis runs inside a host application that provides identity, sessions, the scheduler and the gateway. PostgreSQL is its only stateful component.

  • Hosted

    Sign in to the workbench, and call the API and the Model Context Protocol endpoint with credentials we issue.

    • Nothing to install or operate
    • Every model and source from day one
    • Credentials for people, systems and agents
  • Dedicated

    By agreement: the platform behind your gateway and identity provider, with its own database and your scheduler.

    • Your identity provider issues every token
    • Your PostgreSQL database and network policy
    • A sync-only service identity for your scheduler

See the platform on your own questions.

Request access with the themes, regions and decisions you work on, and the way your team will read the answers.