Skip to content

Rust SDK

missionweaveprotocol is the official Rust crate. This reference describes exact commit 2727f8777737265d98dde4ceaca306612ef54c52, crate version 0.1.0, Rust 1.85 or newer, and edition 2024. The documented pin is not published on crates.io; a different Git revision or package archive is a different implementation input.

The missionweaveprotocol-conformance binary accepts optional --verbose. It runs the embedded structural Schema vectors; it does not establish Registry currency, Admission Log durability, network security, or production readiness.

Normative evidenceCoverageDigest binding
Structural vectors58 total (27 valid / 31 invalid)Bound by the exact protocol bundle digest
Cryptography bundle62 evaluations (12 complete / 50 rejected)sha256:5eade516e4bc5dcf04477727ebcccd11f33348b2d9135fb6fe0365c6e6cc2ea3
Admission bundle30 evaluations (12 complete / 18 rejected)sha256:39971bfafb68ef6c18f9026220cccc4f023fd4d5c8074f8ff0276cb1129cd0a0

Rust

Package
missionweaveprotocol
Required toolchain
Rust 1.85 · Cargo
Admission operations
prepare_first_admission · admit_first · verify_historical_admission
Runtime capabilityStatusEvidence or boundary
Strict JSON and Draft 2020-12 Schema validationImplemented
RFC 8785 canonical JSONImplemented
Signed Document signing and six-stage verificationImplemented
Registry-backed signing-key resolutionImplemented
WebSocket frame codecImplemented
Structural and cryptographic conformance runnerImplemented
Protocol bundlesImplemented
First Admission and Historical TrustImplemented
Admission authority adaptersDeployment adapter required

Deployments provide the current-Registry resolver, authoritative Admission Log, and trusted-context issuer.

Mission orchestrationNot implementedNo high-level Mission orchestration runtime is exported at the pinned commit.
Worker schedulingNot implementedNo Worker scheduling runtime is exported at the pinned commit.
Gateway serviceNot implementedThe SDK provides frame codecs, not a hosted gateway service.
Persistence runtimeNot implementedNo authoritative or Agent-local persistence runtime is exported at the pinned commit.

The crate supplies in-process protocol behavior, not deployment authority. Applications still provide authenticated current and historical Registry evidence, trusted Admission context, and an authoritative append-only Admission Log.