Code: folio-assistant-sci

folio-assistant-sci · 5 declared code directories · Files open on GitHub at the commit this site was built from.

templates/ folio-templates

The PAPER profile of the files `folio_init` writes into a new folio: `paper/` holds the Lean build, lake-cache restore and blueprint workflows and the `.github/scripts` they call, written into a paper folio after the `document/` profile the tools layer keeps. Moved here from cat-harness-tools `templates/paper/` (move M11, folio-assistant#2598; owner 2026-10-23): only a paper folio is given them, and the paper profile is this layer's. The id is the tools layer's `folio-templates`, so this directory is a member of that subgraph and `init-folio` finds it by id across the checkout, never by a path naming this layer. `{{assistant}}`, `{{folio}}`, `{{platform_git}}` and `{{platform_repo}}` are substituted at write time. Declared `code`: executable sources whose target is another repository. `dependents: skip` -- a folio inherits them through `folio_init`, not by owning a copy. Declared WITH its files, per bean dh4f.

14 files

adapters/ sci-adapters

The PAPER content adapter — `PaperContentAdapter` and its Lean tool registrar. It arrived here 2026-09-30 (bean y5si, step 1 of 2 on the owner's Option A ruling on issue #1558), and the destination was not a judgement made at the time: `cat-harness/src/builtin-adapters.ts` already declared this adapter `layer: "sci"`, and `cat-harness/scripts/partition/instance-rules.ts` already listed the prefix `adapters/paper/` in its `repo: "sci"` block. Two existing machine-readable classifications that the DIRECTORY had simply never matched; the directory caught up with them. This is the first EXECUTABLE TypeScript this instance holds beyond `contributions.ts`, which is why `tsconfig.json`'s `include` gained `folio-assistant-sci/adapters/**/*.ts` in the same commit as the move — bean `lvoa` measured what happens when it does not: a file crossing an instance boundary leaves the typecheck program and no gate reports a shrinking one. `dependents: skip` because a dependent gets its adapter by DECLARING a `contentType`, resolved through `BUILTIN_ADAPTERS` by variable path, rather than by inheriting this directory to scan. `adapters/document/` is NOT here and is not coming in this change: it is step 2, and moving it alongside is what takes the instance-boundary import axis through 16 instead of leaving it at 2.

25 files

scripts/ sci-scripts

Tests that hold the harness's code against what this instance owns or contributes: its paper processes and decision tables, its pipeline plugins and contributed checkers. The code under test is imported down from cat-harness. Also the Lean cache service and its tests: `lake-cache.sh` (the `lean-cache` tool), `reseed-lean-cache.sh`, `lake-cache-fetch.sh`, `lake-cache-produce.py`, `lake-cache-fetch-multi.py` and their `.bat` entry points, moved here from cat-harness-tools `scripts/` (folio-assistant#2598; owner 2026-10-23, "C ok"): only a Lean folio runs them, and the `lake-cache` kind is this layer's. The cache branch family they read and write keeps its name, `cat/folio-assistant-sci/lake-cache/<pkg>` (owner, 2026-10-02).

31 files

test/ cat-harness-tools-tests

Tests of the code this layer holds, moved with their subjects so the harness keeps no test importing upward into this layer: `composition-roots` (the declared tool groups and route mounting) and `mcp-graph-tools`.

58 files

pipeline/ cat-harness-tools-pipeline

The content pipeline — build, render, QA checkers and generators over a folio's content graph — moved here from `cat-harness/content/pipeline/` by bean `70lx` (stage 1a). Its QA script sidecars stayed in the harness, under `test/results/script-sidecars/`, because they are the harness's QA state.

13 files

Instances holding code

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev