administrator/DocForge2
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages

Cache validated source generation receipts

Browse source
This commit is contained in:
Andraxion 2026-07-29 06:07:03 -04:00
parent 529accf858
commit 6253c45a5e
3 changed files with 115 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

9
DEVELOPMENT_NOTES.md
View file

@ -86,6 +86,15 @@ malformed, incompatible, foreign, or dirty receipt becomes a cache miss and fall
canonical load and row-verification oracle. Successful fallback verification repairs the disposable
receipt.
The final 1,000-node evidence run initially exposed a repeatable 52 ms exact-read maximum against
the 50 ms target. Profiling showed no source parsing or SQLite cost; each request rebuilt and
revalidated 1,000 `Path` objects from the unchanged JSON receipt twice. The project binding now
caches only the strictly validated receipt structure behind its device, inode, size, modification
time, and change-time signature. Canonical file and directory identities are still recaptured
before and after every query. Receipt replacement or mutation invalidates the cache and fails
closed. The same ordered exact-read profile fell from about 40–52 ms to about 18 ms without
weakening stale-read refusal.
The receipt is deliberately generic-project behavior. Incremental adapter manifests retain
authority over generated or specialist source identities. A one-method legacy adapter continues to
work even when it cannot provide a cheap generation.