WIA-RUST-LEARN-PRIMER: Rust Learn — Reference Simulator

Overview

The Rust Learn — Reference Simulator standard (WIA-RUST-LEARN-PRIMER) documents the WIA Standards canonical envelope shape, API surface, protocol exchanges, and ecosystem integration for rust learn hosts that need to interoperate across jurisdictions, vendors, and operational contexts.

The standard composes with the wider WIA Standards family to inherit cross-standard composition, audit transport (W3C Trace Context plus OpenTelemetry semantic conventions), and federation handshakes (per WIA-INTENT) without per-standard re-implementation.

Phase organisation

spec/PHASE-1.md — Phase 1 wire-format envelopes
spec/PHASE-2.md — Phase 2 REST + JSON-RPC surface
spec/PHASE-3.md — Phase 3 protocol exchanges and federation
spec/PHASE-4.md — Phase 4 ecosystem composition and compliance

Normative references

Rust Reference (rust-lang.github.io/reference)
Rust Edition 2024
ISO/IEC 9899:2018 (C standard for FFI alignment)
Cargo Book (doc.rust-lang.org/cargo)
Rustlings Exercise Pack 5.6
Rust by Example
The Rust Programming Language Book 3rd Edition (Klabnik + Nichols 2023)
Rust Reference Library
IEEE 754-2019 (Floating-point arithmetic)

Companion artefacts

README.md — scope, normative references, governance
cli/rust-learn.sh — POSIX shell helper with sample envelope generators
eBook EN — 8 chapters
eBook KO — 8 chapters
Reference simulator
Press kit

Conformance

A standard is conformant when (1) every Phase 1 envelope it emits validates against the published JSON Schema for that envelope class, (2) every Phase 2 endpoint it exposes honours the documented status codes, content shapes, and error envelopes, (3) every Phase 3 protocol exchange it participates in honours the handshake order, signature requirements, and audit hook contract, and (4) Phase 4 ecosystem composition reaches the required cross-standard capabilities (audit transport, identity, federation) per the Phase 4 Sec 4 capability matrix.

Capabilities discovery and SemVer

Hosts SHOULD publish a capabilities document at /.well-known/wia-rust-learn-capabilities enumerating per-endpoint optionality. Clients MUST treat unsupported capabilities as absent rather than as an error. Hosts moving from one minor version to the next MUST publish the change in release notes with the per-capability migration window per IETF RFC 8594 + RFC 9745. Conformance to this standard requires that all Phase 1 envelopes validate against the published JSON Schema and that all Phase 2 endpoints honour the documented status codes and content shapes.

Governance

Maintained under the WIA Standards public-benefit governance model. See https://wiastandards.com/governance/ for committee composition, voting rules, and the per-standard release calendar.

Implementation timeline (typical)

A first implementation of the Rust Learn standard simulator typically follows: stand up the WebAssembly playground bundling rustc + wasm-pack; load the curriculum from the Phase 1 envelope JSON; render per-chapter exercises via the Web Speech API for voice-guided onboarding; instrument xAPI 2.0 statements per learner attempt; submit completion to the LRS configured per the Phase 4 ecosystem composition matrix.

Cross-standard composition recap

The Rust Learn simulator composes with WIA-OMNI-API for learner identity, WIA-AIR-SHIELD for runtime trust list verification of curriculum bundles, and the cross-standard audit transport for capturing per-attempt outcomes. The simulator itself follows the WIA Standards canonical Phase 1 envelope shape so that learner progress can be exchanged with the platform LRS via the Phase 2 REST API.

Backwards-compatibility envelope

Within the 1.x line, every Phase 1 envelope shape and every Phase 2 endpoint MUST remain reachable. The simulator MAY add optional capabilities (additional exercise types, additional language packs) but MUST NOT break existing curriculum bundles. Breaking changes ride a major version bump with a 12-month deprecation window per IETF RFC 8594 and 9745.