II.
Page JSON
Structured · livepage:library-research
Research Specialization (Library) json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:library-research",
"_kind": "Page",
"_file": "wiki/library/research.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"title": "Research Specialization (Library)",
"displayName": "Research Specialization (Library)",
"slug": "library/research",
"articlePath": "wiki/library/research.md",
"article": "\n# Research Specialization\n\nProcesses for systematic research analysis, standards comparison auditing, and extraction verification, plus a flagship end-to-end research-publication pipeline that composes the scanner point-tasks below.\n\n## Processes\n\n- **research-publication-workflow.js** — Flagship end-to-end research pipeline: question framing -> plan -> parallel source gathering (composing the five scanner point-tasks below as lane playbooks) -> adversarial claim verification with re-fetched citations -> cited synthesis -> policy-gated publication. Deepest kip-librarian integration (kind `research`).\n- **standards-gap-audit.js** — Generic gap audit process for standards research documents. Audits research/comparison documentation against source extraction text using configurable failure pattern categories.\n- **evangelist.js** — Evangelist persona point-task: scans recent project activity (commits, PRs, docs, releases, benchmarks), filters for marketable novelties, and opens an evangelist report issue per item.\n- **novelties-scanner.js** — Novelties Scanner persona point-task: detects, analyzes, and reports on novel innovations, emerging trends, and breakthrough developments.\n- **patentable-novelties.js** — Patentable Novelties persona point-task: extends the novelties scanner with patent-potential assessment and structured invention disclosures.\n- **vendor-researcher.js** — Vendor-researcher persona point-task: discovers candidate vendors, analyses them in parallel against criteria, and produces a comparison and recommendation report.\n- **news-intelligence-pipeline.js** — End-to-end sourcing + intelligence pipeline (folded in from the former sourcing/ specialization): discover -> monitor -> dedupe -> filter signal -> per-portfolio impact assessment -> synthesize -> route alerts -> track follow-through. The former path `specializations/sourcing/news-intelligence-pipeline.js` remains as a header-only `@deprecated` alias that re-exports this file.\n\n## Usage\n\n```js\nimport { process } from './standards-gap-audit.js';\n\nconst result = await process({\n documents: [\n { name: 'Comparison Doc', path: '/path/to/comparison.md' },\n { name: 'Engineering Changes', path: '/path/to/changes.md' }\n ],\n extractionFile: '/path/to/extraction.txt',\n extractionDir: '/path/to/extraction/',\n // Optional: custom gap patterns and fix instructions\n gapPatterns: [...],\n fixInstructions: {...},\n domainContext: 'Steel design standard comparison'\n}, ctx);\n```\n",
"documents": [
"specialization:research"
]
},
"outgoingEdges": [
{
"from": "page:library-research",
"to": "specialization:research",
"kind": "documents"
}
],
"incomingEdges": [
{
"from": "page:index",
"to": "page:library-research",
"kind": "contains_page"
}
]
}