Authored L1 → verbatim against transcriptions and image narratives

Check authored L1 (*.l1.yaml, the measles pattern) for a source with no usable text layer: each statement must be verbatim in the image narrative (images.json) or the transcription block it names; every transcription word (digits aside) must be corroborated by the entry’s text layer unless listed under inspectionOnly; keys must be unique.

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.

transcription-verbatim

Check L1 authored from pictures (a schedule poster, a slide deck: a source with no usable text layer) against the image narratives and transcriptions it names: every statement verbatim in one of them, every transcription word corroborated by the entry’s text layer unless listed under inspectionOnly, and unique keys. A step of recommendation-extraction, in place of recommendation-candidates when that step found no normative sentence; the l1-transcription-verbatim Tool satisfies it.

Source: smart-base/L1/skills/smart-l1/transcription-verbatim.md.

input [1..1]output [1..1]transcription-verbatim«skill»transcription-verbatiminput : TranscriptionVerbatimInput [1..1]output : TranscriptionVerbatimOutput [1..1]TranscriptionVerbatimInput«json-schema»TranscriptionVerbatimInputdir : string [1..1]TranscriptionVerbatimOutput«json-schema»TranscriptionVerbatimOutputreport : string [1..1]

input — smart-base/L1/schemas/skills/transcription-verbatim/input.schema.json

fieldtyperequireddescription
dirstringyesThe directory of authored *.l1.yaml; each names its library entry in graph.source.entry.

output — smart-base/L1/schemas/skills/transcription-verbatim/output.schema.json

fieldtyperequireddescription
reportstringyesOne summary line per file and one FINDING line per failure. Exit 0 clean, 1 findings, 2 nothing to check (not a pass).

Inputs and outputs

Each port names a shared type by IRI, so two Tools for one skill can be checked for interchangeability.

porttyperequireddescriptionconstraint
indirRepoPathyesThe directory of authored *.l1.yaml; each names its library entry in graph.source.entry.string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments.
outreportTextOne summary line per file and one FINDING line per failure. Exit 0 clean, 1 findings, 2 nothing to check (not a pass).string · A short single-line human string. Not admissible as a command-line argument.

Processes and tasks

No process step names a skill this Tool satisfies.

How it is deployed and reached

  • Command line. From the repository root: bun run smart-base/L1/scripts/l1-transcription-verbatim.ts --dir <dir of *.l1.yaml> [--root <repo>].
  • 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.

installnone
runtimebun
networkno
when to choose it
whenThe L1 was authored from inspected images or transcriptions because l1-recommendation-candidates found no normative sentence in the entry’s text layer (a poster, a slide deck).
limitsVerbatim is checked after NFKC normalisation with private-use glyphs dropped, so digits a text layer maps to private-use code points rest on inspection alone. Whether the transcription reads the picture correctly is the reviewer’s call (bun run cat narratives).
costSeconds, no network.

What it is made of

Linked data

The Tool is published as its own JSON-LD document at its IRI, http://smart.who.int/base/tools/l1-transcription-verbatim.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-transcription-verbatim.jsonld",
  "@type": "https://litlfred.github.io/cat-harness/v0/ns/Tool",
  "partOf": "http://smart.who.int/base/smart-base.jsonld",
  "name": "l1-transcription-verbatim",
  "title": "Authored L1 → verbatim against transcriptions and image narratives",
  "description": "Check authored L1 (`*.l1.yaml`, the measles pattern) for a source with no usable text layer: each statement must be verbatim in the image narrative (`images.json`) or the `transcription` block it names; every transcription word (digits aside) must be corroborated by the entry's text layer unless listed under `inspectionOnly`; keys must be unique.",
  "install": {
    "none": true
  },
  "invoke": {
    "shell": "bun run smart-base/L1/scripts/l1-transcription-verbatim.ts --dir <dir of *.l1.yaml> [--root <repo>]"
  },
  "io": {
    "inputs": [
      {
        "name": "dir",
        "schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
        "description": "The directory of authored `*.l1.yaml`; each names its library entry in `graph.source.entry`.",
        "required": true
      }
    ],
    "outputs": [
      {
        "name": "report",
        "schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Text",
        "description": "One summary line per file and one `FINDING` line per failure. Exit 0 clean, 1 findings, 2 nothing to check (not a pass)."
      }
    ]
  },
  "satisfies": [
    "transcription-verbatim"
  ],
  "requirements": {
    "runtime": [
      "bun"
    ],
    "network": false
  },
  "selection": {
    "when": "The L1 was authored from inspected images or transcriptions because `l1-recommendation-candidates` found no normative sentence in the entry's text layer (a poster, a slide deck).",
    "limits": "Verbatim is checked after NFKC normalisation with private-use glyphs dropped, so digits a text layer maps to private-use code points rest on inspection alone. Whether the transcription reads the picture correctly is the reviewer's call (`bun run cat narratives`).",
    "cost": "Seconds, no network."
  }
}

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev