Skip to content

Submit a Launch v1.6.1

Choose a tag to compare

View all tags
@programmable-infra programmable-infra released this 16 Aug 18:48
· 24 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.6.1
86be682
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Version 1.6.1 lets a semantically valid custom Submission V2 at stage: proposal enter the protected Application
V3.1 Draft intake when legacy Fee V2 is explicitly not-selected.

What changed

  • Accepted policy-neutral proposal packages only when their compatibility report remains
    architecture-review-required.
  • Preserved the exact all-null legacy Fee V2 tuple for not-selected submissions.
  • Rejected proposal packages that fabricate a trade-capability manifest, trade-test result, prototype readiness, or a
    mismatched Application stage.
  • Kept the existing prototype and selected legacy Fee V2 paths unchanged.

Authority boundary

A valid proposal package creates only an unreviewed Applicant Draft eligible for independent review. It does not prove
prototype readiness, trade capability, testing, audit, deployment, availability, approval, or launch authorization.
Candidate repository content remains inert data under the protected-base validator.

Verify locally

Use Node.js 24 or newer:

npm ci --ignore-scripts
npm test
Assets 3
Loading