#Knowledge Library

Knowledge Library manages durable source collections, indexing state, search, pinned libraries, recovery, and per-library settings without pretending that a visual component owns ingestion, embeddings, storage, or permissions.

npm install @a3s-lab/ui@0.4.0

<section class="knowledge-library" data-state="ready" aria-label="Knowledge library">
<aside data-knowledge-library-navigation>
  <nav aria-label="Knowledge filters"><button type="button" data-knowledge-filter="all" aria-pressed="true">All knowledge</button></nav>
</aside>
<main>
  <div data-knowledge-library-toolbar>
    <label data-knowledge-library-search><span class="sr-only">Search knowledge</span><input type="search" /></label>
  </div>
  <div data-knowledge-library-viewport>
    <ul data-knowledge-library-list>
      <li><button type="button" data-knowledge-item data-knowledge-value="design" data-knowledge-phase="succeeded" aria-selected="true"><span data-knowledge-item-identity><strong>Design system</strong><small>86 sources</small></span><span data-knowledge-phase="succeeded">Up to date</span></button></li>
    </ul>
  </div>
</main>
</section>
<script type="module">
import "@a3s-lab/ui";
import "@a3s-lab/ui/knowledge-library";
const library = document.querySelector(".knowledge-library");
library.addEventListener("a3s:knowledge-before-action", event => {
  if (!authorizeKnowledgeAction(event.detail)) event.preventDefault();
});
library.addEventListener("a3s:knowledge-action", event => runKnowledgeAction(event.detail));
</script>

import "@a3s-lab/ui/a3s.css";
import "@a3s-lab/ui/all";

#Product decisions

A knowledge base is a durable, named boundary around approved sources. It is not a folder alias, a chat attachment list, or a decorative database card.

• Every library exposes source count, freshness, indexing phase, and a recovery path.
• queued and running are distinct because waiting for capacity and actively indexing require different expectations.
• A failed update preserves the last usable searchable version. Destructive rebuilds require an explicit host flow.
• Automatic updates need a stated policy, minimum interval, pause behavior, and a visible manual recovery action.
• Source selection, authentication, parsing, chunking, embeddings, vector storage, retrieval quality, and access control remain host responsibilities.

#Controller contract

#Accessibility and ownership

Library items remain ordinary named buttons in a list; arrow keys, Home, and End move between visible items while Enter or Space opens details. Status always includes text and never depends on color. Detail tabs, when present, use the Tabs contract. The host owns authorization, ingestion jobs, retries, source validation, storage, retrieval, deletion recovery, and localized user data.