Skip to main content
tempera
Request private access

Private workflows for dependable consequential AI work

Tempera brings evidence, authority, and outcome together inside a system your team can inspect. This public specimen shows the readable contract example a private workflow is designed to follow.

Explore the safe demoRequest private access
Contract record / public specimenRead-only
  1. 1

    Intent

    The stated job is visible before any operation is considered.

    Capture intenttrigger.manual
  2. 2

    Declared connector operation

    The workflow names a declared capability boundary; the sensitive edge stays outside the workflow definition.

    Declare capabilityconnector.request
  3. 3

    Bounded model proposal

    Deterministic transforms and the model’s proposal remain visible beside one another.

    Normalize deterministicallytransform.map
    Bound model proposalllm.generate
  4. 4

    Configured authority signal

    A consequential step waits for the exact signal the workspace binds to authority.

    Await authority signalcontrol.awaitSignal
  5. 5

    Typed result

    The returned value is held to a declared output shape.

    Return typed resultoutput.structured
Connection: declared operationAuthority: exact signalOutput: declared shape

The platform map

Five surfaces. One system boundary

Model policy is separate from workflow authority and connector execution. Read the model-policy boundary.

Choose your guide

What are you looking to do?

  1. Read a workflow contract recordInspect the intent, declared capability, bounded proposal, authority signal, and typed result before a private workflow is configured or run.
  2. Define a custom API boundaryModel one bounded external operation as a declared connector boundary while keeping its endpoints and credentials outside the workflow.
  3. Plan a workflow integrationUnderstand how a private integration should meet the same declared input, authority, and typed-output boundary as a saved workflow.
  4. Inspect a curated MCP capabilityRead a small catalogue of reviewed tool shapes and their grant boundary before connecting an MCP client to a private workspace.
  5. Scope workspace access and approvalsUse an audience, workspace, scope set, expiration, and revocation path to make a private grant explainable before it is issued.

What is public vs private

Inspect the system. Configure in private

Public to inspect

Documentation, method references, and public contract principles are open to review.

  1. 1nodeTypes.list
  2. 2workflows.compose
  3. 3connectors.list
Browse documentation →

Private to provision and run

Workspace configuration, connection details, credentials, signals, execution, and evidence remain private.

  • Workspace configuration
  • Connection credentials and operation settings
  • Execution inputs, results, and configured authority signals
Request private access

Tempera is in private preview. Access is provisioned to approved organizations; browsing these records creates nothing.