Documents & policy guidance
This page is generated from docs/source/concepts-document-content-type/ — each section below links to its own source.
Documents & policy guidance
Skill package: folio-document-adapter ·
Adapter: document ·
Guide: Writing a document
Structured prose: health-policy guidance (an L1 guideline, say), a standard, a report, a handbook, a book chapter. Everything a paper is, minus the formal layer — and therefore minus the two toolchains that serve it.
- Source model — the same tree of typed blocks as a paper, restricted to
the kinds whose content is prose rather than a formal claim:
prose,example,remark,algorithm,simulator,equation,diagram,table. - Rendering —
document_render_mdassembles the folio into one Markdown file;document_render_htmlanddocument_render_pdftake it through pandoc. The PDF path uses an HTML engine (weasyprint, prince, wkhtmltopdf) and never falls back tolatexmk, so “no TeX required” stays true rather than becoming true-until-someone-has-TeX-installed. - Enforcement —
content_profile_checkrejects a math kind, aleanfield or a.leansibling, and runs on everycontent_validate.
Relevant skill schemas:
document-authoring,
document-structure,
normative-statements,
document-publishing.
BPMN 2.0 source · full-size SVG
Carrying a normative statement
A recommendation, requirement or rule is the block readers cite and
implementers trace to. It wants a label, a stable identity and a place in the
dependency graph — everything a theorem has — and it is emphatically not a
theorem, because nothing proves it.
There is no first-class recommendation block kind. Today the carrier is a
prose block with a label and a title; the
normative-statements
skill states the convention and its limits. Earlier guidance in
document-intake mapped guideline recommendations onto definition — that
predates this content type and is wrong for a document folio, where
definition is a math kind whose lean field is required.