Skip to main content

Custom Policies

Custom Policies are the place to store organization-specific instructions that should outlive any single prompt. The current product exposes them as policy definitions under Compliance -> Policies.

What A Policy Is In Today’s Product

A policy is:
  • A named definition
  • Optional description
  • Markdown-style policy content
  • A versioned record with history
This is closer to durable operational guidance than to a standalone rule engine UI.

What You Can Do

The current UI supports:
  • Create from scratch
  • Start from a template
  • Edit and version a policy
  • Duplicate or deactivate it
  • Inspect history and processed metadata
The detail view also shows whether the policy has been processed successfully.

Good Uses

Use a custom policy when you need Cloudgeni to remember local standards such as:
  • Naming conventions
  • Required tags or labels
  • Repository structure expectations
  • Internal security guardrails
Keep the policy short and specific. Long narrative documents are harder for both people and tools to apply consistently.

What Not To Assume

Do not describe custom policies as if they were a separate enforcement engine with their own large runtime surface. In the current product they are reusable guidance artifacts that feed Cloudgeni’s workflows.

AI DevOps

Use policies to give agent sessions better organization-specific context.

Pull Request Reviews

Pair policies with PR review workflows when review standards need to be repeatable.