Trustyu Forge
ADR, schemas, migration, research bundle and projection are versioned and pinned.
Registration frozen on August 4, 2026. The versions, gates, and numbers on this page describe that one cut and are not updated — this is what makes the record auditable. The current state of FORGE 3.1 lives in technical benchmark, today at the cut of August 13th.
Framework milestone · registration of Aug 4, 2026
FORGE 3.1
Specified/Shadow.
The contracts, source-bound cut, and foundation artifacts exist and can be inspected. Products are still in rollout, and their controls do not block the entire fleet. This RC does not declare Fleet Enforced, Operational or Attested.
Runtime, Template, CRM and Hub have foundation releases; each rollout issue remains open.
Public gate 7 has been completed; Gates 2–6 have not yet closed and no missing status becomes a success by inference.
Nine projected claims
Decision linked
to the evidence.
Each block below references v2 projection IDs. The public manifest links claim, visual selector, owner, reviewer, receipts and inference boundary to the same source commit.
API31-C1 · C2 · C3 · C4
API, request spec and coverage are not the same gate
FORGE separates versioned description, compatibility diff, executed request spec and coverage evidence. oasdiff is a useful control; rswag and SimpleCov remain optional adapters of the Ruby profile, not universal authorities.
HARNESS31-C1 · C2 · C3 · C4
The harness maintains explicit limits
QM inspires collaborative surfaces with scope; does not define a normative standard. Session, policy, grants, sandbox, adapters and lifecycle remain verifiable outside the model. Planner/evaluator only comes in after eval and ablation.
SEO31-C2
Structured metadata does not manufacture authority
Schema.org 30.0 provides versioned vocabulary for metadata. This does not prove truth, indexing, ranking, rich results, distribution or citation by AI.
Frozen Origin Bundle
20 sources and receipts, 12 independent groups, three research studies, and nine claims. Projection SHA-256 d326a9af…; artifact manifest SHA-256 3608c795….
Release record JSON access declared by reference
Public claims JSON
RC source catalog
Public record site#22
Confirmed publication: the publication asset was promoted in
trustyu-docs@4ff8c4b and this record entered the website in trustyu-jarvis-site@c731074. Gate 7 is completed; this does not promote runtime and product gates.Shadow artifacts
Foundation published.
Adoption still measured.
Published version proves availability of the artifact, not its adoption by every consumer. Therefore, the four releases below remain classified as shadow foundations. These are the versions in force on August 4th — the fleet has advanced since then, and current versions are in benchmark.
Critical Sequence 2–7
What's missing
for GA.
Public gate 7 was completed by promoting docs#383 and deploying site#24. The promotion for FORGE 3.1 GA — Fleet Enforced still requires verifiable completion of gates 2–6. Release, file or text does not replace real artifact linked to SHA and independent validator.
Numbering of this record. Sequence 2–7 below is from the August 4th cut. The current Terminal Definition of Done in 3.1 is G1–G6 and it's in benchmark, which replaces this table as the current state. Neither numbering creates a new gate: they describe the same path to GA in different slices.
| Seq. | Gate | RC State | Tracking issues |
|---|---|---|---|
| 2 | Runtime evidence v2 and closing the forge check | Published artifact; open closeout | internal record · infra#390 |
| 3 | ARR v2, Harness Fingerprint and effective policy | Open | internal logs · ai-env#68/#72 |
| 4 | Template golden path v2 | Shadow; open closeout | internal registry · template#232 |
| 5 | CRM and Hub with real artifacts and rollout shadow → enforce | Shadow; pending enforcement | internal records · CRM#1840/Hub#764 |
| 6 | Agentic trace-native quality | Open | internal record · Hub#765 |
| 7 | Source-bound citations and factual publishing | Completed · Aug 4, 2026 | docs#370 · public site#22 |
Articles was blocked when this registration was made. On August 4, the docs#367 knowledge program still had no route. The block was lifted by human approval recorded on August 9, 2026 (docs#367 · site#31), and the editorial route is published at /articles/. The opening of the editorial program is its own gate and does not promote none of the runtime and product gates on this page.
The identifier of this URL says
rc; the landmark does not. This record was published under the name “FORGE 3.1 RC” and the path preserves this identifier so as not to break already distributed links. The name has been corrected to FORGE 3.1, which is what the canon has always called the milestone. The rc here was never the channel ADR-0066, which governs repository tags in the SemVer pre-release suffix (X.Y.Z-rc.N) and requires that only corrections go in — no fleet repository loads 3.1.0-rc.N. The scale that applies to this milestone is the one published above: Specified, Shadow, Fleet Enforced, Operational, Attested.No implicit promotion: specified means versioned contract; shadow means artifact emitted and measured without blocking. Enforced, Operational and Attested require their own gates and are not derived from this page.