Expected outcome
You can tell whether the workflow makes its connection, model role, authority pause, and output shape explicit before it reaches a private workspace
You can use this public guide without a Tempera account, product credential, or private workspace. Product access begins only after private onboarding.
Before you start
- One consequential job your team wants an agent to help with
- A clear owner for the action or decision that must remain explicit
Steps
- 01
Read the stated intent
Start with the job the workflow is meant to accomplish. A useful contract names the intended outcome before it lists tools or models
- 02
Find the declared operation
Confirm that the workflow points to a named connector operation instead of embedding an endpoint or credential in the workflow definition
- 03
Separate proposal from authority
A model can propose. A proposal does not grant a consequential action; that remains behind a configured authority signal. A workspace may bind that signal to human or policy review
- 04
Check the returned shape
Read the typed result boundary. The result should be described as part of the contract, not inferred from a free-form model response
What success looks like
- The intent, declared capability, configured authority signal, and output are distinct parts of one readable record
- The public specimen does not imply a configured workspace or a completed run
- The team can name the first decision that should remain explicit during a private evaluation
If something is blocked
- If the workflow looks like a list of tools, restate the decision and the result that must hold up before adding more steps
- If authority is unclear, keep the action private and blocked until an owner names the configured authority signal and its human or policy review binding