BP-002 — HOS Knowledge Library · bp-002-knowledge-library

Owner directive (2026-07-10), canonical. "You should have a folder with multiple folders and multiple files and multiple lines, so the neural engine can work like the obsidian knowledge base of antropic (as leaked in the video linked) but following the whole HOS model. … dont let the Neural Engine Execution or the Neural Ware Agenticly gettings things done stray a single word from the Kernels and the knowledge in general at the Library." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:542]

Content

The RESOLVED layer above the project's scattered sources, at HOS-Instance/library/. Deterministic rule: a datan reads ONLY library cards; every ruling cites its authority. This is what makes agents deterministic: "the version at mainland.so have all the concepts quite scattered and conflicting (but if you have them in a line you can deterministically presume the right definition" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:579].

Tree

library/
  _templates/   TEMPLATE.md — the single card format
  _meta/        check_links.py + build tooling (compiles cards → library.json)
  concepts/     resolved HOS concepts (pad, pod, loop, datan, holon, …)
  engines/      engine + kernel/cogni/genome cards (kernel-*, cogni-*, genome-*)
  playbooks/    pb-*      ordered loop-step tables (HOW, loopable)
  cookbooks/    cb-*      pinned official docs + our proven patterns
  blueprints/   bp-*      WHAT with acceptance criteria
  schematics/   sc-*      mermaid-first flows (how parts interact)
  schemas/      schema-*  prose + fenced JSON Schema data contracts
  sops/         sop-*     standing procedures
  squads/       squad-*   squad charters + roles
  benchmarks/   bm-*      measurable gates
  okrs/         okrs-*    objectives
  sources/      src-*     inventories of live external surfaces

Gates (all must pass; enforced by _meta/check_links.py)

1. Template conformance — every card follows TEMPLATE.md exactly; id = filename stem, unique library-wide. [src: HOS-Instance/library/_templates/TEMPLATE.md:44]
2. Zero orphans — every wikilink resolves to a library card id. [src: HOS-Instance/library/_templates/TEMPLATE.md:50]
3. Variants ⇒ authority — a card with a ## Variants table MUST carry non-empty authority; conflicting definitions are preserved VERBATIM, deprecated text is never deleted; without authority the card is draft with an ## Open question — never guess a ruling. [src: HOS-Instance/library/_templates/TEMPLATE.md:46]
4. Authority precedence — D-ledger (D1–D28, [src: HOS-Webdoc/web/src/data/hos-specification.ts:500]) > C-entries ([src: wiki/development/HANDOFF.md:127]) > owner-directive blockquotes in wiki canon > newest dated owner prompt. [src: HOS-Instance/library/_templates/TEMPLATE.md:52]
5. Citation integrity — every factual claim carries [src: path:line] resolvable from /Users/lucasaugusto/HOS/.
6. Graph compile — cards compile to library.json per schema-library-json with a stable content_hash.

Seed scope

The seed is the full library file plan (~80 cards across the folders above): the concept layer (pad, pod, dooit, ditto, assistant, companion, construct, entity/matter hierarchies, engines, districts, dikwc, neuralware, legacy petra/codex/cortex), the loop layer (loop, cognitive-loop, neural-engine, datan, looper, squad, holon, holonprint, biome, slice, scenery, kernel, cogni, genome, sapiens3, dwork, …), squads + OKRs + SOPs + benchmarks, the pb-/cb-/bp-/sc-/schema- set (this batch), the instance cards (kernel/cogni/genome/district for neural-engine and spatial-site) and the src- inventories.

Acceptance criteria

• All gates green in CI on every commit; one commit per card loop (pb-002-library-authoring step 8).
• The neural-engine can set up Neural Networks, neuralwares and Runs from cards alone — no raw-source reads at run time [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:532].
• Rendered as app page 5 with search + visualization (bp-001-spatial-site).
• Conflicting definitions surfaced, never resolved by guess: "Create different versions for conflicting definitions." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:618]

Composition

• uses: pb-002-library-authoring (authoring HOW) · sop-004-library-authoring, sop-002-conflict-resolution, sop-005-prompt-archival (procedures) · schema-library-json (compiled form)
• used-by: bp-001-spatial-site (page 5) · pb-003-run-dispatch (rules source) · sc-002-neural-engine-run (the Library lane)

See also

• dikwc — where the library sits in the Data→Wisdom pipeline
• neuralware-index — the capability catalog the cards configure