BOUNDARY Forge

Inspect the source. Verify the evidence. Hold the release.

COPPER FOUNDRY / SOURCE VERIFICATION

Verification Workbench

Safe · GitLab Duo repair

Recheck the preserved J1 repair source against the pinned runtime policy. Historical Duo attribution and CI; source integrity checks run now.

Unsafe · weakened guard

A real controlled Git commit replaces the protected guard with an unconditional approval. The source tier inspects it as data; its separate bounded behavioral attempt fails closed.

Forged · release receipt

The genuine repair source is paired with a receipt claiming a different commit and tree. Source-to-receipt binding must fail.

Locked software-source experiments. Each run creates a fresh report. The source tier never imports or executes candidate code; PASS-tier candidates additionally run the J1 deterministic contracts inside the bounded, identity-pinned oracle runner (custody fail-closed). All three use the same verifier as the operator CLI. A run performs a real independent verification and typically takes 30–75 seconds; progress is shown live below.