ConvOpsConvOps
Policies

Reusable rules, injected exactly when the step runs.

Policies let you enforce behavioral rules across workflows without editing template YAML. Create a rule once, assign it globally or to a specific template, and ConvOps injects it into the current step at read time.

Start with ConvOps See how it works
Policies

Active rules on this step

Injected at runtime
cite-task-id

Always cite the task ID in every status update.

Global
reproduce-before-fixing

Reproduce the bug before proposing a fix.

Development template
link-sources

Every claim must include a source link.

Research template
Global

Rules that apply across every workflow in the org.

Template

Rules assigned only to one workflow template.

Current step

Injected into the active step exactly when it runs.

2
Assignment scopes: global or template
1
Edit point for a shared rule
0
Template rewrites needed for policy updates
Create once, assign many

Write the rule once. Reuse it everywhere it matters.

A policy is a standalone governance rule like "always cite the task ID" or "reproduce before fixing." Once created, you can attach it to every workflow that needs the rule instead of copy-pasting the same instruction into template after template.

  • One policy can be attached to many workflows.
  • Edit the policy once and every assigned workflow inherits the change.
  • Behavioral rules stop fragmenting across duplicated templates.
Global or template-scoped

Set rules for the whole org, or only where that workflow needs them.

Some rules belong everywhere. Others only belong on one kind of work. Policies support both modes: assign globally to affect every workflow in the org, or assign to a single template when the rule is specific to that process.

  • Global assignments apply across every workflow in the org.
  • Template-scoped assignments target one workflow without touching the rest.
  • Teams can layer broad standards with workflow-specific guidance.
Composition, not mutation

Policies are injected into the current step response when the workflow is read.

ConvOps does not rewrite your workflow template to apply a policy. The engine composes active policies into the current step at read time, so the AI receives the rule exactly at the moment that step runs.

  • Policies appear in the active step response, not in a monolithic master prompt.
  • Template YAML stays clean — policy logic lives outside the template.
  • Step-level injection keeps guidance fresh when the AI needs it.
Policies

Active rules on this step

Injected at runtime
cite-task-id

Always cite the task ID in every status update.

Global
reproduce-before-fixing

Reproduce the bug before proposing a fix.

Development template
link-sources

Every claim must include a source link.

Research template
Global

Rules that apply across every workflow in the org.

Template

Rules assigned only to one workflow template.

Current step

Injected into the active step exactly when it runs.

Safer change management

Tighten a rule without editing every workflow by hand.

When compliance, engineering, or operations wants to update a rule, they update the policy text once. ConvOps propagates that change to every assigned workflow automatically on the next read.

  • No template hunt across dozens of workflows.
  • No drift between slightly different copies of the same rule.
  • Disable a policy without deleting the workflows that use it.
Sales Proposal
Playbook Definition
1Collect Requirements
2Draft Proposal
3Manager Review
4Client Delivery
4 steps defined
Active Conversations
Using this playbook
Policies + gates

Policies tell the AI how to behave. Gates decide when it must stop.

Governance and policies are related, but they do different jobs. Gates are structural checkpoints the engine enforces. Policies are reusable behavioral instructions injected into the step. Together they give you both control of flow and control of conduct.

  • Gates block movement until conditions are met.
  • Policies shape behavior inside the active step.
  • Use both when you need process control and execution standards.
A cleaner workflow surface

Keep templates focused on the process, not every recurring instruction.

Workflow templates should describe the path of the work. Policies remove repeated governance text from those templates and keep recurring standards in one reusable layer.

  • Templates stay readable because recurring policy text moves out.
  • Behavioral standards become reusable product primitives.
  • The workflow stays about the process. Policies stay about the rules.
See it in motion

See policy-driven execution

Watch a workflow progress with reusable behavioral rules attached to the active step. The AI gets the rule when it needs it, not buried in a giant prompt.

1
2
3
4
5
6
Claude
Watch the workflow in action
0 / 6

Duplicated instructions in templates vs reusable policies

Without policies

  • The same instruction gets copied into workflow after workflow.
  • Updating a rule means editing templates one by one.
  • Slight wording drift creates inconsistent behavior.
  • Recurring governance text clutters the workflow definition.

With policies

  • Create a rule once and assign it where it belongs.
  • Update the policy once; every assigned workflow gets the change.
  • Behavior stays consistent because the rule has one source of truth.
  • Templates stay focused on process while policies handle reusable standards.
Questions

Frequently asked questions

Gates control whether the workflow can advance. Policies control how the AI behaves inside the active step. Gates are structural stops. Policies are reusable instructions injected into the step response.

No. Policies are composed into the current step at read time. The template YAML stays unchanged, which keeps the workflow definition clean and reduces drift.

Yes. Assign a policy globally and it will apply across the organization. If the rule only belongs on one process, assign it to a single template instead.

Reusable behavioral rules: cite the task ID, reproduce before fixing, add source links, ask for approval before publishing, or any standard you want the AI to follow whenever a given workflow step runs.

You update the policy once. Every workflow assignment picks up the new rule automatically the next time the relevant step response is built.

Yes. Policies can be disabled, which stops them from being injected while preserving the workflows and assignments around them.
Continue the tour

Explore the rest of the platform.

01

Conversational Governance

See how gates, approvals, and audit trails enforce the flow itself.

Read more
02

Your Process, Every Conversation

Define the workflow once, then layer reusable rules on top of it.

Read more
ConvOps

Reusable rules, injected exactly when the step runs.

Policies let you enforce behavioral rules across workflows without editing template YAML. Create a rule once, assign it globally or to a specific template, and ConvOps injects it into the current step at read time.

Start with ConvOps Learn how it works