Core developers
Organization controls
An organization can define shared membership, role descriptions and team configuration. The destination Core still decides whether a particular operator may run a particular agent in a workspace.
Follow a team from catalog to execution
- An organization owner or admin publishes the reviewed role or team configuration through the configured backend. Operators select an available catalog version in a compatible client.
- The Host resolves the selected workspace, members, provider profile and local execution scope. The operator reviews the actual roster, startup instructions and permitted message recipients.
- Core reserves local capacity and records the original operation as it admits the reviewed effect. Starting a thread, submitting a model turn and accepting a task report have distinct effects and receipts.
A role description is an instruction to an agent. A changed description, membership record or team selection cannot establish a live provider session or inherit an earlier execution approval.
Read a published catalog
On a configured backend the authenticated native GET /v1/organization-catalogs route returns eligible organizations with their role, catalog revision and hash. A client can request GET /v1/organization-catalogs/{organizationID} for one current publication. The backend checks the native audience and current membership. For the CLI it also checks current device enrollment. The response includes provenance that identifies the published revision. The selected Host still needs a fresh local review before execution.
Decide who can observe
On deployments where organization observability is enabled, review the organization's export policy, the host's reporting identity and the exact workspace enrollment. Owners and admins can manage policy. Reading another member's workspace activity requires the corresponding reader permission. The host also needs current consent to export its supported metadata.
Withdraw access
Revoke the specific membership, workspace reader or export grant being retired. Historical evidence keeps its original identities. Ending a running workload requires the destination's separately authorized control operation. Approvals and control · Observation scope