Governance & validation

Zenith Sapience · Vision

Reconcile exact regional envelopes and supplied costs, keep unknowns visible and inspect unexecuted transfer proposals.

A CLOSER LOOK

Do reported regional amounts reconcile before any envelope change is proposed?

For operators reviewing regional plans: preserve unknown costs, compare exact declared-unit envelopes, and inspect conservative transfer proposals without executing them.

Supply planned and reported amounts

Amounts are exact whole-number strings in one declared unit. Unknown reported costs stay null and hold all proposals.

demo/zenith-sapience/scenario.json ↗

Inspect the original reconciliation engine

The browser bundles this exact engine and existing Hypernova analyzer. Proposals follow input order, conserve units and leave uncovered deficits visible.

demo/zenith-sapience/engine.mjs ↗

Reproduce the local analysis

Run the original Node command. Supplied reports are not verified invoices; no token conversion, transfer, production or settlement approval occurs.

demo/zenith-sapience/README.md ↗

REAL REPOSITORY MATERIAL

Inspect. Understand. Reproduce.

Reading the exact source at revision 4e51d6ae.
This browser inspection does not execute the demo.

demo/zenith-sapience/scenario.json

Select a walkthrough step to explore its source.

Full source text
{
  "schema": "agijobs.zenith-regional-reconciliation.v1",
  "title": "Reconcile regional infrastructure work before proposing budget changes",
  "unit": "declared budget units",
  "totalUnits": "100000",
  "regions": [
    { "id": "north", "name": "North", "allocationUnits": "40000" },
    { "id": "central", "name": "Central", "allocationUnits": "35000" },
    { "id": "south", "name": "South", "allocationUnits": "25000" }
  ],
  "jobs": [
    {
      "id": "relay",
      "label": "Relay inspection",
      "regionId": "north",
      "plannedUnits": "35000",
      "reportedUnits": "45000"
    },
    {
      "id": "backup",
      "label": "Backup maintenance",
      "regionId": "central",
      "plannedUnits": "30000",
      "reportedUnits": "25000"
    },
    {
      "id": "archive",
      "label": "Archive migration",
      "regionId": "south",
      "plannedUnits": "20000",
      "reportedUnits": null
    }
  ]
}

SHA-256 0131e9e16b5cbbd2634149f14a324cfb3cf65e762e33fe2a817e7946c4d1a733

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
node demo/zenith-sapience/run.mjs

What you should observe

JSON reports known-only subtotals, unknown amounts, regional variances, proposal holds and any remaining deficit. Fully funded is true only when complete balanced data has no uncovered deficit.

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.

Supply the missing report, inspect the proposed 5000-unit transfer, then raise that report beyond available envelopes to expose a remaining deficit.

THE SYSTEM, MADE VISIBLE

Architecture & relationships

Architecture diagram · source preserved below
View original Mermaid source
flowchart LR
    Operators((Mission Owners)) --> demo_zenith_sapience[[Demo → Zenith Sapience]]
    demo_zenith_sapience --> 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.

No root-level launch command is associated with this source path. Follow the guide or source directory for its own entry point.

Full command catalog and troubleshooting ↗

ORIGINAL DIRECTORYdemo/zenith-sapienceView on GitHub ↗