olijboyd commited on
Commit
0529cce
·
verified ·
1 Parent(s): 8f45e4f

The TomeVault Instruction Corpus — edition 2026-07

Browse files
Files changed (3) hide show
  1. README.md +19 -6
  2. aggregate.json +0 -0
  3. instruction-files.parquet +2 -2
README.md CHANGED
@@ -20,7 +20,7 @@ configs:
20
 
21
  De-identified structural measurements of AI instruction files (CLAUDE.md, AGENTS.md, SKILL.md, .cursorrules and related conventions).
22
 
23
- Edition 2026-07. 229,375 files. Schema version 1.0.0. Licensed CC BY 4.0.
24
 
25
  ## What this is
26
 
@@ -37,7 +37,7 @@ ruleset thinks an agent asked to load it would get what the author intended.
37
  It contains no file contents, no owner names, no repository names and no URLs.
38
  Every measurement in it is reproducible from the method described below.
39
 
40
- One row per instruction FILE INSTANCE that the pipeline has fetched, converted, and RETAINED THE BODY OF. A row is a file, NOT a repository and NOT an owner: one repository commonly contributes many rows, and a widely-forked file appears once per fork. Any count derived from this table is a count of files unless it explicitly de-duplicates. Two exclusions narrow it further: rows whose deterministic security grade is 'fail', and rows the pipeline tracks without a stored body, which cannot be measured and are therefore absent rather than counted as passing. The retained-body requirement is the largest of the three filters, so this is a measurable subset of what we track and not a census of it.
41
 
42
  ## Source and updates
43
 
@@ -100,13 +100,13 @@ format. Every measurement in this release comes from deterministic rulesets, not
100
  from a language model, so the same input always produces the same row.
101
 
102
  Loadability findings come from the same ruleset our product runs, version
103
- `loadability-v1.1`. The `has_broken_reference` column is
104
  true when a file fires either the stale-path check or the reference-portability
105
  check, meaning it points at something that has gone or that will not travel with
106
  the file when it moves.
107
 
108
  Retired-model flags come from a hand-curated list of model identifiers and their
109
- lifecycle status, last updated `2026-06-23`. Only
110
  identifiers marked deprecated, superseded or retired are flagged. Matching is
111
  whole-token, so `gpt-4` does not match inside `gpt-4o`.
112
 
@@ -114,8 +114,13 @@ Licence classification reuses the same policy module that gates our own
114
  ingestion, so the compliance figures here and our enforcement are definitionally
115
  the same thing.
116
 
117
- `aggregate.json` in this release carries the corresponding month's headline
118
- metrics computed over the same snapshot.
 
 
 
 
 
119
 
120
  ## Known biases
121
 
@@ -135,6 +140,14 @@ repositories reaches. Private repositories, self-hosted platforms and files
135
  inside archives are absent, and there is no reason to assume the absent
136
  population resembles this one.
137
 
 
 
 
 
 
 
 
 
138
  **Security-failing files are excluded.** Rows whose deterministic security grade
139
  is `fail` were removed before export. The remaining population is therefore
140
  slightly cleaner than the raw corpus.
 
20
 
21
  De-identified structural measurements of AI instruction files (CLAUDE.md, AGENTS.md, SKILL.md, .cursorrules and related conventions).
22
 
23
+ Edition 2026-07. 229,720 files. Schema version 1.0.0. Licensed CC BY 4.0.
24
 
25
  ## What this is
26
 
 
37
  It contains no file contents, no owner names, no repository names and no URLs.
38
  Every measurement in it is reproducible from the method described below.
39
 
40
+ One row per instruction FILE INSTANCE the pipeline has fetched and converted. A row is a file, NOT a repository and NOT an owner: one repository commonly contributes many rows, and a widely-forked file appears once per fork. Any count derived from this table is a count of files unless it explicitly de-duplicates. Files whose deterministic security grade is 'fail' are excluded. Each file is measured once, when first seen, and the measurements are retained permanently, so a file stays in the population for every later edition even after we discard its body for storage reasons. Files first crawled before that retention policy began are absent, which makes early editions a floor rather than a census.
41
 
42
  ## Source and updates
43
 
 
100
  from a language model, so the same input always produces the same row.
101
 
102
  Loadability findings come from the same ruleset our product runs, version
103
+ `None`. The `has_broken_reference` column is
104
  true when a file fires either the stale-path check or the reference-portability
105
  check, meaning it points at something that has gone or that will not travel with
106
  the file when it moves.
107
 
108
  Retired-model flags come from a hand-curated list of model identifiers and their
109
+ lifecycle status, last updated `2026-07-31`. Only
110
  identifiers marked deprecated, superseded or retired are flagged. Matching is
111
  whole-token, so `gpt-4` does not match inside `gpt-4o`.
112
 
 
114
  ingestion, so the compliance figures here and our enforcement are definitionally
115
  the same thing.
116
 
117
+ `aggregate.json` carries the headline metrics from snapshot
118
+ `2026-07`, which is the measurement run this edition is
119
+ built from. The two files answer different questions and do not share a
120
+ denominator: the parquet is one row per retained-body file instance, while each
121
+ metric in the aggregate declares its own population in its own `population`
122
+ field. Read a figure with the population beside it, and do not reconcile a count
123
+ from one against a count from the other.
124
 
125
  ## Known biases
126
 
 
140
  inside archives are absent, and there is no reason to assume the absent
141
  population resembles this one.
142
 
143
+ **Early editions are a floor, not a census.** Each file is measured once, when
144
+ first seen, and those measurements are kept permanently. Files first crawled
145
+ before that retention began were never measured and cannot be recovered without
146
+ re-fetching them, so they are missing. Counts will therefore rise across the
147
+ first few editions partly because coverage is filling in, not only because the
148
+ ecosystem is growing. Treat early growth in absolute counts with suspicion and
149
+ prefer the proportions, which are far less affected.
150
+
151
  **Security-failing files are excluded.** Rows whose deterministic security grade
152
  is `fail` were removed before export. The remaining population is therefore
153
  slightly cleaner than the raw corpus.
aggregate.json CHANGED
The diff for this file is too large to render. See raw diff
 
instruction-files.parquet CHANGED
@@ -1,3 +1,3 @@
1
  version https://git-lfs.github.com/spec/v1
2
- oid sha256:bd463168ea58b91ad26527b2b468e198b203f08dd3aefbdf487f0da273b3a211
3
- size 2382649
 
1
  version https://git-lfs.github.com/spec/v1
2
+ oid sha256:1c14950d014279af19d1af51d2725c9617c15a0ea6d5dc96b5e0772510b84741
3
+ size 1690790