Private access · private API boundary
Connect bounded APIs with declared boundaries
Review a custom API boundary before private provisioning. A workflow refers to a declared capability; connection identity, endpoints, and secrets stay out of the workflow definition.
Public contract example
A connector is not a secret pasted into a workflow
Tempera keeps the operation definition, credential reference, and any repair proposal as separate records so a failure does not silently alter an integration.
Declared capability
Custom API, made legible
- Declared operationWhat the workflow is allowed to ask for
- Private connectionTransport and credentials remain outside the workflow
- Governed effectPolicy keeps the next consequential step explicit
- Typed boundaryThe workflow receives only the declared result shape
- Workflow sees
- Declared capability
- Connector keeps
- Connection, transport, credentials
- If an API changes
- Classify first; propose a reviewable repair
What this surface owns
The public record shows the contract a buyer can inspect. Configuration, credentials, and effectful actions remain inside a provisioned workspace.
- 01Private configuration
Bounded custom API
Define one bounded operation for a private workspace integration.
Read connections · Manage connections
- 02Private configuration
Credential reference
Keep a credential reference out of workflow definitions and model context.
Manage connections
- 03Private policy
Recovery proposal
Classify a failed operation and surface a bounded recovery or repair proposal for workspace review.
Read connections