Content manifest validation
Validate the block manifests under a path against their schemas.
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.
content-validate
Source: cat-harness/skills/authoring/content-lifecycle/content-validate.md.
Also satisfied by: content-graph-build.
input — cat-harness/schemas/skills/content-validate/input.schema.json, https://litlfred.github.io/folio-assistant/cat-harness/skills/content-validate/input.schema.json
| field | type | required | description |
|---|---|---|---|
targetPath | string | yes | Path to content to validate. |
validationRules | string[] | Specific validation rule IDs to run (empty = all applicable). | |
schemaRefs | string[] | Schema files to validate against. | |
stagingLinks | stagingLinks | The staging preview of the work under review, as the request for feedback carried it, so the reviewer opens the changed pages rather than rebuilding links. Rule: cat-harness skills/authoring/content-lifecycle/feedback-deep-links.md. |
output — cat-harness/schemas/skills/content-validate/output.schema.json, https://litlfred.github.io/folio-assistant/cat-harness/skills/content-validate/output.schema.json
| field | type | required | description |
|---|---|---|---|
overallStatus | pass \| warnings \| errors | yes | |
results | object[] | yes | |
stagingLinks | stagingLinks | The staging preview of the work this output asks a person to look at: one deep link per changed page, with the same page on main. Required whenever a preview exists; when it does not, say so in missing. Rule: cat-harness skills/authoring/content-lifecycle/feedback-deep-links.md. |
content-validation
Source: folio-assistant-sci/skills/content/folio-paper-adapter/content-validation.md.
Also satisfied by: paper-latex-build.
The skill declares no I/O contract (schemas/skills/content-validation/{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 | targetPath | RepoPath | A paper or chapter directory; absent, every paper the folio declares. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. | |
| in | strict | Flag | Treat warnings as errors. | boolean · A boolean switch — projects to a bare flag, with no value word | |
| out | issues | Text | One line per issue, with its block and file. Exit 2 means NO FOLIO WAS FOUND — could-not-determine, never valid. | string · A short single-line human string. Not admissible as a command-line argument. |
Processes and tasks
Steps this Tool can carry out, because each names a skill it satisfies:
| process | step | lane | via skill |
|---|---|---|---|
| Review task | Accept, or send back | Editors + authoring agents | content-validate |
| Authoring a document | Check the profile | Build pipeline | content-validate |
| Authoring a document | Validate | Build pipeline | content-validate |
| Content lifecycle | Editing and HCI validation | Editors + authoring agents | content-validate |
| Draft, review and publish | Editing and HCI validation | Editors + authoring agents | content-validate |
| Editing and HCI validation | Schema and constraint checks | Mechanical validation (system) | content-validate |
| Editing and HCI validation | Syntax, spelling and links | Mechanical validation (system) | content-validate |
| Editing and HCI validation | Collate findings into a report | HCI validation pipeline (system) | content-validate |
| Authoring a paper | Validate | Build pipeline | content-validate |
| DTH authoring | Validate the draft | Business analyst | content-validate |
| L2 component edit and review | Run the component’s checker | Authoring agent | content-validate |
| L2 DAK authoring | Assemble and validate the DAK | Business analyst | content-validate |
How it is deployed and reached
- Command line. From the repository root:
bun run cat content:validate.cat content:validaterunsbun run cat-harness-tools/pipeline/validate.ts(declared incat-harness-tools/package.json). - 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 |
| runtime | bun |
| network | no |
What it is made of
| role | file | |
|---|---|---|
| definition | folio-assistant-sci/tools/content-manifest-validate/content-manifest-validate.ts | |
| script | cat-harness-tools/pipeline/validate.ts |
Linked data
The Tool is published as its own JSON-LD document at its IRI, https://litlfred.github.io/folio-assistant/folio-assistant-sci/tools/content-manifest-validate.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": "https://litlfred.github.io/folio-assistant/folio-assistant-sci/folio-assistant-sci.context.jsonld",
"@id": "https://litlfred.github.io/folio-assistant/folio-assistant-sci/tools/content-manifest-validate.jsonld",
"@type": "https://litlfred.github.io/cat-harness/v0/ns/Tool",
"partOf": "https://litlfred.github.io/folio-assistant/folio-assistant-sci/folio-assistant-sci.jsonld",
"name": "content-manifest-validate",
"title": "Content manifest validation",
"description": "Validate the block manifests under a path against their schemas.",
"install": {
"none": true
},
"invoke": {
"shell": "bun run cat content:validate"
},
"io": {
"inputs": [
{
"name": "targetPath",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "A paper or chapter directory; absent, every paper the folio declares.",
"required": false,
"arg": {
"positional": 0
}
},
{
"name": "strict",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Flag",
"description": "Treat warnings as errors.",
"required": false,
"arg": {
"flag": "--strict"
}
}
],
"outputs": [
{
"name": "issues",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Text",
"description": "One line per issue, with its block and file. Exit 2 means NO FOLIO WAS FOUND — could-not-determine, never valid."
}
]
},
"satisfies": [
"content-validate",
"content-validation"
],
"requirements": {
"runtime": [
"bun"
],
"network": false
}
}