Skip to content

Release standard: stand up a real signed release, then witness + scry, re-enable Kani #356

Description

@avrabe

Sweep finding: kiln is the wasm interpreter/runtime yet has the weakest pipeline of all — there is no release.yml (the publish.yml only deploys docs), nothing is released or published, no signing/SBOM/SLSA, and its Kani harnesses, capability tests, and verification dashboard are all .disabled.

Track A + B — stand up a real release (priority):

  • Add a release.yml producing signed artifacts (cosign + SHA256SUMS + CycloneDX SBOM + SLSA — synth-canonical).
  • Publish crates to crates.io (signed CI); add npm wrapper if there's a user-facing CLI.

Track C — wasm gates:

  • Add witness MC/DC + scry gates on wasm kiln handles.
  • Re-enable the disabled Kani verification + the verification dashboard.

Track E: wire an executable rivet verification gate (currently static requirements.toml only).


Part of the org-wide release-consistency campaign — the five-track standard is in the release-artifact-pipeline skill (plugin v0.10.0).
Coordination hub: pulseengine/pulseengine.eu#98 — if this standard does not fit this repo (you need a deviation, different sequencing, or want to sync on how a track applies), raise it there. Deviations are decided in the open at the hub, not diverged silently.

Metadata

Metadata

Assignees

No one assigned

    Labels

    release-standardOrg-wide release-consistency campaign (five-track standard); coordinate at pulseengine.eu#98

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions