Failure state
The source file INST-INDEX-RERUM-FACIENDARUM.md contains a newly added open item:
But organvm irf stats still reports the old totals immediately afterward:
Total: 715
Open: 384
SYS: 29
Expected from file contents after insertion:
Total: 716
Open: 385
SYS: 30
Why this matters
The IRF CLI is being used as a governance truth source during session closeout. If it silently undercounts new items, operators can incorrectly conclude the registry is synchronized when it is not.
Reproduction
- Add a new
IRF-SYS-* row near the tail of INST-INDEX-RERUM-FACIENDARUM.md.
- Run
organvm irf stats.
- Compare CLI totals to the file contents.
Observed on
- Date: 2026-04-02
- Repo:
meta-organvm/organvm-corpvs-testamentvm
- During closeout of
public-record-data-scrapper reliability hardening session
Suggested investigation
- Check whether the IRF parser stops at a sentinel, duplicate header, or statistics block boundary.
- Add a parser test with a tail-appended item near the final open section.
- Fail loudly if the source file and derived counts disagree during refresh tooling.
Failure state
The source file
INST-INDEX-RERUM-FACIENDARUM.mdcontains a newly added open item:IRF-SYS-044But
organvm irf statsstill reports the old totals immediately afterward:Total: 715Open: 384SYS: 29Expected from file contents after insertion:
Total: 716Open: 385SYS: 30Why this matters
The IRF CLI is being used as a governance truth source during session closeout. If it silently undercounts new items, operators can incorrectly conclude the registry is synchronized when it is not.
Reproduction
IRF-SYS-*row near the tail ofINST-INDEX-RERUM-FACIENDARUM.md.organvm irf stats.Observed on
meta-organvm/organvm-corpvs-testamentvmpublic-record-data-scrapperreliability hardening sessionSuggested investigation