C++ SDK

MissionWeaveProtocol::sdk is the installed CMake target for the official C++ SDK. This reference describes exact commit 481b0ce3a65c1f2265935318b54481ece5032fdf, version 0.1.0, C++20, CMake 3.24 or newer, OpenSSL 3, and jsoncons 1.8.1. A different source revision or installed prefix is a different implementation input.

Install

Package identity: MissionWeaveProtocol::sdk
Required toolchain: C++20 · CMake 3.24 · OpenSSL 3
Documented commit: 481b0ce3a65c1f2265935318b54481ece5032fdf

git clone https://github.com/MissionWeaveProtocol/cpp-sdk.git missionweaveprotocol-cpp-sdk
cd missionweaveprotocol-cpp-sdk
git checkout --detach 481b0ce3a65c1f2265935318b54481ece5032fdf
cmake -S . -B build -DMISSIONWEAVEPROTOCOL_BUILD_TESTS=ON -DMISSIONWEAVEPROTOCOL_BUILD_EXAMPLES=ON
cmake --build build --parallel 2
ctest --test-dir build --output-on-failure
cmake --install build --prefix /absolute/install/prefix

Verify the installed package

          /absolute/install/prefix/bin/missionweaveprotocol-conformance

Configure with OPENSSL_ROOT_DIR when CMake would otherwise find a non-OpenSSL or pre-3.0 implementation. The build first searches for jsoncons 1.8.1 and otherwise downloads the exact v1.8.1 archive with a pinned SHA-256. Downstream CMake projects configure find_package(missionweaveprotocol CONFIG), fail their own build when the package is absent, and link MissionWeaveProtocol::sdk.

The installed missionweaveprotocol-conformance executable runs the embedded structural Schema vectors. It accepts no documented options and does not establish Registry currency, Admission Log durability, network security, or production readiness.

Use this reference

Complete runtimeEvery installed header concern, codec, bundle verifier, executable boundary, and explicit non-implementation.

First Admission and Historical TrustTyped current-Registry, trusted-context, and Admission Log interfaces with one runnable example.

Exact public APIEvery installed-header declaration resolved to its exact source line.

Support at the documented commit

Normative evidence	Coverage	Digest binding
Structural vectors	58 total (27 valid / 31 invalid)	`Bound by the exact protocol bundle digest`
Cryptography bundle	62 evaluations (12 complete / 50 rejected)	`sha256:5eade516e4bc5dcf04477727ebcccd11f33348b2d9135fb6fe0365c6e6cc2ea3`
Admission bundle	30 evaluations (12 complete / 18 rejected)	`sha256:39971bfafb68ef6c18f9026220cccc4f023fd4d5c8074f8ff0276cb1129cd0a0`

C++

Package: MissionWeaveProtocol::sdk
Required toolchain: C++20 · CMake 3.24 · OpenSSL 3
Exact SDK commit: 481b0ce3a65c1f2265935318b54481ece5032fdf
Admission operations: prepare_first_admission · admit_first · verify_historical_admission

Runtime capability	Status	Evidence or boundary
Strict JSON and Draft 2020-12 Schema validation	Implemented	`src/json.cpp` `src/schema.cpp`
RFC 8785 canonical JSON	Implemented	`src/canonical.cpp`
Signed Document signing and six-stage verification	Implemented	`src/signed_document.cpp` `src/crypto.cpp`
Registry-backed signing-key resolution	Implemented	`src/agent_registry_key_resolution.cpp`
WebSocket frame codec	Implemented	`src/frame.cpp`
Structural and cryptographic conformance runner	Implemented	`src/conformance.cpp` `src/conformance_main.cpp`
Protocol bundles	Implemented	`src/bundle.cpp`
First Admission and Historical Trust	Implemented	`include/missionweaveprotocol/admission.hpp` `src/admission.cpp`
Admission authority adapters	Deployment adapter required	`include/missionweaveprotocol/admission.hpp` Deployments provide the current-Registry resolver, authoritative Admission Log, and trusted-context issuer.
Mission orchestration	Not implemented	No high-level Mission orchestration runtime is exported at the pinned commit.
Worker scheduling	Not implemented	No Worker scheduling runtime is exported at the pinned commit.
Gateway service	Not implemented	The SDK provides frame codecs, not a hosted gateway service.
Persistence runtime	Not implemented	No authoritative or Agent-local persistence runtime is exported at the pinned commit.

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