feat: end-to-end pipeline attestation example + wasm_optimize loom fix#446
Merged
feat: end-to-end pipeline attestation example + wasm_optimize loom fix#446
Conversation
examples/pipeline_attestation/ exercises the full attestation surface on a
single tiny Rust component:
rust_wasm_component_bindgen -> wasm_sign -> wasm_attest
|
wasm_show_chain (JSON) |
wasm_verify_chain |
|
all verified green
Verified locally: `bazel build //examples/pipeline_attestation:all_pipeline_outputs`
emits a wsc "Transformation chain is valid" marker and a JSON artifact with
one attestation entry recording input hash, output hash, tool name/version
and timestamp.
The example deliberately uses wasm_attest (not meld_fuse or wasm_optimize)
because meld_fuse needs a multi-component setup and wasm_optimize has a
pending WASI path-resolution issue — loom reads `bazel-out/...` paths via
WASI and `--dir=.` does not follow the bazel-out symlinks. Documented in a
TODO in wasm/private/wasm_optimize.bzl. While touching that file also
dropped the stale `--` subcommand separator that loom 0.3.0 rejects.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
examples/pipeline_attestation/— an end-to-end demo of the PulseEngine attestation surface on a single tiny Rust component:rust_wasm_component_bindgen → wasm_sign → wasm_attest → wasm_show_chain + wasm_verify_chain.--subcommand separator fromwasm/private/wasm_optimize.bzl(loom 0.3.0 rejects it) and adds a TODO noting the remaining WASI path-resolution issue that blocks end-to-end loom runs under Bazel.Context
Follow-up to #442 / #444 / #445. Those PRs landed the pipeline rules, the meld native toolchain, and the attestation rule family — this one assembles a real demo so users can see the whole flow working without needing to stand up a multi-component fusion setup.
Test plan
bazel build //examples/pipeline_attestation:all_pipeline_outputs— produces awsc "Transformation chain is valid"marker and a JSON chain artifact with one attestation entrywasmsign2 0.2.6), and timestampbazel build //examples/pipeline_attestation:greeter_chain_verifiedalone — verify-chain ship-gate succeedsWhy not
meld_fuseorwasm_optimizein this examplemeld_fuseneeds two or more components with compatible interfaces — a full fusion demo is more than this example intends to set up. A follow-up can add it.wasm_optimize(loom) has a pending WASI path issue: loom.wasm readsbazel-out/...paths via WASI and--dir=.does not follow the bazel-out symlinks. Documented in a TODO inwasm/private/wasm_optimize.bzl; fixing it cleanly will want a small Go wrapper mirroring the one we already use for wsc. Out of scope here.wasm_attestis sufficient to exercise the entire sign/attest/verify/show surface against a single component, which is the goal.🤖 Generated with Claude Code