PB-002 — Library Card Authoring Loop · pb-002-library-authoring
Owner directive (2026-07-10), canonical. "Compare all the context of the pages inside the droplet, write down the Knowledge library with knowledge bases which shall be used by the Neural engines to setup the Neural Networks, Neural Wares, Runs, eveything. […] Create different versions for conflicting definitions. […] So you never need to guess." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:532]
Content
The authoring loop that produces every card in this library (the WHAT is bp-002-knowledge-library; the standing procedure is sop-004-library-authoring). Deterministic rule: a datan reads ONLY library cards, and every ruling cites its authority — the version at mainland.so has "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]. Each row is a work particle a squad (roles per squad-roles) loops on.
| step | action | cookbooks | gear-set | verify gate |
|---|---|---|---|---|
| 1 | Scope the card — pick the id from the library file plan; confirm folder and type | cb-patterns-hosweb (docs conventions) | gear.knowledge | id exists in the plan, unique library-wide, equals filename stem |
| 2 | Read the authority chain — in precedence order: D1–D28 ledger [src: HOS-Webdoc/web/src/data/hos-specification.ts:500], C-entries [src: wiki/development/HANDOFF.md:133], owner-directive blockquotes in wiki canon, newest dated owner prompt | — | gear.knowledge | every claim to be made has a located authority OR is marked as open |
| 3 | Draft to TEMPLATE — YAML frontmatter, # Name · id, owner-directive blockquote, ## Content [src: HOS-Instance/library/_templates/TEMPLATE.md:1] | — | gear.knowledge | all frontmatter fields present; updated is today; blockquote cites its source line |
| 4 | Variants sweep — collect every conflicting definition VERBATIM into the ## Variants table; deprecated text is never deleted [src: HOS-Instance/library/_templates/TEMPLATE.md:51] | — | gear.knowledge | card with Variants has non-empty authority; if no authority exists → status: draft + ## Open question — NEVER guess a ruling |
| 5 | Wikilinks — link every HOS term with a wikilink, only to ids in the library file plan | — | gear.knowledge | _meta/check_links.py zero orphans; zero invented ids |
| 6 | Composition — record uses / used-by edges | — | gear.knowledge | every edge names a resolvable card; reciprocity noted where the peer card exists |
| 7 | Peer review — a second squad role (per squad-roles: Knowledge Analyst / ditto) spot-checks citations | — | gear.knowledge | every sampled [src: path:line] resolves to the quoted text; review is "professional and direct peer review visible" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:632] |
| 8 | Commit — one commit per card loop, PR to the library branch | — | gear.ops | CI check gate green (template lint + link check); commit references the card id |
Escalation: an unresolvable conflict goes to sop-002-conflict-resolution; the card stays draft with an ## Open question addressed to the owner until a ruling lands in the authority chain.
Composition
- uses: sop-004-library-authoring (procedure) · sop-002-conflict-resolution (escalation) · schema-library-json (the graph the cards compile into) · gear-sets
- used-by: pb-003-run-dispatch (queued playbook) · bp-002-knowledge-library (delivery vehicle) · squad-schematic
See also
- sop-005-prompt-archival — how owner prompts become citable authority
- dikwc — the Data→Information→Knowledge pipeline the cards sit in