TypeScript SDK

@missionweaveprotocol/sdk is the official TypeScript implementation package. This reference describes exact commit 6d53ebfcf8350ae81d89fd818611b07f7373685c, package version 0.1.0, and Node.js 20 or newer. A different commit or package build is a different documented implementation input, even when its version string is unchanged.

Install

Package identity: @missionweaveprotocol/sdk
Required toolchain: Node.js 20 · npm
Documented commit: 6d53ebfcf8350ae81d89fd818611b07f7373685c

git clone https://github.com/MissionWeaveProtocol/typescript-sdk.git missionweaveprotocol-typescript-sdk
cd missionweaveprotocol-typescript-sdk
git checkout --detach 6d53ebfcf8350ae81d89fd818611b07f7373685c
npm ci
npm run build
npm pack --pack-destination ..
cd ..
npm install ./missionweaveprotocol-sdk-0.1.0.tgz

Verify the installed package

          node -e 'import("@missionweaveprotocol/sdk").then(({ sdkMetadata }) => console.log(sdkMetadata()))'
npx --no-install missionweaveprotocol-conformance --json

The package root supplies both ESM and CommonJS builds. Only the package root and package.json are supported exports; internal source-file paths are not public subpath APIs. The pinned source package does not build dist/ during a direct Git dependency install, so the documented flow builds and installs a tarball explicitly. Another tarball may replace it only when its provenance is bound to the same exact commit.

The installed missionweaveprotocol-conformance command runs the packaged Schema and vector surfaces. It does not establish deployment authority, Admission Log durability, network security, or production readiness.

Use this reference

Complete runtimeEvery supported package-root module, Node runtime boundary, conformance entry point, and explicit non-implementation.

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

Exact public APIEvery public package-root 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`

TypeScript

Package: @missionweaveprotocol/sdk
Required toolchain: Node.js 20 · npm
Exact SDK commit: 6d53ebfcf8350ae81d89fd818611b07f7373685c
Admission operations: prepareFirstAdmission · admitFirst · verifyHistoricalAdmission

Runtime capability	Status	Evidence or boundary
Strict JSON and Draft 2020-12 Schema validation	Implemented	`src/strict-json.ts` `src/schema-catalog.ts`
RFC 8785 canonical JSON	Implemented	`src/canonical-json.ts`
Signed Document signing and six-stage verification	Implemented	`src/signed-document-codec.ts` `src/crypto.ts` `src/ed25519-strict.ts`
Registry-backed signing-key resolution	Implemented	`src/signed-document-codec.ts`
WebSocket frame codec	Implemented	`src/frame-codec.ts`
Structural and cryptographic conformance runner	Implemented	`src/conformance.ts` `src/bin/conformance.ts`
Protocol bundles	Implemented	`src/package-root.ts` `src/schema-catalog.ts`
First Admission and Historical Trust	Implemented	`src/admission.ts`
Admission authority adapters	Deployment adapter required	`src/admission.ts` 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 matrix distinguishes in-process implementation from deployment-owned authority. Installing the package does not supply a current Registry service, an authenticated atomic Admission Log, a hosted gateway, or durable runtime persistence.