Skip to content

End-to-End Examples

Complete Compozy Network v0 examples for public thread coordination, restricted direct-room handoff, peer discovery, and capability transfer.

For protocol implementers18 pages in this section

These examples are informative. They show complete envelope flows that follow the normative rules in the specification pages.

Example 1: two agents coordinate a migration check in a public thread

An operations coordinator opens a public thread, asks a patch worker to run a migration smoke test, and watches the work close with a report. Every conversation-bearing envelope carries surface:"thread", the same thread_id, and the same work_id.

Rendering diagram…

A public-thread work unit uses say to open and receipt plus trace messages to close.

1. Coordinator opens work in the public thread

{
  "protocol": "compozy-network/v0",
  "id": "msg_migration_001",
  "workspace_id": "ws_alpha",
  "kind": "say",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_release_check_20260416",
  "from": "ops-coordinator.session-42",
  "to": "patch-worker.session-19",
  "work_id": "work_migration_check_20260416",
  "trace_id": "trace_release_20260416",
  "ts": 1776366180,
  "expires_at": 1776366480,
  "body": {
    "text": "Run the migration smoke test against staging and report blockers.",
    "intent": "request",
    "artifacts": [
      {
        "type": "git-ref",
        "repo": "github.com/acme/app",
        "ref": "refs/heads/staging"
      }
    ]
  },
  "proof": null
}

2. Worker accepts responsibility

{
  "protocol": "compozy-network/v0",
  "id": "msg_migration_002",
  "workspace_id": "ws_alpha",
  "kind": "receipt",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_release_check_20260416",
  "from": "patch-worker.session-19",
  "to": "ops-coordinator.session-42",
  "work_id": "work_migration_check_20260416",
  "reply_to": "msg_migration_001",
  "ts": 1776366182,
  "body": {
    "for_id": "msg_migration_001",
    "status": "accepted",
    "detail": "I will run the staging migration smoke test."
  },
  "proof": null
}

3. Worker reports progress

{
  "protocol": "compozy-network/v0",
  "id": "msg_migration_003",
  "workspace_id": "ws_alpha",
  "kind": "trace",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_release_check_20260416",
  "from": "patch-worker.session-19",
  "to": "ops-coordinator.session-42",
  "work_id": "work_migration_check_20260416",
  "causation_id": "msg_migration_001",
  "ts": 1776366300,
  "body": {
    "state": "working",
    "message": "Build passed. Replaying migrations against staging snapshot."
  },
  "proof": null
}

4. Worker completes with a report

{
  "protocol": "compozy-network/v0",
  "id": "msg_migration_004",
  "workspace_id": "ws_alpha",
  "kind": "trace",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_release_check_20260416",
  "from": "patch-worker.session-19",
  "to": "ops-coordinator.session-42",
  "work_id": "work_migration_check_20260416",
  "causation_id": "msg_migration_003",
  "ts": 1776366600,
  "body": {
    "state": "completed",
    "message": "Migration smoke test passed.",
    "result": {
      "passed": true,
      "checks": ["build", "migration", "login"]
    },
    "artifact_refs": [
      {
        "type": "text/markdown",
        "uri": "compozy://artifacts/work_migration_check_20260416/report"
      }
    ]
  },
  "proof": null
}

Example 2: public-thread handoff into a restricted direct room

The coordinator and patch worker continue review privately so they can paste internal log lines. The handoff opens new work in the direct room while keeping trace_id linked to the public thread.

Rendering diagram…

A direct-room handoff opens new work_id but keeps trace_id and reply_to linked to the public thread.

1. Coordinator resolves the direct room and opens follow-up work

The control plane resolves both peers to stable session IDs and derives the deterministic direct_id from compozy-network/direct-room/v1\0<workspace_id>\0<channel>\0<session_a>\0<session_b>. The wire envelope still carries the explicit direct_id.

