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

# Operations overview

> The operations area is the cross-resource health and runtime visibility surface for StackShift.

<Tip>
  **Live.** This area is documented as current, user-reliable behavior.
</Tip>

## Goal

Understand what belongs in operations versus in a resource detail page.

## Prerequisites

* At least one live resource

## Workflow

<Steps>
  <Step>
    Use operations when you want a platform-wide view instead of a single resource view.
  </Step>

  <Step>
    Drill into services, alerts, and nodes depending on the operational question.
  </Step>

  <Step>
    Treat recovery-state messaging as part of the operational model, not just a design flourish.
  </Step>
</Steps>

## When to start in Operations

* Several services look unhealthy at once
* You need a fleet-level view before drilling into one resource
* You want to understand alerts, services, and node state together

## What Operations is not

Operations is not a replacement for resource detail pages. It is the platform-wide orientation surface. Start there when the question is broad, then drill into the relevant project, stack, database, or node page when you need resource-specific evidence.

## Expected result

<Check>
  You know where to look first when something feels wrong at a platform level.
</Check>