Changeblog

Today we cleaned up the Zechariah disambiguation page and finally got it under control. The old long scripture dump was not helping readers; it was mostly list noise and “name only” mentions that cannot be reliably disambiguated. Instead of deleting blindly, we triaged each reference, kept only what could be identified by patronymic, role, or clear context, and dropped what was out of scope for this project. We added new, proper disambiguation entries and created real stub pages for newly identified Zechariahs. That included Zechariah son of Meshelemiah (porter / gatekeeper), Zechariah in the days of Uzziah (understanding in the vision of God), Zechariah son of Bebai (Ezra return context), and Zechariah son of Jonathan (Nehemiah procession / trumpets). Each stub follows the canonical bio-page pattern and provides clean scripture anchors with no speculation. We also tightened the Zechariah footnote attachments in the database. Roster-only verses were detached so they stop throwing footnote markers in random name lists. The remaining markers now form a smaller, high-signal set that actually supports the disambiguation work. A new “name variants” note was added (Zachariah/Zacharias/Zacarías/Zecarias), with a clear statement that no alternate-spelling search has been performed yet.

2026-01-24 Progress note: chapter navigation is now live. I added left and right arrow buttons at the bottom of chapter.php. This fixes a real user-flow problem. Before, the reader had to scroll back to the top, open the hamburger menu, and then hunt for the next chapter link. That rhythm was a friction point. Now the reader can move forward or backward without breaking stride. The logic is database-driven (no hard-coded chapter counts). If you reach the end of a book, the next arrow jumps to the first chapter of the next book. If you are at the beginning of a book, the previous arrow jumps to the last chapter of the prior book. When no previous chapter exists, the left arrow is disabled. We also clarified routing: chapter.php without coordinates immediately redirects to the chapter selector, keeping the scripture renderer clean and canonical.

Added a new P0 security task: integrate Project Honey Pot into the contact/message system. Verified my account, generated an http:BL access key, and confirmed the key is working. Stored the key privately in /private/api_keys.php, following the existing API key pattern. First real-world spam submission was used as a test case. Looked up the sender IP in Project Honey Pot and submitted a comment report successfully. This confirms I can contribute real spam data upstream while I continue hardening the message pipeline. Next work will focus on practical anti-spam defenses (honeypot field, IP throttling, and optional automated http:BL lookup).

Added and completed 38_zechariah.php as a full “book profile” page for Zechariah (#38). This is not a commentary and not a bridge page. It is a separate, orthogonal page role: a structured book-level overview that stays close to the text’s own internal markers (dates, named persons, section seams, repeated phrases, and explicit silences). The intent is orientation and reference, not interpretation or camp argumentation. This page now serves as the canonical exemplar for the “text profile” role. It establishes a repeatable template for future book profiles: clear sectioning, plain-reader language, minimal assumptions, and clean reference handling (linking where appropriate without turning the page into a link farm). Going forward, other book-profile pages can follow this model to keep the project consistent, disciplined, and scalable.

Progress note: the new contact/message system is now live and receiving traffic. A real outside user submitted a message through the form, and it was captured directly into the site database. No email system was involved. The admin view shows full message details (sender, subject, timestamp, and IP), proving the end-to-end pipeline works. The first captured message was obvious spam ("Meredith Doe" + Gmail + SEO pitch), which is actually a good sign. It means the system is public-facing and working under real-world conditions. In plain terms: the bait is in the water, and we caught a fish — it just happened to be junk mail. Next step has been promoted to P0: anti-spam hardening for the contact system. Plan is to add a honeypot field (server-side enforced), basic IP throttling, and optionally Project Honey Pot / http:BL integration later. Goal is simple: reduce spam, protect the database, and keep admin time focused on real messages.

Today I formalized a new orthogonal page role: Text Profiles. This keeps book-level structure and metadata out of bios and bridge pages. I created and saved the domain inventory file: /text_profiles/TEXT_PROFILE_DOMAIN_INVENTORY.md This inventory defines the allowed observation domains (attribution, outline, dates, addressees, places, formulae, silences, etc.), without forcing uniform content for every book. I began /text_profiles/38_zechariah.php as the first real Text Profile instance for book #38. This file will be knowledge-dense, but must remain within the Text Profile scope (text-first, non-interpretive). I also adopted an explicit AUTHOR NOTES policy for draft, replaceable scaffolding, so early wording is not mistaken for settled content. Key constraint reinforced: canonical does not mean sterile. Canonical means role-correct, structured, and safe to evolve without scope drift.

Recorded a future enhancement to improve index paper efficiency without affecting index correctness or report pagination. Identified that naive left-to-right wrapping breaks conventional index reading patterns and should not be used. Committed a P2 backlog item to explore an optional CSS-based (tableless) compact index layout that preserves column-major reading order (top-to-bottom, then left-to-right). Explicitly scoped the item as presentation-only, with no impact on index semantics, addressing, or report body pagination. This should save paper.

Stabilized the monthly Changeblog report as a true printed edition rather than a screen-only view. Resolved persistent line truncation by standardizing the printed report to landscape orientation, eliminating width overflow without shrinking text to unreadable sizes. Aligned pagination logic with print geometry so page and line references are deterministic and match the physical output. Added visible edition page markers ("--- Page N ---") to each report page, allowing the index to be used directly from the printed document rather than relying on printer-generated page numbers. Validated index fidelity by confirming that indexed page/line references land on the correct report lines in print preview across browsers. Deferred physical printing until the end of the month to avoid waste, with confidence that the report will render identically when regenerated.

Continued systematic disambiguation of individuals named Zechariah. Reinforced separation between name resolution, identity pages, and commentary. Completed documentation of Zechariah son of Jeroboam II. Confirmed his short reign from approximately 753 to 752 BC. Anchored this identity in the Kings narrative. Restructured the disambiguation page to function strictly as a routing index. Moved narrative detail out of the index and into the identity page. Documented the biblical limits of the record for this figure. Preserved space for future archaeological or secondary evidence. Addressed Zechariah son of Jeberechiah from Isaiah 8:2. Removed interpretive and devotional material from this identity page. Produced a deliberately minimal profile based on a single attestation. Defined the immediate narrative context explicitly. Recorded what the text does not state about this figure. Affirmed that textual silence is data rather than a deficiency. Prepared a scaffold for Zechariah son of Jehoiada from 2 Chronicles 24. Identified 2 Chronicles 24:20–22 as the primary attestation. Separated core attestation from surrounding narrative passages. Created a stub identity page with correct structural sections. Established a stable and repeatable framework for Zechariah identities. Enabled future work without reopening settled identity decisions.

Stabilized the Zechariah disambiguation workflow. Separated identity resolution from content development. Audited all occurrences of Zechariah across Scripture. Evaluated patronymics, chronology, and office for each occurrence. Rejected name similarity and shortened forms as grounds for merging identities. Identified Zechariah son of Jeroboam II as a distinct historical figure. Confirmed him as the only king named Zechariah. Confirmed his reign as limited to the northern kingdom of Israel. Ruled out cross-kingdom name collisions within the ASV corpus. Excluded spelling variants such as Zechariah and Zecharias from identity merging. Eliminated a class of ambiguity caused by name overlap. Refactored the Zechariah disambiguation page into a routing index. Linked only to resolved individuals. Removed exploratory verse clutter from the index. Created a forward-linked stub page for Zechariah son of Jeroboam II. Included full navigation and a neutral scope note on the stub page. Marked the stub page as under construction. Reserved the identity without forcing premature synthesis. Enabled asynchronous future work while keeping the index stable. Maintained a minimal and method-compliant disambiguation structure. Noted that further work remains on Zechariah-related pages.