---
title: "Reviewed Knowledge Packages"
description: "Portable public knowledge packages for reviewed content and approved AI discovery workflows."
canonical_url: "https://docs.bulkheados.com/ai/knowledge-bundles/"
template: "page-node"
schema_type: "WebPage"
---

<div class="docs-content">
<p class="docs-lead">Reviewed knowledge packages turn approved public material into a portable markdown format that partners, reviewers, and approved tools can inspect without turning the package into your source of truth.</p>

<h2 id="what-they-are">What They Are</h2>
<p>A reviewed knowledge package is a structured set of markdown documents with metadata. It can describe public concepts, link related pages, and point back to the live source on your site.</p>
<p>Review status, source links, and publication evidence travel with each package, so a reviewer can inspect where the knowledge came from without needing workspace access.</p>

<h2 id="when-to-use-them">When To Use Them</h2>
<ul>
<li><strong>Partner review</strong> - Share a package with a partner, reviewer, or external tool without handing over the workspace.</li>
<li><strong>AI discovery</strong> - give approved tools a cleaner package than a scrape of disconnected pages.</li>
<li><strong>Migration planning</strong> - compare incoming knowledge against the current public projection before any content changes are approved.</li>
</ul>

<h2 id="how-bulkheados-handles-them">How BulkheadOS Handles Them</h2>
<p>BulkheadOS treats reviewed knowledge packages as an exchange format. Your site content, ownership, settings, and publishing rules remain managed in the workspace. A package can be generated from reviewed public material, inspected in HQ, and compared with another package without changing live content.</p>
<p>The workspace stays where teams edit, approve, and publish. The package is portable evidence for review and exchange, not a new place to manage your product knowledge.</p>

<h2 id="publication-rules">Publication Rules</h2>
<p>Reviewed knowledge packages are not automatically public. A workspace must have publication enabled, the generated package must exist, and the public discovery report must agree before the package is advertised. Drafts, restricted pages, private notes, and unpublished material stay out of the package.</p>

<h2 id="operator-path">Operator Path</h2>
<ol>
<li>Open <strong>Discovery</strong> in HQ.</li>
<li>Review the knowledge package readiness section.</li>
<li>Load the generated package into the preview panel.</li>
<li>Validate the package and review any warnings.</li>
<li>Compare an incoming package before planning any import work. HQ shows what changed before anyone plans a content update.</li>
</ol>

<div class="docs-callout docs-callout--info">
<p><strong>Safe by default:</strong> Preview and comparison do not publish a package, import content, or change a page. They give operators evidence before a separate approved workflow exists.</p>
</div>
</div>