Pack
A pack is a named set of genres, workflows, library-wide rules and journal kinds for one kind of work. Switching it on in the charter adds them to the whole library and rewrites nothing.

The core genres suit any library. A pack adds what one kind of work needs: the knowledge-base pack keeps sources and readings apart, and the lab pack gives every measured number one home. Several packs on at once still make one library, with one search and one graph.

Layers over the core

folio ships two packs. This library has both on. Switch each off and on, and watch what the library offers for new work. The core stays, and so do the skills on top.

Switched on
The seven skillsthe same in every setting

Read

The charter, every genre and every workflow that is on, each time they start.

Never change

A pack brings no skill. The run skill follows its workflows; write follows its cards.

labmeasured workonoff

Genres

question, protocol, result, claim, report

Workflows

record-a-result, write-a-report

Rules

uncited-number, cites-superseded

Journal kinds

lock, run, kill, instrument, pivot

knowledge-basereading and learningonoff

Genres

source, reading, survey

Workflows

ingest, quiz

Rules

unverified-identifier

Journal kinds

None of its own.

corealways there

Genres

concept, note, entry, map, guide, project, journal, paper

Workflows

None. A library adds its own.

Rules

The gate checks only. No library-wide rule.

Journal kinds

decision, lesson, correction, retraction

Off hides a pack's genres and workflows from new work. Documents already written in its genres stay valid, and its rules stop running.

Each pack sits on the core without changing it: a pack's genres have names no other genre uses, and a pack never redefines a core genre.

What switching one on does

It adds

Its genres, workflows, rules and journal kinds, to the whole library at once. The charter lists it under packs:, and the configure skill records the change in the journal.

It rewrites nothing

No existing document is changed. A pack's rules can flag documents written before it was on, such as a number with no result to cite; the organise skill proposes the fixes.

Where packs come from

The trap: expecting a pack to bring new skills. A pack is data only. The same skills read its genres and follow its workflows, so a new pack never needs a new skill.

Related

Each pack adds genres under names no other genre uses; it never redefines a core one.

Its rules at the gate

A pack's rules are checks the gate runs across the whole library while the pack is on. A library's own pack can only combine checks the gate already has.