Skip to main content

​
AI Policy Builder

AI Policy Builder is optional. Direct selection, manual policies, custom orchestrators, SDKs, MCP, and DreamLayer Agent API work without it.

​
What this lets you do

Draft a deterministic local orchestration policy, inspect it, and activate only the reviewed revision.

​
What you need

  • A visible local connector and workflow catalog
  • Request fixtures for dry runs
  • A reviewer who can approve the exact generated revision

​
Steps

  1. Draft against the user’s visible connector and workflow catalog.
  2. Validate the closed deterministic policy shape.
  3. Dry-run required request fixtures.
  4. Review the trace and coverage.
  5. Activate the exact reviewed revision explicitly.
AI is used during authoring only. Runtime evaluation of an active policy is deterministic.

​
Confirm it worked

The active revision digest matches the reviewed draft, required fixtures pass, and runtime evaluation produces the same result for the same closed input.

​
Common errors

A policy cannot activate with invalid fields, missing dry-run coverage, unsupported catalog references, a revision digest mismatch, or catalog drift. A later edit creates a new draft and never mutates the active revision silently. Policy Builder does not contain DreamLayer’s private managed selection policy.

​
Troubleshooting

Refresh the configured catalog, rerun every required fixture, and review the new revision digest. Do not bypass a failed activation check.

​
Next steps