Build a MissionWeaveProtocol 0.1 runtime

Build a MissionWeaveProtocol 0.1 runtime

Draft Standard 0.1

This versioned Build path is part of the normative website publication. It organizes the local Reference clauses into implementation order without redefining them. When a summary and a linked clause differ, the linked clause is the controlling requirement.

The BCP 14 requirement language used by the local specification is defined in MWP-FND-001. The shared path describes semantics that every language implementation must preserve. SDK-specific pages may add installation commands, language types, and public API syntax, but they must not weaken or replace these rules.

Implementation note

Recommended implementation sequence

1. Bootstrap an exact release, trust boundary, validators, stores, and runtime identity.
2. Preserve protocol JSON, identifiers, timestamps, hashes, and envelope types without host-language normalization.
3. Implement strict parsing, Schema validation, canonicalization, signing, Registry-backed key resolution, and the six-stage verification pipeline.
4. Layer First Admission and Historical Trust above cryptographic verification.
5. Separate authoritative state from rebuildable projections, then implement replay, idempotency, fencing, and side-effect recovery.
6. Authenticate and multiplex Groups over the normative WebSocket framing.
7. Expose stable wire errors while retaining protected diagnostics and useful operational signals.
8. Verify exact release artifacts, report the proven conformance subset, and upgrade without silently changing wire semantics.

This order is implementation guidance. The linked Reference clauses define the requirements and their acceptance boundaries.

Shared runtime reference

Architecture and bootstrapTrust boundaries, runtime responsibilities, release loading, identity, recovery, and startup order.

Protocol typesWire JSON, scalar profiles, durable objects, envelopes, generated types, and semantic state.

Validation, canonicalization, and signingStrict parsing, Schema assertions, JCS, Ed25519, Registry evidence, and signing hashes.

First Admission and Historical TrustTyped Admission Log outcomes, atomic first admission, record validation, and historical replay.

Persistence and recoveryAuthoritative state, local projections, receipts, replay, Cursors, snapshots, and side effects.

Transport and framingHELLO authentication, Session Epoch fencing, subscriptions, multiplexing, ACK, PING, and backpressure.

Errors and observabilityWire-safe errors, retry decisions, protected diagnostics, audit records, metrics, and tracing boundaries.

Conformance and upgradesExact artifacts, structural and trust bundles, claim boundaries, extensions, and version transitions.

Release before code

Start from the local normative release identity, not an unpinned repository branch or SDK README. The release page binds the protocol artifacts, all six SDK commits, profiles, digests, locales, and exact built-site identity used by this documentation.