Testing Your Implementation

Keep core protocol tests independent from your carrier. A receiver should reject malformed content before opening runtime work or applying extension behavior.

Fixture layers

Minimal fixture example

func TestCoreSenderFixture(t *testing.T) {
	raw := []byte(`{
		"protocol":"compozy-network/v0",
		"id":"msg_fixture_01",
		"workspace_id":"ws_alpha",
		"kind":"say",
		"channel":"builders",
		"surface":"thread",
		"thread_id":"thread_fixture_01",
		"from":"sender.demo",
		"to":null,
		"ts":1775606300,
		"body":{"text":"fixture hello"},
		"proof":null
	}`)

	var env Envelope
	if err := json.Unmarshal(raw, &env); err != nil {
		t.Fatalf("decode envelope: %v", err)
	}
	if env.Protocol != "compozy-network/v0" {
		t.Fatalf("protocol = %q", env.Protocol)
	}
	if env.Surface != "thread" || env.ThreadID == "" {
		t.Fatal("thread say requires surface=thread and thread_id")
	}
}

Add a carrier integration test only after fixtures pass. A carrier acknowledgement proves carrier handling; it does not prove protocol acceptance, trust, or completed work.

CompozyOS reference evidence

Inside the Compozy repository, scoped package tests exercise the reference implementation:

go test -race ./internal/network/...

Those tests are not a standalone third-party conformance runner. Publish your implementation version, claimed role, test-corpus revision, carrier test commands, covered groups, and known gaps.

When claiming Trust, create and publish your own versioned vectors using the Ed25519 + JCS requirements. CompozyOS does not currently ship trust vectors or a trust runner. A Core claim does not require the optional profile.