Governance & validation

Trident Orchestrator

Explore Trident's sovereign orchestration model and documented execution paths.

Explore this demo ↓Read the full guide ↗Explore the source ↗

A CLOSER LOOK

How do modeled missions turn into an operator control report?

For operators: inspect the sovereign orchestration scenario, its inputs and the orchestration logic before using the accompanying interface or network launch paths.

Read scenario inputs

Inspect actors, workloads, budgets and controls. Values describe a synthetic scenario and must not be interpreted as live economic performance.

demo/TRIDENT-SOVEREIGN-AGI-ORCHESTRATOR/config/trident.simulation.json ↗

Follow the orchestrator

Trace the configuration through planning, calculations and generated evidence. The separate mainnet launcher is a different, deployment-sensitive workflow.

demo/TRIDENT-SOVEREIGN-AGI-ORCHESTRATOR/orchestrator.ts ↗

Review the operator journey

Read the original guide for report locations, UI use and network prerequisites. Preserve the distinction between rehearsal outputs and authorized operational actions.

demo/TRIDENT-SOVEREIGN-AGI-ORCHESTRATOR/ui/operator-playbook.md ↗

REAL REPOSITORY MATERIAL

Inspect. Understand. Reproduce.

Reading the exact source at revision 5b4cebb3.
This browser inspection does not execute the demo.

JSON source1,514 bytesDownload source ↓View on GitHub ↗

demo/TRIDENT-SOVEREIGN-AGI-ORCHESTRATOR/config/trident.simulation.json

Select a walkthrough step to explore its source.

Full source text

{
  "reportLabel": "trident-sovereign",
  "ipfsGateway": "https://ipfs.io/ipfs/",
  "ensRoot": "trident-sovereign.eth",
  "nations": [
    {
      "name": "Asteria Federation",
      "wallet": "asteria",
      "ensSubdomain": "asteria",
      "mission": "Launch orbital AI task force for food security",
      "specCid": "bafybeigdyrzt5nplu67cde6fywvh7w2fzz6od3as2ko6z5b6b5kvmv2gfu",
      "resultCid": "bafybeihdwdcefgh4dqkjv67uzcmw7ojee6xedzdetojuzjevtenxquvyku",
      "rewardTokens": "125000",
      "deadlineHours": 72
    },
    {
      "name": "Baltic Concord",
      "wallet": "baltic",
      "ensSubdomain": "baltic",
      "mission": "Cross-border energy dispatch intelligence",
      "specCid": "bafybeia6pz2d7h73p3v6svlro5qok7m6hpizpqzphxczr4ixr2l3tktvya",
      "resultCid": "bafybeibwzifnb3k4vuh5fs7yp6um5xszucfn6ov4ybz6xvwz5xucpyn3de",
      "rewardTokens": "98000",
      "deadlineHours": 48
    }
  ],
  "validators": [
    {
      "name": "Neptune Validator Corps",
      "wallet": "neptune",
      "ensSubdomain": "validators.neptune",
      "mission": "Audit orbital data integrity across coalitions"
    },
    {
      "name": "Helios Peacekeepers",
      "wallet": "helios",
      "ensSubdomain": "validators.helios",
      "mission": "Monitor SLA compliance for humanitarian deliveries"
    }
  ],
  "treasury": {
    "name": "Planetary Stewardship DAO",
    "wallet": "stewardship",
    "ensSubdomain": "treasury",
    "mission": "Custody universal surplus and apply treasury policy"
  }
}

SHA-256 163fcd013c282cc6d003305605110526dc98eb640e9c212640ae678983e69462

FROM READING TO A REPRODUCIBLE RUN

Try the selected path.

Node.js workspace

Run from the repository root after nvm install, nvm use and npm ci. Use the versions pinned in .nvmrc and package.json. Commands below describe the selected path; optional app/server packages can have their own locked dependencies.

Complete environment setup ↗

SELECTED EXECUTION PATH

npm run demo:trident-sovereign

What you should observe

The local orchestrator produces scenario evidence and prints its output paths. Inspect generated reports before launching the optional UI.

The source inspector above reads bundled repository material. Local commands run separately on your computer. Recorded examples may contain historical timestamps, placeholders and simulated metrics.

MAKE IT YOUR OWN

One useful experiment.

Pick a budget or control from the configuration and trace it into the report. Identify whether it is checked, calculated or merely described.

THE SYSTEM, MADE VISIBLE

Architecture & relationships

Architecture diagram · source preserved below

View original Mermaid source

flowchart LR
    Operators((Mission Owners)) --> demo_TRIDENT_SOVEREIGN_AGI_ORCHESTRATOR[[Demo → Trident Sovereign AGI Orchestrator]]
    demo_TRIDENT_SOVEREIGN_AGI_ORCHESTRATOR --> Core[[AGI Jobs v0 (v2) Core Intelligence]]
    Core --> Observability[[Unified CI / CD & Observability]]
    Core --> Governance[[Owner Control Plane]]

WHEN SOMETHING DOESN’T MATCH

Troubleshooting

A command or service fails

Start at the first error, confirm the working directory and pinned toolchain, then follow the linked component guide. Optional packages and provider services have separate prerequisites.

A report looks successful but lacks evidence

Check its source revision, configuration, timestamps and underlying events. Historical fixtures and generated plans do not prove a fresh execution.

TRACE THE CHECKS

Verification & next steps

This directory has no standalone test source files. Follow the shared implementation and its behavioral tests before making correctness claims.

For live commissioning, consult the production readiness record.

EVERY VARIANT, PRESERVED

Complete document library

REPRODUCE & INSPECT

Registered commands

Run commands from the repository root after following this demo's guide. Network and owner actions require their documented setup.

npm run demo:trident-sovereign

npm run demo:trident-sovereign:ui

Full command catalog and troubleshooting ↗

ORIGINAL DIRECTORYdemo/TRIDENT-SOVEREIGN-AGI-ORCHESTRATORView on GitHub ↗