{
  "id": "page:library-shared",
  "_kind": "Page",
  "_file": "wiki/library/shared.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Shared (Cross-Domain Assets) (Library)",
    "displayName": "Shared (Cross-Domain Assets) (Library)",
    "slug": "library/shared",
    "articlePath": "wiki/library/shared.md",
    "article": "\n# Shared (Cross-Domain Assets)\n\n## Overview\n\n`shared/` is the home for cross-domain library assets — skills, and eventually agents and processes, that are useful across many specializations rather than belonging to any single domain. Per the library placement policy, only assets with genuine cross-domain applicability live here.\n\n## Current Contents\n\n| Asset | Type | Description |\n|-------|------|-------------|\n| [skills/kip-librarian](skills/kip-librarian/) | Skill | Canonical kip knowledge-store patterns for any process or agent — recall prior facts before work, assert decisions/gate outcomes as structured facts after work, resolve entities with an explicit model, and invoke the kip CLI Windows-safely |\n\n## Placement Rules\n\n- **Full generic development methodologies** → `library/methodologies/`\n- **Domain-specific assets** → `library/specializations/<domain>/`\n- **Cross-domain assets** (useful across many domains) → `library/specializations/shared/`\n\nWhen in doubt, prefer the most specific home: an asset only moves to `shared/` when it is demonstrably useful across many domains.\n",
    "documents": [
      "specialization:shared"
    ]
  },
  "outgoingEdges": [
    {
      "from": "page:library-shared",
      "to": "specialization:shared",
      "kind": "documents"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:index",
      "to": "page:library-shared",
      "kind": "contains_page"
    }
  ]
}