Economic models

Redenomination

Explore denomination changes through an illustrative economic model and interface.

A CLOSER LOOK

How can an operator rehearse a denomination-sensitive job?

For governance and treasury operators: trace a modeled job through validation, owner controls, emergency handling and report verification.

Read the actors and phases

The scenario defines actors, a flow and policy expectations. Its embedded diagram is a narrative model; inspect the implementation before treating any step as executed.

demo/REDENOMINATION/scenario.json ↗

Follow the demonstration

Trace the exported scenario, evidence and report generation. The owner console and guardian drill are separate paths with their own prerequisites.

demo/REDENOMINATION/scripts/run-demo.mjs ↗

Inspect the verifier

The verification script checks scenario structure and evidence relationships. It does not establish that a live currency redenomination or network upgrade occurred.

demo/REDENOMINATION/scripts/verify-scenario.mjs ↗

REAL REPOSITORY MATERIAL

Inspect. Understand. Reproduce.

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

demo/REDENOMINATION/scenario.json

Select a walkthrough step to explore its source.

Full source text
{
  "name": "REDENOMINATION",
  "description": "A governed computer-work mission and exact redenomination planning rehearsal. Produces reviewable drafts and evidence; does not deploy contracts, migrate balances, execute a worker or authorize settlement.",
  "mermaid": "graph TD;\n    A[Employer Alice posts redenomination job] --> B[JobRegistry records specification & policy tags];\n    B --> C{AGI Agent Selection};\n    C -->|Stake + ENS verified| D[Agent Hyperion-9 claims assignment];\n    D --> E[Off-chain AI pipelines produce redenomination dossier];\n    E --> F[Result hash + signature submitted on-chain];\n    F --> G[Chainlink VRF seeds validator committee];\n    G --> H[Commit window opens & validators encrypt verdict];\n    H --> I[Reveal window enforces accountability];\n    I --> J{Majority approves?};\n    J -->|Yes| K[Certificate NFT + payout released];\n    J -->|No| L[Dispute escalates to Sentinel moderators];\n    L --> M{Moderator quorum};\n    M -->|Override| N[System pause & slashing executed];\n    M -->|Uphold| K;\n    K --> O[Observability index updated];\n    O --> P[Prometheus & Grafana dashboards refresh];\n    O --> Q[On-chain audit log immutably sealed];\n    Q --> R[One-click deployment audit trail completed];",
  "actors": [
    {
      "role": "Employer",
      "label": "Alice",
      "goal": "Specify the conversion, approved sources, deliverables, budget and measurable acceptance criteria."
    },
    {
      "role": "AGI Agent",
      "label": "Hyperion-9",
      "goal": "Use an approved OpenClaw or operator-led ChatGPT Work environment to prepare a candidate dossier and evidence."
    },
    {
      "role": "Validator",
      "label": "Validator Guild",
      "goal": "Independently recompute base-unit arithmetic, reconcile liabilities and reject incorrect evidence before any acceptance decision."
    },
    {
      "role": "Moderator Council",
      "label": "Sentinel Multisig",
      "goal": "Review disputed evidence and follow the deployed contracts and authorized incident procedure; no powers are inferred from this demo."
    },
    {
      "role": "Governance",
      "label": "Timelock DAO",
      "goal": "Separately authorize reviewed governance actions after checking the actual chain, ownership and configured timelock."
    }
  ],
  "flow": [
    {
      "phase": "Initialization",
      "steps": [
        "Run the offline generator and verifier; inspect the source hashes and exact conversion ratio.",
        "For a live job, commission isolated worker tools and accounts using docs/computer-work.md; the demo requires none.",
        "Verify actual token decimals, chain, owner, identities and contracts before considering deployment or admission.",
        "Keep signing credentials outside the worker; agree acceptance rules, dust allocation and recovery responsibilities."
      ]
    },
    {
      "phase": "Job Lifecycle",
      "steps": [
        "Employer Alice defines a redenomination dossier using public, licensed non-personal or synthetic data.",
        "Review computer-work/task.json, allowed origins, bounded deliverables and source data; admit its exact digest through the existing adapter.",
        "An approved OpenClaw worker uses browser, computer, code and file tools as configured; ChatGPT Work is a separate operator-led option.",
        "Worker returns conversion.json and dossier.md, with source references and a complete description of residual amounts.",
        "Independent review checks every account, base-unit conversion, aggregate reconciliation and missing or duplicate entries.",
        "Rejected or uncertain work retains its evidence and requires correction or reconciliation before a new admitted attempt.",
        "Accepted candidate evidence enters the separately commissioned validator and contract lifecycle; provider completion does not release payment.",
        "Production readiness requires receipts, finality, incident drills and deployment-specific authorization."
      ]
    },
    {
      "phase": "Emergency Drill",
      "steps": [
        "Run the guardian drill to check saved artifacts and review emergency procedures; it sends no transactions.",
        "Rehearse an authorized pause on a disposable deployment and stop in-flight workers through their own controls.",
        "Reconcile unknown outcomes, pending liabilities and disputed work; preserve dispatch and settlement journals.",
        "Verify real state and required approvals before resumption. A successful offline drill is not a production-readiness certificate."
      ]
    }
  ],
  "metrics": {
    "validationCommitteeSize": "Deployment-specific; verify actual committee",
    "stakeRequirementAgent": "See exact generated agent-role threshold below",
    "stakeRequirementValidator": "See exact generated validator-role threshold below",
    "auditSampleRate": "Set by approved task and deployment policy",
    "governanceTimelock": "Verify deployed timelock; no fixed delay assumed",
    "marketOpportunity": "$40 trillion/year project planning assumption; unverified",
    "executionMode": "Offline planning only"
  },
  "resources": {
    "docs": [
      "docs/governance.md",
      "docs/system-pause.md",
      "docs/institutional-observability.md",
      "demo/REDENOMINATION/README.md",
      "docs/computer-work.md",
      "demo/One-Box/computer-work/README.md"
    ],
    "scripts": [
      "npm run demo:redenomination:verify",
      "npm run demo:redenomination:export",
      "npm run demo:redenomination:control-room",
      "npm run demo:redenomination:owner-console",
      "npm run demo:redenomination:guardian-drill",
      "npm run demo:redenomination:mission-control"
    ]
  },
  "diagramStatus": "Original vision diagram, preserved verbatim. Specific VRF, encryption, immediate payout and moderator powers require separate implementation and verification; see README.",
  "deploymentReference": "deploy:oneclick:auto and monitoring:validate remain repository tools, requiring their own setup and review. This rehearsal does not execute them."
}

