TFC-01 / GOVERNED CHANGE & RELEASE COURT

Change enters
as evidence.
Not authority.

Forge binds every proposed change to the audited Genesis baseline, challenges it through five release worlds, proves test and rollback evidence, then stops at a signed candidate receipt. Only a human can authorize deployment.

01DIFF

02TEST

03SIMULATE

04ADMIT

05HUMAN

12345678910111212
GATES

RELEASE PLANS5

VERIFICATION STAGES12

BOUND TESTS10

POLICY GATES12

SIGNED CANDIDATES0

01 / DECLARE CHANGESETDRY-RUN ONLY

What must earn
release eligibility?

SYSTEM DOMAINCHANGE CLASS

RELEASE TAGCHANGE SUMMARY

SOURCE DIGEST / SHA-256CHANGE DIGEST / SHA-256ROLLBACK DIGEST / SHA-256

TEST COVERAGE / 96%MAX BLAST RADIUS / 4MAX RISK / 25

01AUTHORITY◆

02SOURCE◆

03AUDIT◆

04ASSURANCE◆

05POLICY◆

06SAFETY◆

07DEPENDENCY◆

08SUPPLY_CHAIN◆

09RISK◆

10ROLLBACK◆

11HUMANITY◆

12EXPOSURE◆

RELEASE PRINCIPALcheckingDEVICE-BOUND / NON-EXPORTABLE / HUMAN-CONTROLLED

I authorize verification and signed candidate creation only. Forge may not alter source, run commands, call tools, approve itself or deploy this change.

02 / SIGNED RELEASE RECEIPTAWAITING CHANGESET

The pipeline begins
with proof.

Declare a content-addressed change and rollback artifact to run the 12-stage court without touching production.

What must earnrelease eligibility?

The pipeline beginswith proof.

What must earn
release eligibility?

The pipeline begins
with proof.