TrustTECHNICAL AREA · FORGE 3.3.0-alpha.1
Examine the system.
Not just the promise.
This layer brings together what can be inspected publicly: architecture, method, version, artifacts, verifiers, and boundaries. The complete source remains restricted when exposure would create risk or false verifiability.
Verified in owner repo does not mean operating. The state supports mechanism and tests in the responsible repository; adoption, real execution and fleet outcomes require their own evidence.
DEPTH LAYERS
Choose what you want to verify.
Release 3.3
Outcomes, gates, Alpha state, and cut boundaries.
LEGACY ADOPTIONBrownfield
Characterization, reconciliation, and wave-based migration.
DATED STUDIESBenchmark
Comparisons, sources, method, and preserved history.
PROVENANCEReferences
Papers, standards, models, and official sources.
FORGE PUBLIC EVIDENCE MAP · V2 · UPDATED SEPTEMBER 8, 2026
Every claim with an artifact, verifier, and boundary.
The map combines the immutable Alpha cut record with a later evidence ledger. Technical progress appears without rewriting the version or turning mechanism into adoption.
| Capability | State | Artifact | Checker | Validity | Inference boundary |
|---|---|---|---|---|---|
| G0Release contract | Implemented | /releases/forge-3.3/release-record.json | scripts/build_forge33.py | exactly 3.3.0-alpha.1 and its bound canonical source | Supports consistency of the public mechanism declaration; it does not prove adoption, operation or outcomes. |
| G1Durable spec | Implemented | /releases/forge-3.3/release-record.json | scripts/build_forge33.py | exactly 3.3.0-alpha.1 and its bound canonical source | Supports consistency of the public mechanism declaration; it does not prove adoption, operation or outcomes. |
| G2Governance | Implemented | /releases/forge-3.3/release-record.json | scripts/build_forge33.py | exactly 3.3.0-alpha.1 and its bound canonical source | Supports consistency of the public mechanism declaration; it does not prove adoption, operation or outcomes. |
| G3Fail-closed verdict | Verified in owner repo | forge-v0.26.0 · gate-verdict/v2 | runtime suite and source SHA CI | owner repo at SHA c55b0b08; per-consumer adoption not included | It does not prove that every fleet gate emits the contract or that the verdict is enforced. |
| G4Gate lifecycle | Verified in owner repo | forge-v0.26.0 · gate-lifecycle/v1 | assessment 34161130913 · 3/3 receipts | short window in owner repo; false-positive rate and enforcement have no denominator | It does not authorize automatic promotion, warn, enforce or fleet operation. |
| G5Reviewed release | Implemented | forge-v0.26.0 · 9 assets | release run 34165466888 | tag and assets bound to SHA c55b0b08 | A sanctioned bypass does not equal independent human review of the content. |
| G6Fleet propagation | Implemented | /releases/forge-3.3/release-record.json | scripts/build_forge33.py | exactly 3.3.0-alpha.1 and its bound canonical source | Supports consistency of the public mechanism declaration; it does not prove adoption, operation or outcomes. |
| G7Delivery integrity | Under investigation | G7 v1 replay + receipt sha256:220f8939… · restricted technical access | trustyu-docs#760 · trustyu-crm#2105 · run 34240297679 | historical window of 240 deployments + promotion observed on 2026-09-08; main and staging at ea3a6f1c… | The guard remains post-merge/advisory; without an immutable artifact digest, real recovery or production blocking. |
| G8Outcomes | Verified in owner repo | forge-v0.26.0 · delivery-effectiveness/v1 | 1,096 tests and source SHA CI | mechanism in owner repo; fleet result is insufficient-data | Without two services and a sufficient window, there is no baseline, trend, causality or benchmark. |
| SECData perimeter | Verified in owner repo | forge-v0.26.0 · agent-data-profile/v1 | negative tests and source SHA CI | mechanism in owner repo; consumer profiles are still absent | It does not prove a DPA, destination configuration, exercised deletion or fleet operation. |
HOW TO START
Start with the decision, not the tool.
- Bound the intent. Problem, outcome, constraints, and out of scope.
- Choose the path. New product, evolution, or Brownfield.
- Define the evidence. Artifact, verifier, validity, and human authority.