Programs a library runs
Each method is a program of typed steps over everything that arrives: Jev answers, the frontier names or writes, code counts. What it builds is a structure with its own honest statistics, served at the library’s endpoint.
Graph
Entities (people, works, places, concepts…), declared by a source or found, and the moments that refer to them: questions and answers, mentions, definitions, claims. Each profile is one program of typed steps over what arrives: Jev answers finders on every passage and chooses among the library’s own names; the frontier names only what no option fits; code builds the spans.
Table
Units by questions, reported as indicators with intervals: content analysis. A card publishes a method with its evidence: questions pinned to the Jev model its track record was measured with, a calibration fitted to a named coding standard, its limitations. What it reports is computed when asked, never stored.
emic_living_with_the_bassin@0.1.0Emic living with the bassin
A published method with its evidence.
emic_living_with_the_bassin@0.2.0Emic living with the bassin
A published method with its evidence.
semetko_valkenburg@0.2.0Semetko valkenburg
A published method with its evidence.
Trajectory
Subjects followed through time, with an honest account of what the end of a record means. A subject is a work (one person’s posts, in order), its clock a date on each unit; intervals resample subjects, never observations.
Codebook
A lens and its lineage, with the statistics that show where it is blind: friction, separation, redundancy. The one inductive method: answers in, better questions out.
codebook@1The codebook
The inductive method: a library grows its own questions from its passages, a turn at a time, through a gate.
codebook@1The codebook
The inductive method: a library grows its own questions from its passages, a turn at a time, through a gate.