Programmable v4 Builder v0.8.0

Programmable v4 Builder v0.8.0

This release makes the current protected Submit a Launch build profile the Builder's complete Programmable requirement
set. At candidate freeze that profile contains one rule: build for Ethereum mainnet and route 10 bps of gross canonical
pool volume to the Programmable treasury.

The Builder still applies its universal Uniswap v4, EVM, source-integrity, and repository-correctness checks as
engineering checks. Those checks cannot silently become extra Programmable launch requirements.

Current launch requirements

• The golden path resolves 0xprogrammable/submit-launch:main before context or construction.
• It reads every active Rule ID applicable to the build profile and adds none from bundled prose, templates, or local
  policy files.
• It returns the exact repository ID, branch, commit, tree, policy and schema blob identities, byte lengths, and
  SHA-256 digests used for the build.
• Missing, caller-authored, stale, or drifted policy authority fails closed instead of falling back to bundled rules.

Protected Submit a Launch binding

The v0.8.0 candidate observed protected Submit a Launch main at these exact coordinates:

• repository ID: 1320171831;
• required branch: main;
• main commit: 2f4f57c8b450489dcd2de29672e31d63ca87ed35;
• repository tree: 33dcc1457e80229fba2236c8a43f29d6ce38317b;
• policy version: 1.2.0;
• policy path: policy/launch-policy.v1.json;
• policy digest: sha256:868c7a647238461f5bbc6afd15bd974d78a1a77f9a13aa1b81044d0e1ffe01dc;
• policy schema: policy/schemas/launch-policy.v1.schema.json; and
• active build Rule ID: LAUNCH.ETHEREUM_AND_TREASURY_10_BPS.

Runtime consumers still resolve current protected main and invalidate stale observations. The coordinates above are
release evidence, not a permanent runtime pin.

Authority boundary

Policy satisfaction is not an audit or automatic approval. The central production-launch profile remains disabled.
This release does not grant review, acceptance, eligibility, deployment, routing, discovery, real-funds, signing, or
launch authority. Protected Submit a Launch and Website services must independently consume and verify the same central
policy for their own decisions.

Local source inventory

Generator-backed local inventories cover 327 production JavaScript modules and a Contract Registry of 50 portable
contracts with 25 validator closures, 1,034 transitive module bindings, and 176 distinct modules. The portable package
contains at most 677 reviewed files. The Fee V2 archive contains 54 unit, one fuzz and three invariant test functions,
and the repository discovers 9 evals/tests/*.test.mjs files. These are source inventories, not audit or production
evidence.

At candidate freeze, bundled lifecycle retains publicationStateVerified: false. The exact clean revision must still
pass protected CI, the complete release rehearsal, artifact reproducibility, tag and GitHub Release verification, and
fresh installed-package verification before v0.8.0 can be called released.

Assurance status

This is an owner-authorized package publication with the repository, protected CI, reproducible packaging, checksums, archive verification, and clean host-install checks completed for the exact release commit. The release receipt remains releaseCandidate: false: real named-model tiers with an independent judge, a trusted separate-UID or container sandbox, a comparable public repository-E2E population, an independently authored novel holdout and prior-release comparator, pinned-fork RPC evidence, and installed-host natural-language-to-submission runs remain EXTERNAL_BLOCKED. Do not describe this package as an audit, automatic approval, production readiness, deployment, or launch authority.