# Vaultfire frozen-source acceptance

The completed acceptance selects protocol source `a96486bc798fda53a4fac674726d28100e7a26af`, tree `5f2b9856fbeea2721f87ef84138e6876d7c3113d`, archive SHA-256 `721da3d13e2b755dda90abfb2ab660d8a5a62404afd01499fb285d3c03d22a8f`. Source identity is separate from the eventual website publication P.

## Executed evidence

- **Distributed source:** All 14 selections passed against a strictly verified clean extraction, including the early full portable website regressions, public quickstart, both SDKs, maintained protocol/finance composition, all 70 core selections, finance controls, independent economic differentials and mutation checks.
- **Website:** The exact unchanged website inputs have a measured ten-command pre-freeze producer, including the complete Node suite after the fresh canonical nine-validation receipt. These browser/build executions are input-bound pre-freeze evidence, not relabeled fresh archive browser execution.
- **Preserved attempts:** Failed commands, timeouts, operator mistakes and resource failures remain separately recorded. Explicit skips and earlier native source/artifact correspondence are not promoted into newly executed or public-chain acceptance.
- **Local finance:** Disposable chain 31337, direct-runtime 18-decimal MockERC20, isolated policy signer, exact approvals, connected invoice/treasury/escrow/bonds, separate rewards and accounting/recovery. Delivery and observation examples remain synthetic.

## Qualification boundaries

Local success does not establish genuine positive SP1 proving, public-chain finality, Base/USDC or Solana finance qualification, real merchant fulfillment, independent human/economic approval, staffed custody/operations, or permission to use public funds. Public V3 activation, signing, payments and partner funds remain disabled. Accountability and Partnership Bonds retain their distinct consent and settlement rules; principal, remedy reserves and sponsor rewards remain separate.

## Inspect the records

Read `acceptance.json` for exact identities, evidence classes and remaining gates. Extract `acceptance-evidence.tar.gz` into a separate folder and run `sha256sum --check --strict SHA256SUMS` there before inspecting the raw logs; the transport checksum is published in this directory's `SHA256SUMS` and on its download page.