Skip to content

feat(wasm): execute task-local losses through scheduler - #26

Draft
GBeurier wants to merge 1 commit into
agent/loss-cabi-controller-bindingfrom
agent/loss-wasm-runtime-controller
Draft

feat(wasm): execute task-local losses through scheduler#26
GBeurier wants to merge 1 commit into
agent/loss-cabi-controller-bindingfrom
agent/loss-wasm-runtime-controller

Conversation

@GBeurier

Copy link
Copy Markdown
Owner

Summary

  • lower explicit native training-loss roles into execution plans with canonical per-node ordering
  • execute prebuilt plans through the WASM scheduler while preserving task-local loss requirements
  • require independently supplied trusted controller manifests before dispatch
  • cover JavaScript-local custom losses in FIT_CV and REFIT, including stale manifests and missing attestations

Validation

  • cargo fmt --all --check
  • cargo test -p dag-ml-core execution_plan_lowers_training_losses_in_canonical_order
  • cargo test -p dag-ml-wasm
  • cargo clippy -p dag-ml-core -p dag-ml-wasm --all-targets -- -D warnings
  • wasm-pack build crates/dag-ml-wasm --target nodejs --release
  • independent review completed twice; final review reported no findings

Stack

Node is unavailable in the local environment; the Node 20/22 smoke is delegated to CI.

@GBeurier
GBeurier force-pushed the agent/loss-wasm-runtime-controller branch 2 times, most recently from f6f0a81 to dd27d47 Compare July 16, 2026 05:40
@GBeurier
GBeurier force-pushed the agent/loss-wasm-runtime-controller branch from dd27d47 to 6a9e708 Compare July 19, 2026 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant