# REPRODUCE — forge-pm-work-order-sim

> FICTIONAL / SYNTHETIC DEPLOYMENT MODEL. Every number is reproducible from a seed.

## Prerequisites
- Node.js >= 20.
- `../work-order-agents` with dependencies installed (the simulation imports the
  ecosystem and reuses its `node_modules`). If needed:
  `cd ../work-order-agents && npm install`.

## Reproduce every operational number
```bash
cd delivery-package/forge-pm-work-order-sim
node verify.mjs
```
This regenerates the 100,000-order corpus (seed `20260625`), runs the real
ecosystem, and writes `verification-report.json` + `verification-report.md` and
`evidence/{simulation-results.json, roi.json, audit-trace-sample.json}`.

To iterate quickly at reduced scale (proportional mix):
```bash
WO_SIM_N=2500 node verify.mjs
```

## Reproduce the executive + certification reports
```bash
node build-deliverables.mjs
```

## Reproduce the public page
```bash
node publish.mjs
```

## Reproduce the proof package + gate (from repo root)
```bash
node tools/forge-proof.mjs --outcome delivery-package/forge-pm-work-order-sim \
  --verify "node verify.mjs" --report verification-report.json \
  --outcome-seam "Fictional enterprise customer and 100% synthetic data/assumptions; no real deployment."
node tools/forge-proof-verify.mjs --outcome delivery-package/forge-pm-work-order-sim
node tools/forge-gate.mjs --outcome delivery-package/forge-pm-work-order-sim --action publish
```

## Determinism guarantee
The corpus carries a content fingerprint (recorded in
`verification-report.json#/dataset/corpusFingerprint`). A MUST_PASS check asserts
that re-generating from the same seed yields the identical fingerprint, so any
engineer obtains the same inputs and therefore the same metrics.
