Generated from
folio-assistant-core/skills/content/folio-document-adapter/folio-content-profiles.md— do not edit here.
Folio content profiles — document base and paper extension
The harness skill content-profiles
defines why adapters (disjoint code/runtime namespaces) and profiles
(nested vocabulary subsets) are separate axes. For content folios built on
folio-assistant-core, this skill states how the document and paper
profiles instantiate those rules.
1. document is the base; paper extends it
- A
documentfolio is structured prose: policy guidance, a standard, or a technical report (document-structure). - A
paperfolio extendsdocumentwith block kinds whose assertion is a formal mathematical claim (definition,theorem,lemma,proposition,corollary,proof,conjecture), backed by machine-checkable.leansiblings and a TeX pipeline. - Every block kind is a
folio-block-kind/v1node in its owning layer’sblock-kinds/graph with a required two-valuedprofilefield (documentorpaper), from whichBLOCK_KINDS,DOCUMENT_BLOCK_KINDS, andMATH_BLOCK_KINDSinschemas/content/block-kinds.tsare derived.
2. Profile enforcement and TeX-free document rendering
- Profile enforcement (
profile-check.ts): checks on every validation that (1) every block’s kind belongs to the folio’s active profile, and (2) in adocumentfolio, no block carries aleanfield or a.leansibling (even on shared kinds likeremark,example,algorithm, orsimulatorwhere the schema marksleanoptional). - TeX-free document render path:
document_render_{md,html,pdf}assemble the folio to Markdown and drive Pandoc (withweasyprint,prince, orwkhtmltopdffor PDF), never falling back tolatexmk. - Normative statements: carried by
recommendationblocks pernormative-statements, never bydefinition. - Extracted-statement pages: when source documents are added to the
folio’s working artifact, the standard step
publish-extracted-statementspublishes every statement extracted from them, each linked to its library entry and section. The step is the same for every profile; the profile’s adapter decides only how those pages look in its artifact (pages of a document, an appendix of a paper, pages of an implementation guide).