open-standards/wai/wai-int-module/record/manifest.json
Transaction Science 98d646dc92 wai-int-module: the first WA²ISM module of record, the operator-set module held at the integer level on every engine
wai/wai-int-module is one WebAssembly module with the interface of waism §5 and nothing else:
no import, one memory with a declared maximum, and every allocation trapping where memory
cannot grow (R13). It decodes the integer payloads (WIV1, WIH1, WIA1, WIS1), int_synth,
int_mlicpp, opus.dred.int and avatar.face through wai-rs's integer decoders, whose networks
run on wai-ops/1; networks and weights arrive as each capability's set.

- record/: the scalar and SIMD128 builds (7,099 vector instructions), named by SHA-256 in
  manifest.json, each held at the integer level by the Rust checker and check-module.mjs.
  build.sh builds both with the machine's paths remapped and checks both with both checkers.
  A build on another host has other bytes (the compiler's crate hashes take in each path
  dependency's absolute path and the host) and gives every case the same outcome.
- corpus.json (corpus.py): every committed vector and refusal fixture of those
  capabilities, 120 cases, from the committed corpora.
- host/ (wasmtime 50.0.1 Cranelift and Winch, Wasmi 2.0.0 with floats off), run-node.mjs and
  browser/run-browser.mjs run every case as a sink does and print one run digest; every run,
  on Linux x86_64, Linux arm64 and macOS arm64, gives the same.
- plant.py plants a float or a relaxed vector instruction in a module, for the checkers.
- waism §5, The set: one file as its bytes, several as their file sequence. avatars §6 names
  generator.wfg and identity.wfi; avatars §7.8, opus-dred §4.8 and determinism-tiers §5 state
  the module as a fabric.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-08 16:45:56 -05:00

25 lines
1.4 KiB
JSON

{
"format": "waism-module-record/1",
"about": "The modules of record of wai-int-module, the operator-set module: WAISM's integer level (extensions/waism.md, waism/1-int), held by both of the profile's checkers. Each file is named by its SHA-256; the CI step module-check.sh holds this directory to it.",
"level": "waism/1-int",
"files": {
"wai_int.wasm": {
"sha256": "dae995c03d0478f961e7c9692bcb41ddaf87c79591964f6a8a192e3637665b19",
"bytes": 765069,
"build": "scalar",
"instructions": 314437,
"vector_instructions": 0
},
"wai_int.simd128.wasm": {
"sha256": "6158ca3aed0682c096680dd6186790f7942242bf17c3ab2edee2ab0bad09eaba",
"bytes": 773155,
"build": "SIMD128: -C target-feature=+simd128",
"instructions": 313155,
"vector_instructions": 7099
}
},
"source": "wai/wai-int-module as the commit that adds this file has it, over wai/wai-rs and wai/wai-ops as main had them at f4578857a484be7a52122dd874c834d75de447a2, with the crates Cargo.lock pins",
"cargo_lock_sha256": "1fc1f4589c3a2a5dceaeed874ef5523985dc034d24fcf020d7b43c6e2d1fd478",
"toolchain": "rustc 1.99.1 (58cf8f9c3 2026-10-13) on Linux x86_64, target wasm32-unknown-unknown",
"build": "bash wai/wai-int-module/build.sh: release, one codegen unit, fat LTO, panic=abort, the memory's maximum 16,384 pages; the checkout, the Cargo home and the toolchain remapped to /open-standards, /cargo and /rustup"
}