Development record
The assembled input for a real reading of this repository is about 9.8 MB at every position, roughly 2.45 million tokens, so no reading can be handed one. Measured by running the shipped assembler over the tree at a real commit: widening 9808456 bytes across 951 items, entailment 10156762 across 1297, comparative and detection the same as widening, with the largest single item at 280242 bytes. Field projection works and is not the problem: 104 of the 951 items are projected to a named field and 847 travel whole, so the whole-file rows dominate by two orders of magnitude. The evals cannot see this because they run over a miniature fixture repository of about thirty files, which is the right corpus for asserting a firewall and the wrong one for asserting that the artefact fits anywhere. Nothing in the record states a size budget for the assembled input, and no criterion measures one, so the instrument can be entirely correct and still undeliverable. The instrument has never been run, which is how this survived thirteen intents.
The assembled input for a real reading of this repository is about 9.8 MB at every position, roughly 2.45 million tokens, so no reading can be handed one. Measured by running the shipped assembler over the tree at a real commit: widening 9808456 bytes across 951 items, entailment 10156762 across 1297, comparative and detection the same as widening, with the largest single item at 280242 bytes. Field projection works and is not the problem: 104 of the 951 items are projected to a named field and 847 travel whole, so the whole-file rows dominate by two orders of magnitude. The evals cannot see this because they run over a miniature fixture repository of about thirty files, which is the right corpus for asserting a firewall and the wrong one for asserting that the artefact fits anywhere. Nothing in the record states a size budget for the assembled input, and no criterion measures one, so the instrument can be entirely correct and still undeliverable. The instrument has never been run, which is how this survived thirteen intents.
Grounds
- pursued: we expect a declared window per entry, re-measured by a dry-run eval on every committed change, to keep the assembled input deliverable, because the size defect reached release only because nobody measured; an entry that passes its eval and still overflows the reader it was calibrated for by more than the divisor's recorded spread would show it wrong.
Frontmatter
| id | iss-2608311501186646 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | critical |
.abcd/work/issues/resolved/iss-2608311501186646-the-assembled-input-for-a-real-reading.md
open on GitHub ↗ · commit history ↗
mentions6
- adr-58A reading is commissioned about something, so the invocation takes a scope
- dcn-26083100000000142026-08-31 — Degrade itd-185's four semantic supply-regime signatures
- itd-196A capability is rehearsed end to end before it ships, over a real tree, in a throwaway snapshot
- itd-198An assembly reports what it would cost before a reading is commissioned
- itd-199A reading is about something narrower than everything, and its scope is a committed, adjustable choice
- itd-2609020625400445A committed preset declares the window it was calibrated for, and the record holds every preset to its declaration