Run & Deploy — Forge Proof Layer

No build step and no runtime dependencies beyond Node.js. The Proof Layer is a set of repo tools plus two always-applied rules.

Tools (repo root tools/)

• forge-proof.mjs — Proof Layer engine (state, grade, Trust Score, challenge, decision).
• forge-gate.mjs — fail-closed gate for deliver/publish/certify/benchmark/commit.
• forge-proof-verify.mjs — independent checksum self-test.
• forge-portfolio.mjs — proof-aware portfolio publisher.

Policy (always applied)

• .cursor/rules/forge-proof-standard.mdc — Proof Layer authority, seven states,

Evidence Grades, Trust Score, claim-to-evidence chain, CEO restrictions.

• .cursor/rules/forge-delivery-pipeline.mdc — the mandatory gate in the pipeline.

Wire it into a pipeline

Call the gate at each release boundary and halt on a non-zero exit:

node tools/forge-proof.mjs --outcome delivery-package/<slug> --verify "<cmd>" --report verification-report.json
node tools/forge-gate.mjs  --outcome delivery-package/<slug> --action deliver   || exit 1
node tools/forge-gate.mjs  --outcome delivery-package/<slug> --action publish   || exit 1
node tools/forge-gate.mjs  --outcome delivery-package/<slug> --action commit     || exit 1

Publish

node delivery-package/forge-proof-layer/publish.mjs   # this outcome's page + proof copy
node tools/forge-portfolio.mjs                         # rebuild the proof-aware portfolio

GitHub Pages deploys published/ automatically on push to main.