> ## Documentation Index
> Fetch the complete documentation index at: https://na-36-automation-governance-sync.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Content brief template

# Content Brief - \[PAGE TITLE]

**Tab:** \[GPU Nodes / Gateways / Developers / Other]
**Page type:** \[guide / evaluation / concept / reference / how-to]
**Estimated audience:** \[describe in functional terms: hardware profile, goal, LPT position]
**Brief author:**
**Date:**

[//]: # "mdx-safe-markdown:divider"

## ⛔ GATE: L0 - Value Proposition

Complete all four before proceeding. If any cannot be answered, stop.
Escalate to product owner. Do not draft until answered.

**Q1 - Operator outcome**
What does this product, feature, or section do for the operator?
One sentence. No conditionals. No `if`, `can`, `may`, `depends on`.

> Answer:

[//]: # "mdx-safe-markdown:divider"

**Q2 - Featured (majority) path**
Which operator profile is already succeeding with this, and what does their
setup look like? This is the default story. Edge cases are variants.

> Answer:

[//]: # "mdx-safe-markdown:divider"

**Q3 - Reader's real alternative**
What would the reader do instead of this?
Defines the competitive context this page must address.

> Answer:

[//]: # "mdx-safe-markdown:divider"

**Q4 - Required belief**
What does the reader need to believe to take the next step?
One sentence. A belief, not a mechanism.

> Answer:

[//]: # "mdx-safe-markdown:divider"

**L0 self-check before proceeding:**

* [ ] Q1 contains no conditional (if / can / may / depends on)
* [ ] Q2 describes the majority path, not an edge case
* [ ] Q3 is specific, not blank or vague
* [ ] Q4 is a belief statement, not a mechanism description

If any box is unchecked: stop. Return to product owner.

[//]: # "mdx-safe-markdown:divider"

## ⛔ GATE: L1 - Persona Path Mapping

Complete before drafting. Every row must be served by the page
or explicitly routed to a linked page.

| Operator profile (hardware / LPT / goal) | Primary question on arrival | What this page must give them | Served here or linked? |
| ---------------------------------------- | --------------------------- | ----------------------------- | ---------------------- |
|                                          |                             |                               |                        |
|                                          |                             |                               |                        |
|                                          |                             |                               |                        |

[//]: # "mdx-safe-markdown:divider"

## Content Sequence Plan (L2)

Mark the sequence before writing. This is the order sections appear on the page.

* [ ] **1. Operator outcome** - value kept, one sentence, no conditionals
* [ ] **2. Featured path** - majority model, described in full
* [ ] **3. Variants** - alternative paths with specific entry requirements
* [ ] **4. Economics** - concrete figures, no hedging
* [ ] **5. Decision aid** - complete, no empty cells, no REVIEW flags
* [ ] **6. Staged action path** - numbered, zero to first outcome
* [ ] **7. Next page link** - one link, correct next step for primary reader

[//]: # "mdx-safe-markdown:divider"

## Scope

**In scope:**

**Out of scope (explicit):**

[//]: # "mdx-safe-markdown:divider"

## SME Review Items

List any claims that require SME verification before publishing.
These are not placeholders. Each must be resolved before the page merges.

| Claim | SME required | Status     |
| ----- | ------------ | ---------- |
|       |              | Unverified |

[//]: # "mdx-safe-markdown:divider"

## Research Sources

List sources used before drafting. Do not draft without completing this section.

[//]: # "mdx-safe-markdown:divider"

## Forbidden

List files this brief must not touch (scope protection):

[//]: # "mdx-safe-markdown:divider"

## Step 0 - Verification (Codex)

Before writing any content, Codex must verify:

1. The base branch is current (`docs-v2-dev`)
2. Target file paths exist as expected
3. No conflicting in-progress tasks on the same files
4. L0 and L1 sections above are complete

If any Step 0 check fails: stop and report. Do not proceed.