> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/docsfab/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/docsfab/_mcp/server.

# About DocsFab Workflows

> Find the DocsFab workflow guide for the documentation or product-knowledge task you need to complete.

DocsFab workflows are task guides that you use after setup to run one
specific documentation or product-knowledge job. Each workflow keeps product
evidence, runtime execution, quality checks, and write authority explicit.
For more information, refer to [Overview of DocsFab](/docsfab/about).

## Before You Choose

Complete [Install DocsFab](/docsfab/get-started/installation) before you run a
workflow. Define one bounded product, repository revision, audience, and
documentation target. A workflow can produce evidence, a model artifact, or a
reviewable patch. It does not grant publication, deployment, or merge
authority.

To create the first page or a short set for a new product or feature, start
with the [Runner Quickstart](/docsfab/get-started/runner-quickstart).

## Choose a Workflow

Choose the task guide for the result you need:

| Goal | Guides |
| --- | --- |
| Create, update, or restructure pages. | [Create a Documentation Set](/docsfab/workflows/create-documentation-set), [Update Beside a Change](/docsfab/workflows/update-documentation-beside-a-change), [Update a Page Set](/docsfab/workflows/update-documentation-set), [Restructure a Set](/docsfab/workflows/restructure-documentation-set) |
| Inspect existing documentation. | [Baseline Documentation Health](/docsfab/workflows/baseline-documentation-health), [Review Merge Request Impact](/docsfab/workflows/review-merge-request-impact), [Audit Templates](/docsfab/workflows/audit-templates), [Assess Readiness](/docsfab/workflows/assess-readiness) |
| Bind evidence to a job. | [Select Sources](/docsfab/workflows/select-sources), [Bind a Commit Range](/docsfab/workflows/bind-commit-range), [Bind a GitLab Change](/docsfab/workflows/bind-gitlab-change), [Bind a GitHub Change](/docsfab/workflows/bind-github-change), [Bind a Release Range](/docsfab/workflows/bind-release-range) |
| Handle a specialized update. | [Update One RST Page](/docsfab/workflows/update-rst-page), [Verify No Change](/docsfab/workflows/verify-no-change) |
| Work in a persistent conversation. | [Attach Live Evidence](/docsfab/workflows/attach-live-sources), [Edit Documentation](/docsfab/workflows/edit-in-live-agent), [Deliver a Live-Agent Patch](/docsfab/workflows/deliver-live-patch) |
| Continue stopped work. | [Supply Requested Work Products](/docsfab/workflows/supply-work-products), [Answer and Resume](/docsfab/workflows/answer-and-resume) |
| Use an activated Slack project. | [Review From Slack](/docsfab/workflows/review-from-slack), [Ask a Documentation Question](/docsfab/workflows/ask-from-slack), [Continue a Hosted Review](/docsfab/workflows/continue-hosted-review) |
| Automate or deliver a result. | [Run in CI](/docsfab/workflows/run-docsfab-in-ci), [Automatic CI Proposals](/docsfab/workflows/automatic-ci-proposals), [Delegate a Local Task](/docsfab/workflows/delegate-a-task), [Deliver a Draft MR](/docsfab/workflows/deliver-draft-mr) |
| Inspect execution evidence. | [Investigate Saved Runs](/docsfab/workflows/investigate-saved-runs), [Diagnose a Failed Run](/docsfab/manage/diagnose-run) |

For the common execution steps, follow [Run a Documentation Workflow](/docsfab/workflows/run-a-documentation-workflow). For first-pass source selection and stops, refer to [First-Pass Knowledge](/docsfab/workflows/first-pass-knowledge). Exact stage order, fields, and authority rules remain in [Workflow Contracts](/docsfab/reference/workflow-contracts).

## Gather Product Knowledge

When a documentation job stops because load-bearing product evidence is
missing, contradictory, or stale, gather and reconcile that evidence before
you resume the documentation work. Product-knowledge work does not replace a
version-bound behavior check, an accountable intent decision, or a
documentation-quality review.

Complete these stages in order when you start without a validated product
model:

1. [Run the knowledge-gathering workflow](/docsfab/workflows/run-knowledge-gathering-workflow).
2. [Conduct a product-model interview](/docsfab/workflows/conduct-product-model-interview)
   when attributable intent or participant knowledge is missing. You can skip
   the interview when registered evidence already covers the target.
3. [Reconcile source threads](/docsfab/workflows/reconcile-source-threads) and issue the next
   model version. You cannot skip reconciliation when selected source threads
   contain unresolved differences that affect the target.

Stop and preserve the open dependency when any of the following conditions apply:

- The authoritative source or exact version is unavailable.
- Retention, citation, access, or participant consent does not cover the
  proposed artifact.
- A conflict requires behavior evidence or an accountable decision that is not
  available.
- Provenance is lost, or an immutable source or model version would need to be
  overwritten.

Do not fill the gap with conversational memory or plausible prose. Keep the
affected documentation target blocked until its load-bearing evidence is
available.

## Understand the Boundaries

The two workflow groups have the following responsibilities:

- Product-knowledge workflows establish traceable inputs and readiness. They
  do not silently promote a participant statement or agent inference into
  product truth.
- Documentation workflows bind pinned inputs to a fixed runtime job and
  quality policy. They do not broaden write or delivery authority from the
  wording of a request.

For the underlying authority model, refer to
[A Result Grants No Authority](/docsfab/about/core-concepts/documentation-jobs#a-result-grants-no-authority).
For the intended product goals these journeys serve, refer to
[Use Cases](/docsfab/about/use-cases).