Evidence layers
No single green check proves the whole lifecycle. Each layer answers a narrower question.
- Source reviewDid the exact source revision and its evidence pass the published review gates?
- Launch activationIs the matching execution profile active for the named revision, wallet and chain?
- Wallet executionDid the creator inspect and submit the expected transaction?
- FinalityIs the successful transaction part of the canonical finalized chain?
- Router provenanceDoes the canonical Router record bind the token, pool, hook and launch kind?
- Public projectionDo the indexer, API and website show the same finalized identity?
Review and approval
A review applies to one exact source revision and evidence set. A later commit is a different target, even when its project name is unchanged.
Acceptance is technical readiness for the named scope. It is not an external audit, endorsement, price opinion or promise that a launch will trade.
Router provenance
A valid Launch Stamp Router record establishes that a launch was executed and stamped through the published Router path. Applications can use the recorded kind to label it Programmable Classic or Programmable Custom.
A stamp does not establish current liquidity, tradability, price, audit coverage or support in an external application. Direct factory calls outside the Router do not receive the label.
Roles and controls
Every release should disclose who can change fees, recipients, dependencies, template configuration and future launch controls. The creator wallet controls its own launch transaction. Protocol roles do not sign that transaction on the creator's behalf.
A pause can stop new launches or new authority actions when the relevant contract supports it. It cannot rewrite finalized launches or silently change immutable contracts already deployed.
Use the exact release and deployment records for addresses, code hashes, roles and current control state.
Independent review
The Programmable contracts in the public product repository have not undergone an external audit or public security contest. Internal reviews, tests, static analysis and reproducible release evidence are not substitutes for an independent audit.
A project can publish its own audit or security work. That evidence applies only to the version and scope it names.
Report an issue
Include the affected chain, contract or URL, the exact source revision and a minimal reproduction. Do not post private keys, access tokens, wallet signatures or unpublished exploit details in a public issue.