folio-assistant-core

The content layer. This instance defines what a folio is: the content-object model, the block kinds, the content adapters (document and paper) and the profiles nested inside them, and the folio graph typology itself.

Where it sits

It sits on C@T Harness and may import from it. The harness never imports from this layer. bun run cat check:partition:edges reports any edge that runs the wrong way. Instances such as WHO IRIS sit on top of this one. That is why the navbar lists it between them, because the order comes from each declaration’s needs.

What it holds

The declaration folio-assistant-core.json lists every directory and the graph typologies each one holds. The section below is generated from that declaration. It shows the counts and the viewers that are published today.

Folio Assistant Core

What a folio IS — the content-object model, the block kinds, the adapters, and the folio graph typology itself.

declared directories: 31
declared graph typologies: 27
visualisations you can open: 27

Subgraphs — 31 local, 0 remote

local folio-assistant-core-docs folio-assistant-core/docs/ · docs
local folio-assistant-core-translations folio-assistant-core/translations/ · translation-sources
local folio-assistant-core-block-typologies folio-assistant-core/block-kinds/ · block-kinds
local folio-assistant-core-content-adapters folio-assistant-core/content-adapters/ · content-adapters
local folio-assistant-core-validators folio-assistant-core/validators/ · validators
local core-code-lists folio-assistant-core/code-lists/ · code-list
local core-qa-checkers folio-assistant-core/qa-checkers/ · qa-checkers
local core-pipeline-plugins folio-assistant-core/pipeline-plugins/ · pipeline-plugins
local core-pipeline folio-assistant-core/pipeline/ · code
local folio-assistant-core-typologies folio-assistant-core/typologies/ · typologies
local core-schemas folio-assistant-core/schemas/ · schemas, cat-harness
local folios folio-assistant-core/folios/ · folio
local glossary folio-assistant-core/glossary/ · glossary
local core-tools folio-assistant-core/tools/ · tools
local core-adapters folio-assistant-core/adapters/ · code
local core-src folio-assistant-core/src/ · code
local core-scripts folio-assistant-core/scripts/ · code
local core-templates folio-assistant-core/templates/ · code
local core-library folio-assistant-core/library/ · library
local core-methodologies folio-assistant-core/methodologies/ · methodology
local core-skills folio-assistant-core/skills/ · skills
local core-processes folio-assistant-core/processes/ · processes
local qa folio-assistant-core/test/results/ · qa
local memory folio-assistant-core/memory/ · memory
local beans folio-assistant-core/beans/ · beans
local health folio-assistant-core/test/health/results/ · health
local voices folio-assistant-core/skills/voices/ · voices
local defs folio-assistant-core/beans/defs/ · bean-defs
local notes folio-assistant-core/beans/notes/ · bean-notes
local workflows folio-assistant-core/beans/workflows/ · workflow-state
local docs-source folio-assistant-core/docs/source/ · docs

Gaps in this instance's declaration (4)

folio-assistant-core: a viewer is published at /en/cat-harness/uploads/folio-assistant-core/ by cat-harness’s uploads visualiser, which covers none of this instance’s directories. Declare one it covers and the tile links it.
folio-assistant-core: a viewer is published at /en/cat-harness/attestations/folio-assistant-core/ by cat-harness’s attestations visualiser, which covers none of this instance’s directories. Declare one it covers and the tile links it.
folio-assistant-core: a viewer is published at /en/cat-harness/scenarios/folio-assistant-core/ by cat-harness’s scenarios visualiser, which covers none of this instance’s directories. Declare one it covers and the tile links it.
folio-assistant-core: a viewer is published at /en/cat-harness/policies/folio-assistant-core/ by cat-harness’s policies visualiser, which covers none of this instance’s directories. Declare one it covers and the tile links it.

What a folio is made of here

A folio is a set of content objects. Each object is a file triple: a typed manifest, a markdown body and, for a formal claim, a Lean sibling. This layer says which kinds of block exist and what each one must carry. Each kind is a node in the block-kinds/ graph with a required profile, so no kind can go unclassified. The document adapter serves structured prose. The paper adapter extends it with the kinds whose assertion is a formal mathematical claim, typeset through LaTeX.

The rest of the instance supports that model. validators/ names the checks the code provides, one node per graph typology and schema family. glossary/ holds the content vocabulary. methodologies/ holds the authoring methods a folio draws on. processes/ holds the executable BPMN diagrams for the authoring and review work. skills/ holds the instructions an agent loads to carry that work out.

The rule this layer turns on

This repository is the platform, not the content. A folio’s chapters, constants and vocabularies live in that folio’s own repository. If you are about to write subject matter here, you are either in the wrong repository or writing something that belongs in a folio as data.

The instance’s README sets out the scope boundary in full, along with what is still pre-split.