Skip to main content
Optimizations turn audit recommendations into a hosted backlog. Policies (Alpha) turn selected recommendations into hosted guardrail drafts that can be reviewed before activation.
Optimizations and policies are hosted workspace features. Run local audits for free, then push the audits you want to track in the hosted dashboard. Optimizations work on any workspace; Policies (Alpha) require Pro or Enterprise.

​
Optimizations backlog

The backlog is built from the latest active pushed audits. It combines:
  • modeled items from v2 recommendations
  • provisional opportunities when an older audit has findings but no modeled recommendation object
  • recurrence signals when similar opportunities appear again
Use filters for status, source, severity, category, implementation surface, recurrence state, and time range.

​
Lifecycle statuses

Optimization items move through:
  • Open: the opportunity still needs work
  • Implemented: a change was shipped or the operational fix was made
  • Validated: a compare audit was selected to prove the result
  • Archived: the item is no longer relevant
Modeled items can store a validation link to a pushed compare audit. Use the same effective source and a compatible audit window so the before/after comparison is meaningful.

​
Recommendation fields

The current v2 recommendation contract includes:
  • priority bucket: fix_now, test_next, or watch
  • implementation surface, such as retry_policy, loop_guard, model_routing, scheduler, prompt_builder, or user_behavior
  • category, severity, confidence, effort, and estimated savings
  • scope label, where-to-change guidance, validation plan, and action steps
These fields are generated by the CLI and preserved in the push payload, dashboard, hosted MCP, and @xerg/schemas.

​
Policies (Alpha)

Policies are hosted rules associated with the workspace. A policy has a status, scope, action, threshold metric, threshold value, source, and optional recommendation reference. Current policy status values are:
  • draft
  • active
  • paused
Current scopes are:
  • workspace
  • source
  • workflow
Signed-in workspace admins can create, update, and delete policies. Workspace API keys can create idempotent recommendation-backed draft policies through the recommendation flow, but they cannot make arbitrary manual policy changes.

​
Cedar previews

When policy generation is enabled, Xerg stores Cedar policy text and version metadata with the policy. Policy creation and updates return validation errors if Cedar generation, parsing, or validation fails. Use draft status while evaluating a rule. Promote to active only after the team agrees on the threshold and scope.

​
Hosted MCP write safety

Hosted MCP exposes both read tools and guarded write tools. Write tools use preview and commit semantics so clients can inspect the planned change before committing it. Relevant tools include:
  • xerg_recommendations
  • xerg_list_policies
  • xerg_upsert_policy
  • xerg_delete_policy
  • xerg_create_policy_from_recommendation
Use hosted MCP for client configuration and the full tool list.