Reusable rules, injected exactly when the step runs.
Policies let you enforce behavioral rules across workflows without rewriting the workflow definition. Create a rule once, assign it globally or to a specific workflow, and ConvOps injects it into the current step at read time.
- cite-task-idGlobal
Always cite the task ID in every status update.
- reproduce-before-fixingDevelopment template
Reproduce the bug before proposing a fix.
- link-sourcesResearch template
Every claim must include a source link.
- 2
- Assignment scopes: global or template
- 1
- Edit point for a shared rule
- 0
- Template rewrites needed for policy updates
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.
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.
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.
- cite-task-idGlobal
Always cite the task ID in every status update.
- reproduce-before-fixingDevelopment template
Reproduce the bug before proposing a fix.
- link-sourcesResearch template
Every claim must include a source link.
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.
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.
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.
Reusable rules, injected exactly when the step runs.
Policies let you enforce behavioral rules across workflows without rewriting the workflow definition. Create a rule once, assign it globally or to a specific workflow, and ConvOps injects it into the current step at read time.