> ## 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.

# From a use case to production

> The lifecycle of an AI use case: phases, environments, and the workspace or self-care choice.

You own the use case. This is the path we recommend to take it from a first idea to a supervised production service, and a method you can reuse for the next one.

## The lifecycle

<Steps>
  <Step title="Framing & POC">
    Pick a scope that proves business value and is feasible. Validate the idea quickly before investing. Recommendation: agree on shared selection criteria so the next use cases are chosen the same way.
  </Step>

  <Step title="Audit & MVP specification">
    Define the target scope, run a security review, and specify the MVP. Bring in the systems and data the agent will need.
  </Step>

  <Step title="MVP">
    Build an industrializable version: connectors, authentication, [evaluation](/products/agent-factory/evaluations), and monitoring in place. Iterate with real users (UAT).
  </Step>

  <Step title="Industrialization">
    Apply engineering discipline: [Git versioning](/products/ai-builder/versioning), CI/CD, [observability](/products/ai-builder/observability), roles and permissions, security and performance tests.
  </Step>

  <Step title="Go-live">
    Promote to production and make the solution auditable (AI Act, GDPR). Onboard the teams who will use it.
  </Step>

  <Step title="Operation & continuous improvement">
    Keep it running and secure: monitoring, KPIs via [Insights](/products/ai-insights/overview), and updates to keep pace with the state of the art.
  </Step>
</Steps>

## Deploying it

Deployment runs on **two independent cycles**: the platform moves through its own Dev, Pre-production, and Production environments with CI/CD, while each use case has its own dev and prod workspaces on the production environment, versioned by Git. This is covered in detail in [Deployment strategy](./deployment), including the workspace-or-self-care choice.

## Next steps

<CardGroup cols={2}>
  <Card title="Deployment strategy" icon="rocket" href="./deployment">
    Platform environments, and the two-workspace Git model per use case
  </Card>

  <Card title="Who does what" icon="users-gear" href="./operating-model">
    The teams and rights behind this lifecycle
  </Card>

  <Card title="Opening strategies" icon="shield-check" href="./opening-strategies">
    How to let people build without chaos
  </Card>
</CardGroup>