docs(contract): hosted participants get their own group, not the pit

Merged
KH
3d ago
+37-8

Corrects the example I added in #45. It put hosted participants (ChatGPT, Cursor cloud agents, generic MCP) in gid 22 and said they "never read local". In examples/policy.pit.json the pit is the inside group, and it reads relaycast:channel/ and relaycast:inbox/local-. A reviewer on agentrelay.com#326 caught the same mistake in the operator page.

This PR replaces the example with a dedicated hosted group:

  • a never: [22] ceiling;
  • its own relaycast:inbox/cursor-cloud- prefix, which local agents may write;
  • write-only access to relaycast:inbox/local-.

I checked the documented results with relaygate-explain against examples/policy.pit.json plus these entries:

  • allowed: a hosted participant writing a local inbox; local writing a hosted participant's inbox;
  • refused: a hosted participant reading a local inbox, a local channel, any pit stream or slack:.

Docs only.

๐Ÿค– Generated with Claude Code


Autofix with [code]smith
Open in [code]smith ยท Need help on this PR? Tag @codesmith-bot with what you need.


Summary by cubic

Fixes the docs example for hosted participants so they get a dedicated hosted group instead of the pit group, matching what examples/policy.pit.json actually defines.

The old example placed hosted participants (ChatGPT, Cursor cloud agents, generic MCP) in gid 22 and claimed they never read local, but the pit is the inside group that reads relaycast:channel/ and relaycast:inbox/local-. The replacement gives hosted participants their own group with a pit ceiling (never: [22]), write-only access to local inboxes, and a cursor-cloud- inbox prefix local agents may write to. inboxDefaults entries cover hosted participants without that prefix (ChatGPT, MCP) and desktop-enrolled local agents, granting both directions of DM. The results were verified with relaygate-explain. Docs only.