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

# Knowledge and Delivery

## Docs

- [Git History Tools in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/git-history-tools.md): Read what a planner or writer step can learn from local git history, how each read is bounded and cited, and the codes a refused read records.
- [Knowledge Contracts in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/knowledge.md): Look up DocsFab knowledge commands, source-thread records, and reference-model artifacts.
- [DocsFab Knowledge CLI](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/knowledge/knowledge-cli.md): Look up commands and options for the local DocsFab knowledge-gathering control plane.
- [Source-Thread Registry in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/knowledge/source-thread-registry.md): Look up the canonical source-thread records, artifact representations, event ledger, and validation commands.
- [Reference-Model Package in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/knowledge/reference-model-package.md): Look up the directory layout and required records for an immutable DocsFab product reference-model version.
- [Delivery Contracts in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/delivery.md): Look up DocsFab GitLab mailbox, candidate proposal, convergence, and freshness contracts.
- [GitLab Host Mailbox in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/delivery/gitlab-host-notification.md): Look up the current GitLab mailbox contracts and provider-neutral merge-request change-event intake.
- [Reviewed Documentation Candidate Proposals in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/delivery/documentation-delivery.md): Look up the trusted-host contract for proposing an independently reviewed candidate as a GitLab draft merge request. For this repository's Fern preview, follow Preview the Documentation Site.
- [Documentation Convergence and Freshness in DocsFab](https://docs.nvidia.com/docsfab/reference/knowledge-and-delivery/delivery/documentation-convergence.md): Understand how DocsFab keeps source threads, models, documentation, and quality evidence aligned.


> **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/reference/knowledge-and-delivery/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/docsfab/_mcp/server.

# DocsFab Knowledge and Delivery Reference

> Find the contracts that govern product-knowledge records and delivery through GitLab and Fern.

This section of the DocsFab reference separates evidence records from
delivery channels. Knowledge contracts define what DocsFab retains and
synthesizes. Delivery contracts define how reviewable results, documentation
previews, and freshness evidence move without granting publication or merge
authority. For more information, refer to [Overview of
DocsFab](/docsfab/about).

## Choose a Reference Area

The following table maps each question to its reference area.

| Question | Area | What it does not cover |
| --- | --- | --- |
| Which command or canonical record preserves product evidence? | [Knowledge Contracts in DocsFab](/docsfab/reference/knowledge-and-delivery/knowledge) | GitLab communication, Fern delivery, and publication. |
| How does a completed result reach reviewers or stay current? | [Delivery Contracts in DocsFab](/docsfab/reference/knowledge-and-delivery/delivery) | Source acquisition, claim synthesis, and model-record shape. |

## Follow the Evidence Flow

1. Register evidence in a [source thread](/docsfab/reference/knowledge-and-delivery/knowledge/source-thread-registry).
2. Reconcile evidence into an immutable [reference-model package](/docsfab/reference/knowledge-and-delivery/knowledge/reference-model-package).
3. Check whether documentation and retained review evidence [remain current](/docsfab/reference/knowledge-and-delivery/delivery/documentation-convergence).
4. Deliver a review signal through the [GitLab mailbox](/docsfab/reference/knowledge-and-delivery/delivery/gitlab-host-notification) or preview documentation through [Fern site delivery](/docsfab/reference/knowledge-and-delivery/delivery/documentation-delivery).