---
title: "Introduction"
description: "What BulkheadOS does for complex software companies."
canonical_url: "https://docs.bulkheados.com/"
template: "page-node"
schema_type: "WebPage"
---

<div class="docs-content">
<p class="docs-lead">BulkheadOS is a company operating graph for complex software companies. It links websites, docs, support, sales, product behavior, procedures, tests, and AI guardrails so humans and agents work from the same governed truth.</p>

<h2 id="what-you-get">What You Get</h2>
<p>When you map a product area in BulkheadOS, you get:</p>
<ul>
<li><strong>One governed product map</strong> - Connect public claims, docs, expected behavior, procedures, tests, and AI guardrails.</li>
<li><strong>Shared company language</strong> - Define the terms product, support, sales, documentation, and AI systems must use consistently.</li>
<li><strong>Traceable public surfaces</strong> - Serve pages, markdown alternates, schema, and AI-readable context from the same source of truth.</li>
<li><strong>Customer signal routing</strong> - Link support friction, sales objections, implementation gaps, and feedback back to product decisions.</li>
<li><strong>Verified action paths</strong> - Move from discovery into reviewed operator workflows without losing provenance or tenant isolation.</li>
</ul>

<h2 id="who-its-for">Who It's For</h2>
<ul>
<li><strong>Complex software companies</strong> - Teams whose websites, docs, support, sales, product decisions, and AI answers no longer line up.</li>
<li><strong>Product and knowledge operations teams</strong> - Teams turning scattered customer signal into governed product understanding.</li>
<li><strong>Support, CX, and sales engineering teams</strong> - Teams that need repeated friction and objections to become visible product inputs.</li>
<li><strong>AI platform teams</strong> - Teams trying to make agents accurate without asking them to infer the company from disconnected fragments.</li>
</ul>

<h2 id="key-principles">Key Principles</h2>
<ol>
<li><strong>Link the company first</strong> - AI quality depends on explicit company structure, not larger prompts over scattered content.</li>
<li><strong>Governance is the product</strong> - Claims, docs, procedures, tests, and AI guardrails change as one reviewed system.</li>
<li><strong>Public and operational truth stay connected</strong> - The website, knowledge base, support reality, and product decisions share one graph.</li>
<li><strong>Discovery can become verified action</strong> - AI-readable surfaces point back to provenance-preserving operator workflows.</li>
</ol>

<h2 id="show-me-real-examples">Show Me Real Examples</h2>
<p>The best way to understand BulkheadOS is to see the surfaces in use. These pages show how the operating graph becomes documentation, search, feedback, and AI discovery.</p>

<div class="docs-example-grid">
  <a class="docs-example-card" href="/content/code-blocks">
    <span class="docs-example-card__eyebrow">Code Examples</span>
    <strong class="docs-example-card__title">Shiki, code blocks, and copy buttons</strong>
    <span class="docs-example-card__body">See how Markdown preview, syntax highlighting, and multi-language snippets work in practice.</span>
  </a>
  <a class="docs-example-card" href="/ai/search">
    <span class="docs-example-card__eyebrow">Search</span>
    <strong class="docs-example-card__title">Orama-powered edge search</strong>
    <span class="docs-example-card__body">Inspect the exact request and response shape for the zero-D1 runtime search endpoint.</span>
  </a>
  <a class="docs-example-card" href="/content/feedback">
    <span class="docs-example-card__eyebrow">Feedback</span>
    <strong class="docs-example-card__title">Page feedback and editorial loops</strong>
    <span class="docs-example-card__body">Capture quick yes or no signals, then route them back into docs maintenance work.</span>
  </a>
  <a class="docs-example-card" href="/federation/comments">
    <span class="docs-example-card__eyebrow">Fediverse</span>
    <strong class="docs-example-card__title">Federated comments and reply threads</strong>
    <span class="docs-example-card__body">Show readers how comments flow back from ActivityPub into your site UI.</span>
  </a>
</div>

<h2 id="next-steps">Next Steps</h2>
<p>Start with the <a href="/ai/llms-txt">AI discovery</a> guide, then use the <a href="/quickstart">Quickstart</a> to understand how a tenant surface is published.</p>
</div>