Weekly Research: Scripture Served Native
The Bible engine is easy to describe and hard to overclaim. What we can verify today: the KJV is served from a native SQLite database inside davar_http.exe, no third-party Bible API at page-render time. Strong's Hebrew entries promoted from the estate biblelua lane resolve through /api/bible/strongs. Interlinear OT tags match staged estate files with hash proof.
What we do not claim: that every translation, commentary volume, or church-father corpus in the estate bibles lane is public. Most of biblelua-data remains operator substrate. Promotion is one layer at a time with hash receipts.
This weekly lane exists so ministry writing stays tethered to research, not so we can dump the whole estate on the website.