Skip to content

Resource binding and keys

Binding connects a portable requirement to a resource available in an installation. A definition can request structured model output, a calendar read, or an approver role. The workspace supplies a compatible model, an authorized calendar account, or the person assigned to review.

A resource key gives a portable definition a stable identity across revisions. The registry resolves that identity to reviewed definition content. Binding supplies the resource to use at execution in a particular workspace.

Identify a definition across installations

Section titled “Identify a definition across installations”

A portable key is lowercase, dot-separated, and starts with the resource kind. For example, a pipeline can reference the meeting list by its key.

{
"kind": "list",
"resourceKey": "list.example.meetings"
}

The same list can have a different local record ID in each workspace. Use the portable key in definitions so they can move between installations. Resource-key rules

In the Gabriel implementation, a team resource can use a key scoped to its team. A placement identifies its playbook by playbookId and sourceFingerprint. Use the profile’s typed resource reference when a team resource refers to an inherited portable definition. Studio definitions

Requirement Workspace binding Dispatch check
A model with structured output A configured model and provider The selected model can return the required shape.
A connector operation A provider connection under the requested account context The actor has a current grant for that operation.
A reviewer role An authorized member or role assignment The reviewer can decide on this scope and proposal.
A logical output A destination list, artifact, or provider target The actor can write to that destination under local policy.

This example shows the relationship between a Studio requirement, its workspace binding, and the result. For the persisted requirement format, see connectors.

portable requirement calendar:upcoming
workspace binding authorized calendar for the acting member
runtime mapping permitted provider operation → meetings result
next step input meetings

To use a model served on hardware you manage, bind the same requirement to a local inference endpoint.

Adding a field to the meeting list can keep its resource key while changing the pinned definition. Allocate a new key for a separate definition and update its consumers explicitly. At import, report unresolved keys and mismatched kinds before activation.

Hold the affected step if an account is disconnected, an operation loses its grant, or the selected model lacks a required capability. Report the missing prerequisite so a workspace owner can repair it.

Changing an account or destination can change the effect that was reviewed. Compare the dispatch request to the recorded approval and obtain a fresh decision when its scope changes. See the proposed binding rules and approvals.