Conformance

MissionWeaveProtocol 0.1 provides 56 implementation-neutral conformance cases:

Expected result	Cases	Canonical directory
Valid	26	conformance/vectors/valid/
Invalid	30	conformance/vectors/invalid/

The canonical manifest.json maps every case to one schema, one instance document, and its expected validity. See the conformance README for the normative usage requirements.

What the vectors prove

Running all 56 cases checks that an implementation agrees with the protocol’s structural document rules. The invalid cases cover deliberately rejected shapes, such as missing signatures, invalid lifecycle states, absent ownership, unsafe extension behavior, and inconsistent provenance.

Passing the manifest is necessary but not sufficient. Behavioral conformance also requires the state-machine, ordering, authorization, signature, epoch, lease, budget, hierarchy, timestamp, and replay rules in the normative specification.

Signed-document cryptography is a separate conformance surface. Its cryptography manifest contains 22 cases and 58 evaluations across all nine signature-required schema profiles. The cryptography README defines the ordered six-stage verification requirements. Passing either manifest does not imply passing the other.

Validate in the protocol checkout

python -m pip install -r requirements-validation.txt
python scripts/check_repository_policy.py
python scripts/validate_protocol.py

Run with the Python SDK

With sibling source checkouts named missionweaveprotocol and python-sdk, run this from the protocol checkout:

uv run --project ../python-sdk missionweaveprotocol-conformance --root .

Or run this from the Python SDK checkout:

uv run missionweaveprotocol-conformance --root ../missionweaveprotocol

The Python SDK also vendors the same schema and vector bundle for offline validation. Its PROTOCOL_PIN.json records the exact protocol commit and content digests used by that checkout.