Hmbown Planar Binding
Bind an external service, API, or agent to a contract with defined scope, duration, and failure modes.
Overview
Planar Binding is interpreted here as a hybrid spell with a prototype execution model.
Canonical source: Planar Binding (spell)
Provider target: OpenClaw
When To Use
- You are integrating an external API or service and need to define the contract before granting access.
- An external agent or model needs to be constrained to a specific role, scope, and duration within your workflow.
- You want explicit failure modes, cost limits, and termination conditions before binding a dependency.
Workflow
- Name the external entity to bind and the service it will perform.
- Define the binding contract: scope of access, duration, rate limits, cost ceiling, and failure behavior.
- Establish the termination conditions - when and how the binding ends.
- Execute the binding with the user's explicit consent and credentials, then confirm the contract is active.
Deliverables
- A binding contract specifying scope, duration, cost limits, and failure modes.
- A confirmation that the external entity is active and operating within bounds.
- A termination procedure for releasing the binding cleanly.
Guardrails
- Never bind to an external service without the user's explicit consent and credentials.
- Make cost and rate-limit implications explicit before executing any binding.
- Include termination conditions in every binding - no open-ended commitments.
Default Invocation
Use $planar-binding to integrate this external service with an explicit contract covering scope, cost, duration, and termination.