Paper build to LaTeX chapters
Render a paper’s content objects to LaTeX chapters: load the paper manifest, resolve its chapters and blocks, render, validate the LaTeX AST, and write the chapter files. With no manifest it builds the folio’s only paper, and refuses — naming them — when there are several or none.
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-validation
Source: folio-assistant-sci/skills/content/folio-paper-adapter/content-validation.md.
Also satisfied by: content-manifest-validate.
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 | paperManifest | RepoPath | The paper’s <paper>.ts manifest; absent, the folio’s single paper. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. | |
| in | outDir | RepoPath | Where to write the chapters; absent, chapters/ at the content root. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. | |
| out | chapters | RepoPath | One .tex per chapter under the output directory. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. |
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 cat content:build.cat content:buildrunsbun run cat-harness-tools/pipeline/build.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/paper-latex-build/paper-latex-build.ts | |
| script | cat-harness-tools/pipeline/build.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/paper-latex-build.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/paper-latex-build.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": "paper-latex-build",
"title": "Paper build to LaTeX chapters",
"description": "Render a paper's content objects to LaTeX chapters: load the paper manifest, resolve its chapters and blocks, render, validate the LaTeX AST, and write the chapter files. With no manifest it builds the folio's only paper, and refuses — naming them — when there are several or none.",
"install": {
"none": true
},
"invoke": {
"shell": "bun run cat content:build"
},
"io": {
"inputs": [
{
"name": "paperManifest",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "The paper's `<paper>.ts` manifest; absent, the folio's single paper.",
"required": false,
"arg": {
"positional": 0
}
},
{
"name": "outDir",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "Where to write the chapters; absent, `chapters/` at the content root.",
"required": false,
"arg": {
"flag": "--out-dir"
}
}
],
"outputs": [
{
"name": "chapters",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "One `.tex` per chapter under the output directory."
}
]
},
"satisfies": [
"content-validation"
],
"requirements": {
"runtime": [
"bun"
],
"network": false
}
}