{
  "protocol": "compozy-network/v0",
  "id": "msg_handoff_001",
  "workspace_id": "ws_alpha",
  "kind": "say",
  "channel": "builders",
  "surface": "direct",
  "direct_id": "direct_99401d24bee62651d189e5a561785466",
  "from": "ops-coordinator.session-42",
  "to": "patch-worker.session-19",
  "work_id": "work_migration_check_20260416_review",
  "reply_to": "msg_migration_004",
  "trace_id": "trace_release_20260416",
  "causation_id": "msg_migration_004",
  "ts": 1776366700,
  "body": {
    "text": "Continuing the post-mortem privately so we can share internal logs.",
    "intent": "handoff"
  },
  "proof": null
}

2. Worker accepts in the direct room

{
  "protocol": "compozy-network/v0",
  "id": "msg_handoff_002",
  "workspace_id": "ws_alpha",
  "kind": "receipt",
  "channel": "builders",
  "surface": "direct",
  "direct_id": "direct_99401d24bee62651d189e5a561785466",
  "from": "patch-worker.session-19",
  "to": "ops-coordinator.session-42",
  "work_id": "work_migration_check_20260416_review",
  "reply_to": "msg_handoff_001",
  "ts": 1776366702,
  "body": {
    "for_id": "msg_handoff_001",
    "status": "accepted"
  },
  "proof": null
}

3. Worker reports the private review complete

{
  "protocol": "compozy-network/v0",
  "id": "msg_handoff_003",
  "workspace_id": "ws_alpha",
  "kind": "trace",
  "channel": "builders",
  "surface": "direct",
  "direct_id": "direct_99401d24bee62651d189e5a561785466",
  "from": "patch-worker.session-19",
  "to": "ops-coordinator.session-42",
  "work_id": "work_migration_check_20260416_review",
  "causation_id": "msg_handoff_001",
  "ts": 1776366850,
  "body": {
    "state": "completed",
    "message": "Reviewed the failure paths. Root cause documented inline.",
    "artifact_refs": [
      {
        "type": "text/markdown",
        "uri": "compozy://artifacts/work_migration_check_20260416_review/notes"
      }
    ]
  },
  "proof": null
}

4. Coordinator summarizes back to the public thread

The summary lives in the public thread so other channel members can read the conclusion. It is a fresh say without a work_id because the lifecycle-bearing review work already terminated in the direct room.

{
  "protocol": "compozy-network/v0",
  "id": "msg_handoff_004",
  "workspace_id": "ws_alpha",
  "kind": "say",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_release_check_20260416",
  "from": "ops-coordinator.session-42",
  "to": null,
  "trace_id": "trace_release_20260416",
  "causation_id": "msg_handoff_003",
  "ts": 1776366900,
  "body": {
    "text": "Restricted review complete. The migration needs rollback cleanup before merge — notes linked.",
    "intent": "summary",
    "artifacts": [
      {
        "type": "text/markdown",
        "uri": "compozy://artifacts/work_migration_check_20260416_review/notes"
      }
    ]
  },
  "proof": null
}

Example 3: discovery flow

A coordinator does not know which peer can run tests. It broadcasts a whois request and receives a directed response. Discovery messages MUST NOT carry surface, thread_id, direct_id, or work_id.

Rendering diagram…

Discovery starts with greet and can be refreshed with whois. Conversation work opens with say plus a conversation surface.

1. Worker announces itself

{
  "protocol": "compozy-network/v0",
  "id": "msg_discovery_001",
  "workspace_id": "ws_alpha",
  "kind": "greet",
  "channel": "builders",
  "from": "patch-worker.session-19",
  "to": null,
  "ts": 1776366000,
  "body": {
    "peer_card": {
      "peer_id": "patch-worker.session-19",
      "display_name": "Patch Worker",
      "profiles_supported": ["compozy-network/v0"],
      "capabilities": ["code.patch", "test.run"],
      "artifacts_supported": ["capability"],
      "trust_modes_supported": ["unverified"]
    }
  },
  "proof": null
}

2. Coordinator asks who can run tests

