aboutsummaryrefslogtreecommitdiff
path: root/lib/kernel/overlay.ml
diff options
context:
space:
mode:
authorLukasz Kasprzak <lukas@labunix.xyz>2026-08-13 21:18:58 +0200
committerLukasz Kasprzak <lukas@labunix.xyz>2026-08-13 21:18:58 +0200
commit72b19098905cd609d87783f6e68311de4f1b61a0 (patch)
tree608eaf6bcc46d9dbda0a6dd3a830a5967b201bfa /lib/kernel/overlay.ml
parentcbf6826edc77e3ad5a813237bae27e367221452c (diff)
downloadcolitur-72b19098905cd609d87783f6e68311de4f1b61a0.tar.gz
colitur-72b19098905cd609d87783f6e68311de4f1b61a0.zip
docs: a confidence raised while its revisit trigger was deleted
Five follow-ups from the fix-round re-review, none touching a computed result. M20's note had said "moderate-high, not certain" with a specific revisit trigger attached. The fix round raised the label to "near-certain" and deleted the trigger in the same edit. Upgrading a confidence while removing the condition that would lower it again is the one move this record must not make, so the trigger is restored alongside the higher label: no primary text anywhere names the Major Litanies in a Mass-orations-count worked example, only the general II-class-Sunday rule twice over. RG 434(b) closes the Office-shaped doubt and nothing further. "WORD-IDENTICAL" overstated the relation between RG 111(b) and n. 434(b). Only the trailing "quae tamen omittitur si commemoratio privilegiata facienda sit" is verbatim in both; the openings differ, n. 434(b) recasting the rule into the orations register. The claim was self-refuting -- both texts are quoted adjacent to it -- and the argument never depended on it. Now "identical in its operative clause". And n. 434 is not "a different part of the same document": the running heads put RG 111 under Rubricae generales and n. 434 under Rubricae generales Missalis Romani, two distinct corpora bound in one volume, which is the entire force of the corroboration. The code comment had understated its own point. Also corrects the register's LT line range for n. 434(b) (3574-3576, not 3564-3570; the (b) clause is not in the cited range), and records in calendar.ml the diagnostic that channel (3) trades away: a rite whose transfer_target names a date its own disposition omits used to raise a loud, mislabelled Validate failure and is now silent at the origin. The kernel cannot distinguish that from a deliberate omission without rite knowledge it must not have, so accepting it is right -- but the signal is gone, and that should be written down rather than discovered later.
Diffstat (limited to 'lib/kernel/overlay.ml')
0 files changed, 0 insertions, 0 deletions