Sharing content-free strategy evidence over Agent Mesh

Share the observation needed for coordination

The V4 strategy reference describes content-free outcome attestations. It excludes prompts, reasoning, credentials, source code and private mission content from that exchange.

For an illustrative peer comparison, the useful record may describe the bounded outcome of a strategy without carrying the underlying customer document. Keep the attestation schema tied to its coordination purpose rather than using it as a convenient general message channel.

A signature does not establish local applicability

The receiving peer rechecks catalog compatibility, membership, signature, Trust, diversity and governance. Those checks distinguish an attributable remote statement from evidence the local deployment may actually use.

A strategy observation from another configuration may be authentic while remaining unsuitable for the local candidate catalog. Preserve that distinction in diagnostics. A rejected attestation need not mean that the sender lied; it may mean the local policy cannot admit it for this decision.

Use causal exchange without transferring authority

The Rooms and Mesh integration describes the authority-neutral projection boundary and signed strategy outcome exchange. Each receiving peer reapplies its own scope and governance rules.

The synchronization layer supplies required state visibility and catch-up context. A peer learning about an outcome does not thereby acquire approval to install that strategy.

Keep aggregate advice distinguishable from a decision

V4's bounded priors and convergence results remain advisory. An application can use them as evidence for a local proposal while retaining the separate decision and execution boundaries.

In an illustrative operator interface, show the contributing attestation references and the local recommendation separately from any approved change. A remote peer's positive experience should not appear as an already-authorized local update.

Inspect payloads as well as decisions

• Verify that attestations contain only the permitted bounded fields.
• Reject payloads that attempt to include raw private content.
• Exercise stale membership or incompatible catalog cases.
• Inspect the receiving peer's local policy result.
• Confirm that advisory convergence cannot directly activate a strategy.

These suggested checks examine both the evidence boundary and the authority boundary. They do not imply that every possible metadata disclosure has been eliminated; your deployment still chooses appropriate identifiers, access and retention.