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

# Overview

> A playbook for taking an AI use case from framing to adoption at scale, and governing agents across your organization.

This is a **playbook, not product reference**. It is written from your point of view: *you* decide the strategy, *we* recommend how to run it, and every recommendation links to the product rubric that makes it enforceable.

Two questions sit at the center of every rollout:

1. How do you take a use case from a first idea to production, and then to adoption at scale?
2. How do you let people build with AI without losing control of security, quality, and compliance?

<CardGroup cols={2}>
  <Card title="From a use case to production" icon="diagram-project" href="./use-case-lifecycle">
    The lifecycle in phases, the environments, and when to use a workspace or stay no-code.
  </Card>

  <Card title="Who does what" icon="users-gear" href="./operating-model">
    The operating model: squads, committees, and AI champions, and who holds which right.
  </Card>

  <Card title="One organization or several?" icon="sitemap" href="./org-vs-groups">
    The decision most teams hesitate on, and where groups fit.
  </Card>

  <Card title="Opening strategies" icon="shield-check" href="./opening-strategies">
    Open to everyone or curate specific use cases, and how to open without chaos.
  </Card>
</CardGroup>

## The one principle

Governance on the platform works on levels, and **each level can only tighten the one above, never widen it**. On conflict, the tightest limit wins. Inside its own envelope, each level distributes freely. Keep that in mind as you read the rest of this playbook. It is detailed in [Opening strategies](./opening-strategies) and in [Governe](/products/ai-governance/overview).
