Skip to Content
Choose an operating mode

Choose an operating mode

Use the mode whose evidence boundary matches what you want to verify.

ModeServices and resourcesEvidencePersistenceValid claim
Hosted guided simulationBrowser and hosted Next.js appVersioned checked-in fixtureNone beyond the page sessionThe scripted product states and transitions render correctly.
Locally run simulationNode.js 22 or 24 LTS and pnpm 11The same checked-in fixtureNo PostgreSQL gate historyThe app and fixture-backed flow run from your checkout.
Local-liveDocker Compose v2, 2 CPU, 8 GB RAM, 13 GB disk; Payne web, worker, PostgreSQL, DataHub Core 1.6.0, MCP, inference choice, sandboxCurrent reads from the bundled local DataHub scenarioPostgreSQL and named Compose volumesThe bounded local workflow ran against the observed local catalog state.

Hosted simulation has no live connection to DataHub, PostgreSQL, the worker, or an inference provider. Local-live is a local development and evaluation profile, not a production deployment.

Operating modes and system ownership

Components and ownership

  • Visitor browser — Renders public UI Owner: visitor.
  • Hosted Next.js — Landing, docs, guided simulation Owner: Payne application.
  • Versioned fixture — Checked-in simulation evidence Owner: repository.
  • Payne web — Local workspace and server actions Owner: Payne application.
  • Payne worker — Durable jobs and monitoring Owner: Payne application.
  • PostgreSQL — Payne durable state owner Owner: Payne.
  • DataHub + MCP — Current catalog facts and bounded reads Owner: DataHub.
  • Inference provider — Bounded interpretation Owner: configured provider.
  • Official sandbox — Bounded application and re-ingestion Owner: Payne local-live.

Relationships

  1. The visitor opens the hosted Next.js application.
  2. Hosted simulation reads a checked-in fixture and has no live service connection.
  3. The visitor opens the locally running Payne web process.
  4. Payne web reads and writes authorized durable product state.
  5. The worker claims jobs and persists immutable evidence and outcomes.
  6. Adapters discover bounded reads through MCP and use official interfaces for allowlisted application writes.
  7. The worker sends bounded evidence for interpretation; the provider cannot set gate state.
  8. The worker applies the accepted fixture artifact only inside the official sandbox.
  9. The bounded scenario updates lineage before Payne performs a fresh read.
Open interactive trust map

Interactive diagram loading. The relationship list remains available.

React Flow

Use the guided simulation for a quick evaluation or the local quickstart to exercise current local evidence.

Last updated on
Configure Ollama inferencePayne prerequisites