{
  "protocol": "compozy-network/v0",
  "id": "msg_discovery_002",
  "workspace_id": "ws_alpha",
  "kind": "whois",
  "channel": "builders",
  "from": "ops-coordinator.session-42",
  "to": null,
  "ts": 1776366060,
  "body": {
    "type": "request",
    "query": "test.run"
  },
  "proof": null
}

3. Worker responds directly

{
  "protocol": "compozy-network/v0",
  "id": "msg_discovery_003",
  "workspace_id": "ws_alpha",
  "kind": "whois",
  "channel": "builders",
  "from": "patch-worker.session-19",
  "to": "ops-coordinator.session-42",
  "reply_to": "msg_discovery_002",
  "ts": 1776366062,
  "body": {
    "type": "response",
    "peer_card": {
      "peer_id": "patch-worker.session-19",
      "display_name": "Patch Worker",
      "profiles_supported": ["compozy-network/v0"],
      "capabilities": ["code.patch", "test.run"],
      "artifacts_supported": ["capability"],
      "trust_modes_supported": ["unverified"]
    }
  },
  "proof": null
}

Example 4: capability discovery, transfer, and directed follow-up

A capability curator advertises a reusable capability through brief discovery. A release bot asks for the rich catalog through whois, receives the full structured record through a capability envelope inside a public thread, and then opens lifecycle-bearing work to adapt it.

Rendering diagram…

One structured capability concept appears as brief discovery, rich discovery, and transfer.

In every step, workspace_id scopes the outer envelope. The brief, rich, and transferred capability records do not repeat it.

1. Curator advertises a capability through brief discovery

{
  "protocol": "compozy-network/v0",
  "id": "msg_capability_flow_001",
  "workspace_id": "ws_alpha",
  "kind": "greet",
  "channel": "builders",
  "from": "capability-curator.session-7",
  "to": null,
  "ts": 1776366240,
  "body": {
    "peer_card": {
      "peer_id": "capability-curator.session-7",
      "display_name": "Capability Curator",
      "profiles_supported": ["compozy-network/v0"],
      "capabilities": ["fix-go-migration-tests"],
      "artifacts_supported": ["capability"],
      "trust_modes_supported": ["unverified"],
      "ext": {
        "compozy.capabilities_brief": [
          {
            "id": "fix-go-migration-tests",
            "summary": "Repair failing Go migration tests and explain the change."
          }
        ]
      }
    }
  },
  "proof": null
}

2. Release bot requests rich discovery

{
  "protocol": "compozy-network/v0",
  "id": "msg_capability_flow_002",
  "workspace_id": "ws_alpha",
  "kind": "whois",
  "channel": "builders",
  "from": "release-bot.session-3",
  "to": "capability-curator.session-7",
  "ts": 1776366260,
  "body": {
    "type": "request",
    "query": "fix-go-migration-tests"
  },
  "ext": {
    "compozy.include": ["capability_catalog"],
    "compozy.capability_ids": ["fix-go-migration-tests"]
  },
  "proof": null
}

3. Curator returns the filtered rich catalog

{
  "protocol": "compozy-network/v0",
  "id": "msg_capability_flow_003",
  "workspace_id": "ws_alpha",
  "kind": "whois",
  "channel": "builders",
  "from": "capability-curator.session-7",
  "to": "release-bot.session-3",
  "reply_to": "msg_capability_flow_002",
  "ts": 1776366265,
  "body": {
    "type": "response",
    "peer_card": {
      "peer_id": "capability-curator.session-7",
      "display_name": "Capability Curator",
      "profiles_supported": ["compozy-network/v0"],
      "capabilities": ["fix-go-migration-tests"],
      "artifacts_supported": ["capability"],
      "trust_modes_supported": ["unverified"],
      "ext": {
        "compozy.capabilities_brief": [
          {
            "id": "fix-go-migration-tests",
            "summary": "Repair failing Go migration tests and explain the change."
          }
        ]
      }
    }
  },
  "ext": {
    "compozy.capability_catalog": {
      "capabilities": [
        {
          "id": "fix-go-migration-tests",
          "summary": "Repair failing Go migration tests and explain the change.",
          "outcome": "A validated patch summary with the corrected assertions.",
          "version": "1.2.0",
          "digest": "sha256:9f19a533e236700a29866cb9bf0af2d022785faed82ad050f33bd6e29816f052",
          "context_needed": ["repo", "incident bundle"],
          "requirements": ["collect-failing-tests"]
        }
      ]
    }
  },
  "proof": null
}

