Govern

Policy Editor

Author the live compile policy that shapes context selection and tool approval defaults. Changes here affect the governed production path, so this screen is built for review before release.

Minimum sentence tokens
10
Short sentences below this threshold are filtered first.
Allowed overage
25.0%
How much the compile output may grow beyond the baseline.
Rule count
0
Boosting and redaction rules active in the current policy.
Save state
Synced
Approval gating still applies when live policy updates require review.
Live policy configuration

Tune the compile policy, then ship it through the same governed save path used by the product.

Lower values keep more terse snippets in the compiled context.

Set how much the compiled result may exceed the extractive baseline.

Rule stack

Combine whitelist boosts with regex-driven redaction for governed compile behavior.

No rules configured yet. Add a rule to boost critical topics or redact sensitive patterns.
Authoring checklist
Protect the context window
Trim noise aggressively enough to keep relevant working context under control.
Preserve critical topics
Boost security, billing, and workflow keywords that should consistently survive ranking.
Use Policy Lab for experiments
Prototype examples, run preview compiles, and then import the result here for live save.
POLICY SYNCED
Schema reference

Global settings

  • min_sentence_tokens: minimum tokens per sentence.
  • max_overage_ratio: maximum allowed compile growth.

Rule properties

  • whitelist: keywords to boost.
  • regex: pattern to match.
  • weight: score multiplier.
  • redact: replacement text.

Advanced tool_controls YAML is preserved on save. Use Policy Lab when you want to prototype approval defaults and overrides before promoting them here.

EXAMPLE
min_sentence_tokens: 6
max_overage_ratio: 0.05
tool_controls:
  defaults:
    write: ask
    delete: ask
rules:
  - whitelist: ["security", "pci"]
    weight: 2.0
  - regex: "\\b[A-Z0-9._%+-]+@[A-Z0-9.-]+\\.[A-Z]{2,}\\b"
    redact: "[EMAIL]"