FForge Outcome Delivery
Forge Proof Layer

Release Notes

← Back to outcome

Release Notes — Forge Proof Layer v1.0.0

Date: June 25, 2026

Summary

The Proof Layer is now a mandatory, non-bypassable architectural gate with final authority over every claim. Verification is no longer the last word — the Proof Layer sits between Verification/Repair and Certification/Delivery/Publication.

Added

  • Seven certification states: NOT_STARTED, BUILD_FAILED,

FUNCTIONAL_DELIVERED, VERIFICATION_INCOMPLETE, PROOF_INCOMPLETE, CERTIFIED, PRODUCTION_VALIDATED. Only the Proof Layer assigns the top two.

  • Evidence Grade (A+..F) in proof/EVIDENCE_GRADE.md.
  • Trust Score (0–100, 10 scoring + 6 penalty categories) in proof/TRUST_SCORE.json.
  • Auditor Challenge per outcome in proof/AUDITOR_CHALLENGE.md.
  • PROOF_DECISION.json — the gate's authoritative allow/block record.
  • tools/forge-gate.mjs — fail-closed gate (exit 0/1/2).
  • tools/forge-portfolio.mjs — portfolio cards now show Functional /

Verification / Proof status, Evidence Grade, Trust Score, disclosed seams, limitations, verification summary, and reproduction status.

Changed

  • tools/forge-proof.mjs extended with grading, scoring, the challenge, the

decision record, and the seven-state machine. The marketing-language scanner now treats code-span/quoted identifiers as non-marketing.

  • .cursor/rules/forge-proof-standard.mdc and forge-delivery-pipeline.mdc

encode the Proof Layer's authority and the mandatory gate.

  • docs/CURRENT_ARCHITECTURE.md documents the new pipeline and Proof Layer stage.

Disclosed seams

  • Grade A/A+ and PRODUCTION_VALIDATED require external/official inputs not

present in this environment, so those paths are defined but not exercised here.