Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions 6
open-standards/wai/haptic-conformance
History
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science 3fac029a71 wai: every corpus states the provenance of its content 
Each *-conformance/README.md now has a line that begins **Provenance.**:
the generator that writes the corpus and its input, and for an input not
generated here its source and licence. OER/2's corpus is settled and left
as it is. byte-exact-conformance and quantum-ops-conformance get a README.
wai-rs/tests/vectors/README.md gives a row per vector directory. Where the
staged-delivery, staged-measurement and telemetry READMEs called their
content "synthetic", that sentence is now their provenance line.

Two vectors are recorded as not generated, from the provenance audit:
int_video's video_real (a pan over a third-party picture) and
neural-conformance's photo (a third-party picture, with a decoder trained on
unrecorded images). Their lines say so and that they are to be replaced;
the photo bullet no longer names the picture's source product.

tests/corpus_provenance.rs requires the line in every corpus and a row for
every vector directory; CI runs it with the carriage tests. CONTRIBUTING
states the rule: corpus content is generated here, or recorded with a
licence that permits redistribution, and a word like "synthetic" is not a
provenance line.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-07 10:09:21 -04:00
..
vectors wai: interactive + temporal cargo classes, provenance, telepresence 2026-06-13 23:16:42 -04:00
expected_hashes.json wai: interactive + temporal cargo classes, provenance, telepresence 2026-06-13 23:16:42 -04:00
README.md wai: every corpus states the provenance of its content 2026-10-07 10:09:21 -04:00

README.md

Haptics Conformance Corpus

Vectors for the haptics extension's sample-equivalence criterion: given the same wai.haptic.signal, a conforming sink MUST reconstruct the identical canonical u8 buffer (per-channel interleaved [intensity, sharpness]), hence the identical BLAKE3 — on every machine, no tolerance parameter. The touch counterpart of replay/mixdown-equivalence, with the tick replaced by the haptic sample.

Provenance. Generated here: wai_haptic_vectors gen writes every vector from envelopes authored in code. No recording.

All vectors reconstruct in the wai.det.fixed64 floor (Fx linear interpolation of the keyframed envelope → u8). Signals are self-contained (no external sources), so each vector is just a .whap file + its expected signal_hash.

Layout

  • vectors/<name>.whap — the WHAP container (contract + channel signals).
  • expected_hashes.json — per signal: channels and signal_hash.

Vectors:

  • ramp — intensity 0→1 over the duration.
  • thud — full sharp hit, decaying.
  • dual_pulse — two channels (dual-rumble): a strong pulse + a soft steady channel.

Running

cd ../wai-rs
cargo run --features haptic --bin wai_haptic_vectors -- verify ../haptic-conformance
cargo run --features haptic --bin wai_haptic_vectors -- gen    ../haptic-conformance   # regenerate

Pass = hash equality.