doxa-life/doxa-maps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

check:gospel-internet derives the sub-ladder counts from the table

Browse source 
The OR-within-key assertion compared with typed numbers (57 + 806), which
break whenever the gospel pools are corrected (one is: 806 -> 518). It now
checks the rule against the table's own coverage report.
This commit is contained in:
Doxa Maps 2026-09-27 18:57:56 +00:00
parent 9296aa9cc6
commit 6e41ef9fda
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
plugin-designs/gospel-internet/scripts/check-gospel-internet-model.mjs
View file

@ -64,7 +64,10 @@ bus.setFilter('access_detail', ['read', 'hear'])
const or = M.filterRows(rows, bus).length
bus.setFilter('access_detail', 'read'); const a = M.filterRows(rows, bus).length
bus.setFilter('access_detail', 'hear'); const b = M.filterRows(rows, bus).length
ok(or === a + b && or === 57 + 806, `read|hear = ${or} = read ${a} + hear ${b}`)
// the expected counts come from the table's own coverage report, not typed numbers: the sub-ladder moves
// whenever the gospel pools are corrected (it did, 2026-09-27), and the rule under test is OR-within-key
const cov = doc.meta.coverage.by_access_detail
ok(or === a + b && a === cov.read && b === cov.hear, `read|hear = ${or} = read ${a} + hear ${b} (the table's own ${cov.read} + ${cov.hear})`)
bus.clearFilters()
// 4. cascade