> ## Documentation Index
> Fetch the complete documentation index at: https://docs.draftt.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How Draftt Works

Draftt runs a continuous governance loop across your tech stack. Here is how data flows from your infrastructure to an actionable finding in your team's queue.

## The Governance Loop

<Steps>
  <Step title="Connect your sources">
    Draftt connects to your cloud providers, managed services, registries, ticketing platforms, and collaboration tools via read-only integrations. No agents required. No changes to your infrastructure or code.

    See [Connectors & Integrations](/integrations-overview) for the full list.
  </Step>

  <Step title="Build the inventory">
    Draftt pulls resource metadata from every connected source and assembles a unified, continuously updated inventory. Each resource is enriched with version data, configuration state, ownership signals, and cost attribution.

    The inventory reflects the live state of your stack, not a point-in-time snapshot.
  </Step>

  <Step title="Evaluate against policies">
    On every scan cycle, Draftt evaluates every resource in your inventory against your active governance policies. System policies track end-of-life status, certificate expiration, version currency, and Kubernetes compatibility out of the box. Custom policies let you enforce your own standards.

    See [Governance Policies](/governance-policies) for how policies are configured.
  </Step>

  <Step title="Surface findings">
    When a resource violates a policy, Draftt surfaces it in the inventory with the affected resource, the violated policy, the resolved owner, and a recommended remediation path.
  </Step>

  <Step title="Route to remediation">
    Findings are routed to the tools your teams already use: Jira, ServiceNow, Azure DevOps, Slack, Teams, or email. Tickets include everything the engineer needs to act: what is wrong, why it matters, who owns it, and how to fix it.
  </Step>
</Steps>

## Scan Frequency

Draftt scans every 8 hours by default. The scan interval can be configured to match your organization's needs. Policy evaluation runs on every scan cycle, so your inventory and governance status always reflect a recent state of your stack.

## Data Access

All integrations use read-only access. Draftt never modifies your infrastructure, pushes configuration changes, or writes to your cloud accounts. The only write actions Draftt performs are creating tickets and sending notifications in platforms you have explicitly connected and configured.