Connecting Agent Rooms to Agent Mesh with explicit projections

A projection translates a record between domains

A human-governed Room and a peer collective represent related work through different contracts. The bridge helps describe that work across the boundary without making one domain's metadata authoritative in the other.

The Rooms and Mesh reference documents objective and task projections supplied by @agentplat/rooms-mesh. A projection expresses coordination data. It is not a scheduler, admission decision or trust service.

Unsigned output requires an application-owned next step

The documentation shows projectRoomToMeshObjective and projectRoomTaskToMeshWork. Their output is unsigned. The adopting host owns signing, publication, bidding, acceptance and execution.

That separation is useful in a code review. Trace the projected object from its creation to every later side effect. Identify which application component is authorized to issue or publish it and which policy it consults. Do not let a convenient serialization step become an implicit grant of authority.

Example: distribute research for a reviewed proposal

In an illustrative workflow, a Room holds an internal proposal and its review history. The host projects a bounded research task into Mesh coordination data. Authorized application steps then publish the work and establish the appropriate assignment.

When an accepted result returns, the host projects it into an ordinary Room message or draft artifact. The reviewer can inspect that evidence alongside the proposal. The result does not automatically approve the proposal, complete every task or authorize delivery to an external customer.

Keep roles and permissions within their owners

A Room participant role does not silently become Mesh membership, admission or a lease. Similarly, a Mesh result is not a human approval. The authority documentation explains why coordination certification remains separate from external effects.

For your integration, write down the policy checks on each direction of the bridge. The outbound path should identify the exact work and scope; the inbound path should identify the accepted result and the allowed Room operation. Verify duplicate application does not create a second logical result.

Inspect the seam before scaling the collective

• Project one Room task and inspect the unsigned output.
• Verify that projection alone starts no peer execution.
• Apply only a result admitted by your configured process.
• Repeat result delivery and check idempotent Room handling.
• Confirm that returned drafts still require the intended review.

The Morphogenesis integration reference applies the same separation to organizational records. Start with one explicit bridge operation before composing more advanced control surfaces.