L1 extraction → statement lists
The smart-base collector for core’s publish-extracted-statements step: an l1-extraction directory’s authored L1 sources (recommendations: rows) and scenario-candidate graphs (user-scenario nodes whose evidence.location names a row), written as folio-extracted-statements/v1 lists, each statement with the library entry its L1 source names and the page it was read from. Core’s statements:pages then renders them with links to the entry and section.
| Tool | l1-statement-lists |
| IRI | http://smart.who.int/base/tools/l1-statement-lists.jsonld |
| part of | http://smart.who.int/base/smart-base.jsonld |
| type | https://litlfred.github.io/cat-harness/v0/ns/Tool |
| declared by | smart-base |
| invoked | shell |
| qa | qa-reports |
Skills it satisfies
A skill states the capability; this Tool is one way to exercise it. Each skill’s declared input and output contract follows, where it has one.
publish-extracted-statements
The standard step of adding source documents to a folio’s working artifact: every statement extracted from a library source is published readably in the artifact’s own pages AND in the shared extraction viewer, each with a link to its library entry and to the section it came from, and CI fails when the generated pages are stale. Generic across content types; each type’s adapter says only how its pages look. Executable form: processes/library/publish-extracted-statements.bpmn.
Source: folio-assistant-core/skills/library/ingestion/publish-extracted-statements.md.
Also satisfied by: publish-extracted-statements.
The skill declares no I/O contract (schemas/skills/publish-extracted-statements/{input,output}.schema.json).
Inputs and outputs
Each port names a shared type by IRI, so two Tools for one skill can be checked for interchangeability.
| port | type | required | description | constraint | |
|---|---|---|---|---|---|
| in | dir | RepoPath | yes | An l1-extraction directory. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. |
| in | out | RepoPath | yes | Where the lists go. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. |
| in | instance-root | RepoPath | The instance the evidence locations are relative to; the working directory when absent. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. | |
| in | check | Flag | Compare instead of writing: exit 1 when a list is stale. | boolean · A boolean switch — projects to a bare flag, with no value word | |
| out | lists | RepoPath | <stem>.recommendations.json per L1 source and <stem>.scenarios.json per scenario graph. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. |
Processes and tasks
Steps this Tool can carry out, because each names a skill it satisfies:
| process | step | lane | via skill |
|---|---|---|---|
| L3 FHIR IG pipeline | Publish extracted statements | Build pipeline — SUSHI · validator · IG Publisher | publish-extracted-statements |
| Authoring a document | Publish extracted statements | Build pipeline | publish-extracted-statements |
| L1 document ingestion — a document to the L1 source knowledge graph | Publish the extracted statements | Ingestion Engine (agent, runs unattended) | publish-extracted-statements |
| Publish extracted statements with source links | Collect each statement with its source section | Ingestion Engine (agent, runs unattended) | publish-extracted-statements |
| Publish extracted statements with source links | Render them in the artifact’s own pages | Ingestion Engine (agent, runs unattended) | publish-extracted-statements |
| Publish extracted statements with source links | Publish them in the shared viewer | Ingestion Engine (agent, runs unattended) | publish-extracted-statements |
| Publish extracted statements with source links | Check pages are current, links resolve | Ingestion Engine (agent, runs unattended) | publish-extracted-statements |
| Authoring a paper | Publish extracted statements | Build pipeline | publish-extracted-statements |
| DTH authoring | Publish extracted statements | Business analyst | publish-extracted-statements |
| L2 DAK authoring | Publish extracted statements | Business analyst | publish-extracted-statements |
How it is deployed and reached
- Command line. From the repository root:
bun run smart-base/scripts/l1-statement-lists.ts. - GitHub Actions. No workflow in this checkout runs its command.
As an API: its operation in the OpenAPI document and the MCP tool list of its layer.
| install | none |
| when to choose it | |
|---|---|
| when | An L1 extraction’s statements are to be published, with links to their sources, in the folio’s own pages and the shared viewer. |
| limits | An L1 source that names no library entry is refused. A row’s page is its first page. A node citing a file that is not an L1 source (a persona citing the mapping) is not a statement and is skipped. |
| cost | Seconds, no network. |
What it is made of
| role | file | |
|---|---|---|
| script | smart-base/scripts/l1-statement-lists.ts |
Linked data
The Tool is published as its own JSON-LD document at its IRI, http://smart.who.int/base/tools/l1-statement-lists.jsonld, partOf its layer’s document. The node below is the definition this page was drawn from, and is embedded in the page as application/ld+json.
{
"@context": "http://smart.who.int/base/smart-base.context.jsonld",
"@id": "http://smart.who.int/base/tools/l1-statement-lists.jsonld",
"@type": "https://litlfred.github.io/cat-harness/v0/ns/Tool",
"partOf": "http://smart.who.int/base/smart-base.jsonld",
"name": "l1-statement-lists",
"title": "L1 extraction → statement lists",
"description": "The smart-base collector for core's `publish-extracted-statements` step: an `l1-extraction` directory's authored L1 sources (`recommendations:` rows) and scenario-candidate graphs (`user-scenario` nodes whose `evidence.location` names a row), written as `folio-extracted-statements/v1` lists, each statement with the library entry its L1 source names and the page it was read from. Core's `statements:pages` then renders them with links to the entry and section.",
"install": {
"none": true
},
"invoke": {
"shell": "bun run smart-base/scripts/l1-statement-lists.ts"
},
"io": {
"inputs": [
{
"name": "dir",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "An `l1-extraction` directory.",
"required": true,
"arg": {
"flag": "--dir"
}
},
{
"name": "out",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "Where the lists go.",
"required": true,
"arg": {
"flag": "--out"
}
},
{
"name": "instance-root",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "The instance the evidence locations are relative to; the working directory when absent.",
"required": false,
"arg": {
"flag": "--instance-root"
}
},
{
"name": "check",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Flag",
"description": "Compare instead of writing: exit 1 when a list is stale.",
"required": false,
"arg": {
"flag": "--check"
}
}
],
"outputs": [
{
"name": "lists",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "`<stem>.recommendations.json` per L1 source and `<stem>.scenarios.json` per scenario graph."
}
]
},
"satisfies": [
"publish-extracted-statements"
],
"selection": {
"when": "An L1 extraction's statements are to be published, with links to their sources, in the folio's own pages and the shared viewer.",
"limits": "An L1 source that names no library entry is refused. A row's page is its first page. A node citing a file that is not an L1 source (a persona citing the mapping) is not a statement and is skipped.",
"cost": "Seconds, no network."
}
}