SHA-256 6c7be15f93cdc3e2f12f1436bcc6dc197e826c593e4ce133c40ebcb51f4aa383

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:redenomination
npm run demo:redenomination:verify

What you should observe

Scenario artifacts and verification output are produced locally. Inspect the report and exported UI data before opening mission control.

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.

Follow one failure or dispute branch in the scenario and identify the actor authorized to handle it. Distinguish a prepared control from an executed transaction.

THE SYSTEM, MADE VISIBLE

Architecture & relationships

Architecture diagram · source preserved below
View original Mermaid source
flowchart TD
    Brief["Task, sources and acceptance rules"] --> Admit["Admit exact task digest"]
    Admit --> Worker["Isolated screen and file worker"]
    Worker --> Evidence["Candidate files and receipt"]
    Worker --> Unknown["Interrupted or uncertain outcome"]
    Unknown --> Reconcile["Inspect actual effects and journal"]
    Evidence --> Check["Independent arithmetic and dossier review"]
    Check -->|Reject| Correct["Separately admitted correction"]
    Correct --> Admit
    Check -->|Accept| Govern["Authorized validation and final settlement"]

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

4 tracked test source files are available in this directory. Inspect the tests and their environment before choosing a suite; file counts do not establish test results.

Browse the test sources

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:redenomination
npm run demo:redenomination:control-room
npm run demo:redenomination:export
npm run demo:redenomination:guardian-drill
npm run demo:redenomination:mission-control
npm run demo:redenomination:owner-console
npm run demo:redenomination:verify

Full command catalog and troubleshooting ↗

ORIGINAL DIRECTORYdemo/REDENOMINATIONView on GitHub ↗