R2 — the acceptance criterion contains a figure marked TBD #46

Open
opened 2026-09-05 16:20:21 +00:00 by dtourolle · 1 comment
Owner

R2 — efficient display of huge RAW libraries. Its acceptance criterion contains the literal string "(figure TBD)".

What is undefined

  • The scroll velocity below which no cell may render as a placeholder — the "(figure TBD)".
  • The prefetch margin.
  • The cache-hit rate.

No figure is stated anywhere in the tree, and neither of the latter two quantities is measured.

What is known

TD-2 and TD-3 both describe the thumbnail path falling short of this in ways that were measured. So this is not a case of "probably fine, unverified" — there is evidence of a gap, against a criterion too vague to say how large it is.

R2 was deliberately left untagged for that reason: the machinery is substantial and the criterion is unmet and partly undefined.

Acceptance

  • State the scroll-velocity figure, the prefetch margin and the target cache-hit rate in requirements.md.
  • Measure the latter two — the catalog bench harness (#42) is the natural home.
  • Reconcile with TD-2 and TD-3: either they close, or they are restated against the now-stated figure.

Related

#45 — R1 fails the same way. A requirement whose threshold was never chosen and a target nothing measures fail identically: not by being wrong, but by being unfalsifiable.

See docs/outstanding.md §9.

**R2 — efficient display of huge RAW libraries.** Its acceptance criterion contains the literal string **"*(figure TBD)*"**. ## What is undefined - The scroll velocity below which **no cell may render as a placeholder** — the "(figure TBD)". - The prefetch margin. - The cache-hit rate. No figure is stated anywhere in the tree, and neither of the latter two quantities is measured. ## What is known TD-2 and TD-3 both describe the thumbnail path **falling short of this in ways that were measured**. So this is not a case of "probably fine, unverified" — there is evidence of a gap, against a criterion too vague to say how large it is. R2 was deliberately left untagged for that reason: the machinery is substantial and the criterion is unmet and partly undefined. ## Acceptance - [ ] State the scroll-velocity figure, the prefetch margin and the target cache-hit rate in `requirements.md`. - [ ] Measure the latter two — the catalog bench harness (#42) is the natural home. - [ ] Reconcile with TD-2 and TD-3: either they close, or they are restated against the now-stated figure. ## Related #45 — R1 fails the same way. *A requirement whose threshold was never chosen and a target nothing measures fail identically: not by being wrong, but by being unfalsifiable.* See `docs/outstanding.md` §9.
dtourolle added the unmet-requirementsize:Sperformancedecision labels 2026-09-05 16:20:21 +00:00
Author
Owner

Fails the same way as #45. Measurement home is #42 s harness. Reconcile TD-2 and TD-3 with whatever figure is stated.

**Fails the same way as** #45. Measurement home is #42 s harness. Reconcile TD-2 and TD-3 with whatever figure is stated.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dtourolle/DarkRoom#46