Changeblog

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.

Focused today on infrastructure rather than new content. Clarified and reorganized the Project Briefing. Made implicit assumptions explicit. Defined Scripture as primary data. Separated Scripture strictly from commentary layers. Defined commentary as the place for opinion, disagreement, and analysis. Formalized the requirement to represent major positions fairly. Required that positions be stated as their proponents would recognize. Defined the role of bridge pages precisely. Set bridge pages to collect primary texts without promoting models. Resolved ambiguity between data collection and interpretation. Distinguished strong arguments from unsupported opinions. Affirmed well-argued positions anchored in evidence. Rejected smoothing, persuasion, and unsupported claims. Introduced HOUSE_STYLE.md to standardize formatting decisions. Settled presentation rules to avoid repeated debate. Deferred contributor systems by design. Deferred community formation and SEO intentionally. Prioritized coherence and rule enforcement before discoverability. Strengthened the methodological foundation of the project. Reduced the need for repeated explanation in future work. Improved long-term consistency and reuse. Enabled future automation and reliable exports. Prepared the project for durable growth without reinterpretation.

Focused today on infrastructure hardening and scope correction. Completed several high-priority housekeeping tasks. Identified and canonized admin/commentary_new.php as the admin database model. Used this page as the reference for navigation and database access discipline. Standardized cache-busting and avoided duct-tape patterns. Stabilized the Joshua namespace across multiple pages. Clarified roles and disambiguation boundaries for Joshua-related entries. Completed Joshua of Beth Shemesh as a minimal, Scripture-anchored identity page. Drafted Joshua the High Priest with a focus on textual role rather than synthesis. Identified and corrected content leakage during the review. Removed or deferred material that was interesting but out of scope. Reinforced commitment to unsentimental pruning and clear page purpose. Created a new bridge page, borrowed_capacity.php, to capture a related theme. Produced less visible content but reduced overall system disorder. Improved system cleanliness despite uncovering additional issues. Set the next focus on Joshua son of Nun. Planned follow-up work on Zechariah disambiguation and bio pages. Prepared to return to post-exilic material that motivated the project.

Added a dedicated admin-side verse editor. Enabled precise corrections to Scripture text without using phpMyAdmin. Loaded verses by book, chapter, and verse. Displayed the current database text for review. Allowed safe inline edits for minor transcription issues. Identified a schema mismatch during implementation. Aligned the editor with the existing ASV_verses table and column names. Adapted the editor to the schema rather than reshaping the database. Preserved the integrity of the Scripture data model. Added explicit error reporting for admin use. Implemented a SHA-256 check to prevent accidental overwrites. Protected against conflicts from multiple sessions or edits. Improved safety and speed of Scripture text maintenance. Restricted phpMyAdmin to database administration tasks only.

Added a database-driven Study Index page. Listed bridge pages and bios that are referenced by Scripture footnotes. Defined the page as navigation rather than commentary or a bridge page. Queried verse_footnotes and footnotes to discover studies in active use. Aggregated results by target URL. Displayed a clean index with verse-reference counts. Improved discoverability based on actual Scripture annotations. Removed reliance on manual curation. Preserved boundaries between Scripture, footnotes, and study pages. Derived the index from real usage across the text. Enabled automatic updates as new studies are linked from footnotes. Eliminated ongoing maintenance for the index. Prevented drift between content and navigation.