> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.nvidia.com/docsfab/about/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/docsfab/_mcp/server. # About ## Docs - [Use Cases](https://docs.nvidia.com/docsfab/about/use-cases.md): Learn which product goals DocsFab serves, which journeys start those goals, and which catalog jobs those journeys use. - [Key Features](https://docs.nvidia.com/docsfab/about/key-features.md): Compare DocsFab capabilities by outcome, evidence state, and the guide for using them. - [Architecture Overview for DocsFab](https://docs.nvidia.com/docsfab/about/architecture.md): Understand DocsFab component roles and the flow from a documentation request to a reviewable result. - [Documentation Jobs in DocsFab](https://docs.nvidia.com/docsfab/about/core-concepts/documentation-jobs.md): Learn what a DocsFab documentation job is, which jobs the catalog offers, what a job returns, and why a result grants no write or merge authority. - [When a Job Stops in DocsFab](https://docs.nvidia.com/docsfab/about/core-concepts/job-stops.md): Learn why a DocsFab job stops instead of guessing, how to read a stop, and which kind of next action unblocks it. - [Product Knowledge in DocsFab](https://docs.nvidia.com/docsfab/about/core-concepts/product-knowledge.md): Learn how DocsFab keeps product evidence by source, synthesizes it into a versioned product reference model, and uses that model to write documentation. - [Documentation Quality in DocsFab](https://docs.nvidia.com/docsfab/about/core-concepts/documentation-quality.md): Learn how DocsFab judges documentation quality in layers, what each check can show, and how to read fail, insufficient-evidence, and needs-input results. - [Security and Trust](https://docs.nvidia.com/docsfab/about/core-concepts/security-and-trust.md): Understand the trust model for DocsFab sessions, product evidence, credentials, and documentation delivery. - [Release Notes for DocsFab](https://docs.nvidia.com/docsfab/about/release-notes.md): Learn about the changes, features, and known issues in each DocsFab release. > **Note:** This page contains both a page directory (above) and the landing page content (below). The page directory is generated for agent use and does not appear on the landing page. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.nvidia.com/docsfab/about/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/docsfab/_mcp/server. # NVIDIA DocsFab Documentation > Create, update, and review documentation from product evidence, then inspect the claims, changes, and quality results behind each outcome. DocsFab helps product teams create, update, and review documentation from repository evidence and attributed product knowledge. You can use a local conversation or a named workflow to produce documentation changes and inspect their supporting evidence. For capabilities and evidence states, refer to [Key Features](/docsfab/about/key-features). DocsFab is in project stage alpha. The local command-line interface (CLI) and live agent are the current product surfaces. Automatic GitLab CI proposals remain intended, with integration pending. For capability evidence and public release limitations, refer to [DocsFab Implementation Status](/docsfab/reference/status-and-configuration/implementation-status). ## Skip Ahead Choose a starting point for supported environments, your first task, workflow examples, or recovery. Check platform coverage, tested model routes, and environment prerequisites in the [DocsFab Support Matrix](/docsfab/reference/support-matrix). [Install DocsFab](/docsfab/get-started/installation), then follow the [Live Agent Quickstart](/docsfab/get-started/live-agent-quickstart) or [Runner Quickstart](/docsfab/get-started/runner-quickstart). Choose a named job and inspect command examples in [Run a Documentation Workflow](/docsfab/workflows/run-a-documentation-workflow). Match an error or failed task to a recovery action in [Troubleshooting DocsFab](/docsfab/troubleshooting). ## Use Cases Choose the documentation outcome you need. [Use Cases](/docsfab/about/use-cases) explains the participating roles and catalog jobs for these goals. Turn product evidence into a new page or short documentation set. Gather missing product knowledge before drafting, then inspect the result with the [Runner Quickstart](/docsfab/get-started/runner-quickstart). Assess documentation impact and propose a scoped update beside a product change. Start with [Update Documentation Beside a Change](/docsfab/workflows/update-documentation-beside-a-change) or [Review Merge Request Impact](/docsfab/workflows/review-merge-request-impact). Review an existing set, establish a health baseline, and identify gaps in accuracy or reader evidence. Start with [Baseline Documentation Health](/docsfab/workflows/baseline-documentation-health). ## Core Concepts These concepts explain how DocsFab turns a request into evidence you can inspect. Start with jobs and stops to understand execution, then read product knowledge and quality to interpret the evidence. A job binds one named outcome to a repository revision, workflow, and allowed operations. It retains a run record, findings, and any authorized patch. Refer to [Documentation Jobs](/docsfab/about/core-concepts/documentation-jobs). A stop records why a job cannot finish and what can unblock it. Missing input, a failed check, and a capability boundary require different next actions. Refer to [When a Job Stops](/docsfab/about/core-concepts/job-stops). The product reference model is a canonical, versioned representation of shared product understanding. Claims remain traceable to sources, scope, decisions, and unresolved questions. Refer to [Product Knowledge](/docsfab/about/core-concepts/product-knowledge). Quality combines evidence about factual trust, reader understanding, and task success. Separate checks retain their own conclusions; a completed workflow does not grant publication approval. Refer to [Documentation Quality](/docsfab/about/core-concepts/documentation-quality). ## Core Components DocsFab combines knowledge and quality inputs with a runtime that executes jobs. A separate host channel delivers results to GitLab. Registers attributed sources, reconciles conflicts, and versions the product reference model. Refer to [Product Knowledge](/docsfab/about/core-concepts/product-knowledge). Binds jobs to pinned inputs and allowed tools, executes workflow steps, and retains the result. Refer to [Architecture Overview](/docsfab/about/architecture). Supplies locked writing, review, evaluation, and deterministic-check inputs to a job. Refer to [Documentation Quality](/docsfab/about/core-concepts/documentation-quality). Posts review notes or opens draft merge requests through separately authorized GitLab delivery. Refer to [GitLab Delivery](/docsfab/reference/architecture#gitlab). For component relationships, refer to [Architecture Overview](/docsfab/about/architecture). For credential, command, and evidence boundaries, refer to [Security and Trust](/docsfab/about/core-concepts/security-and-trust).