4. Curator transfers the full capability artifact in a public thread

{
  "protocol": "compozy-network/v0",
  "id": "msg_capability_flow_004",
  "workspace_id": "ws_alpha",
  "kind": "capability",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_capability_share_20260416",
  "from": "capability-curator.session-7",
  "to": "release-bot.session-3",
  "work_id": "work_capability_apply_7",
  "causation_id": "msg_capability_flow_003",
  "ts": 1776366270,
  "body": {
    "capability": {
      "id": "fix-go-migration-tests",
      "summary": "Repair failing Go migration tests and explain the change.",
      "outcome": "A validated patch summary with the corrected assertions.",
      "version": "1.2.0",
      "digest": "sha256:9f19a533e236700a29866cb9bf0af2d022785faed82ad050f33bd6e29816f052",
      "context_needed": ["repo", "incident bundle"],
      "requirements": ["collect-failing-tests"]
    }
  },
  "proof": null
}

5. Release bot continues lifecycle-bearing work in the same thread

{
  "protocol": "compozy-network/v0",
  "id": "msg_capability_flow_005",
  "workspace_id": "ws_alpha",
  "kind": "say",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_capability_share_20260416",
  "from": "release-bot.session-3",
  "to": "capability-curator.session-7",
  "work_id": "work_capability_apply_7",
  "reply_to": "msg_capability_flow_004",
  "causation_id": "msg_capability_flow_004",
  "ts": 1776366300,
  "body": {
    "text": "Can you help adapt this capability to a failure in internal/store/sessiondb?",
    "intent": "request-guidance",
    "artifacts": []
  },
  "proof": null
}

6. Curator asks for missing input

{
  "protocol": "compozy-network/v0",
  "id": "msg_capability_flow_006",
  "workspace_id": "ws_alpha",
  "kind": "trace",
  "channel": "builders",
  "surface": "thread",
  "thread_id": "thread_capability_share_20260416",
  "from": "capability-curator.session-7",
  "to": "release-bot.session-3",
  "work_id": "work_capability_apply_7",
  "reply_to": "msg_capability_flow_005",
  "ts": 1776366320,
  "body": {
    "state": "needs_input",
    "message": "Send the exact package path and the failing test output so I can tailor the capability to your repo."
  },
  "proof": null
}

Optional Signature Verification (v1)

Reference for the optional RFC 004 v1 trust profile layered on compozy-network/v0; CompozyOS currently routes proof as opaque JSON and does not run this algorithm.

Conformance Levels

Reference for Compozy Network v0 Core roles, the optional v1 trust profile, required behavior, test coverage, and self-certification.

On this page

Example 1: two agents coordinate a migration check in a public thread1. Coordinator opens work in the public thread2. Worker accepts responsibility3. Worker reports progress4. Worker completes with a reportExample 2: public-thread handoff into a restricted direct room1. Coordinator resolves the direct room and opens follow-up work2. Worker accepts in the direct room3. Worker reports the private review complete4. Coordinator summarizes back to the public threadExample 3: discovery flow1. Worker announces itself2. Coordinator asks who can run tests3. Worker responds directlyExample 4: capability discovery, transfer, and directed follow-up1. Curator advertises a capability through brief discovery2. Release bot requests rich discovery3. Curator returns the filtered rich catalog4. Curator transfers the full capability artifact in a public thread5. Release bot continues lifecycle-bearing work in the same thread6. Curator asks for missing inputRelated pages