Skip to content

Submit a Launch v1.10.0

Choose a tag to compare

@programmable-infra programmable-infra released this 20 Aug 22:59
· 10 commits to main since this release
Immutable release. Only release title and notes can be modified.
c50cb5b

Submit a Launch v1.10.0

Version 1.10.0 makes the current launch contract practical for builders who use Hookbuilder, another agent, or no
agent at all. It preserves the open-world intake: requirements depend on the route and evidence a project actually
selects, not on a fixed list of allowed product ideas.

What changed

  • Added a deterministic Application V3.2 scaffold for no-market, external, unresolved, and official Programmable
    Ethereum routes. The scaffold never invents source, trade, fee, Router, deployment, stamp, or settlement evidence.
  • Clarified the public agent and pull-request guidance so self-built projects and third-party tools follow the same
    canonical contracts and policy as Hookbuilder-generated projects.
  • Added a production-only runtime fee-settlement requirement alongside the existing prelaunch 10 bps commitment and
    finalized Router-stamp requirement.
  • Kept repository-side settlement assertions deliberately analysis-pending. They cannot mint a passed observer
    proof or claim that runtime collection, finality, settlement, future payment, or ongoing monitoring was verified.
  • Extended Active Contract V2 so agents can discover the scaffold and the complete settlement-assertion validation
    closure from one integrity-bound contract.
  • Updated launch-stamp promotion receipts to bind the current Policy 2.1.0 readiness decision while preserving the
    exact accepted Application V3 package and finalized Router evidence.

Authority and compatibility boundary

Application V3.1 remains byte-unchanged legacy compatibility. Application V3.2 remains the current contract for an
official Programmable Ethereum route. A scaffold is only a local draft helper; it does not submit, approve, deploy,
sign, broadcast, classify, promote, or authorize funds.

The enabled launch-readiness profile remains checker-only. The production-launch profile remains disabled. The
new runtime settlement contract documents and structurally validates a pending assertion, but a future independently
anchored observer verifier is still required before that production-only rule can pass.

Verify locally

Use Node.js 24.12 or newer:

npm ci --ignore-scripts
npm test