Changeblog

Started a new bridge page: clouds.php. Added the PAGE_META block with page_type set to bridge_pages and title set to Clouds. Verified that the Study Index reads the metadata correctly and lists Clouds as a bridge page. Built the opening Scope Statement. Defined the page as a text-gathering node for passages where cloud language connects with divine presence, divine movement, heavenly court scenes, judgment, glory, concealment, or figurative multitude. The page explicitly does not decide which prophetic model is correct. It maps the passages first. Added Layer 1 as the active working layer. Kept Layer 0 as the Scripture text itself, rendered through chapter.php. This preserves the layer architecture: Scripture first, bridge-page observation second, interpretive taxonomy later, and argument outside the bridge page. Built the first Layer 1 study blocks. Added Core Passages for Cloud Language, Clouds and Divine Presence, Clouds and Divine Movement, Clouds, Glory, and Concealment, Clouds in Judgment Contexts, Clouds in Heavenly Court Scenes, Clouds and Divine Speech, Clouds in Son of Man Language, and Cloud as Figurative Multitude. Used vlink() throughout the bridge page so every reference points back to the Scripture layer. Confirmed that the links correctly route from clouds.php to the exact chapter-and-verse anchors in Layer 0. Captured an author note on Isaiah 19 while the thought was fresh. The note records that Isaiah 19:1 names Egypt directly and places cloud-riding language inside a judgment oracle concerning Egypt. The note was kept out of the rendered page because it belongs to a future Layer 2 or Layer 3 discussion, not to the bridge-page map. Created a new Clouds footnote and linked it to clouds.php. Chose high-signal entry points instead of attaching a footnote to every cloud occurrence. A full search found 136 matches for cloud-related language, but the footnote system should serve as entry ramps, not noise. Tested the Footnote to Verse Tool with selected passages. Confirmed that the parser requires the database book name Psalms rather than Psalm. Also confirmed that verse ranges work when entered with a plain hyphen instead of an en dash. Attached the Clouds footnote to the selected verses. The preview completed cleanly with zero unparseable lines, zero unknown book names, and zero missing verses. Existing attachments were safely ignored. Verified the full Wissensnetz loop in practice: Study Index to Clouds, Clouds to Scripture through vlink(), and Scripture back to Clouds through footnotes. Psalm 104:3 was used as the visible test case. The marker rendered beside the verse, and the chapter footnote list routed back to the Clouds bridge page. Result: clouds.php is now a live bridge-page node. It has a working scope statement, a strong Layer 1 structure, direct Scripture links, and selected footnote entry points from the Scripture layer. Layer 2 has not been added.

Layer Architecture + Day of the Lord Expansion This round of work focused on structural clarity, not theological conclusions. The "Day of the Lord" bridge page moved from simple collection to layered design. Layer 0 remains the biblical text itself. No commentary. No framing. Just Scripture. Layer 1 now organizes the passages by recipient — Judah, Babylon, Egypt, Edom, the nations — without collapsing them into a system. The grouping is observational only. Layer 2 was added beneath it. This section explains how major interpretive traditions relate these passages to one another. The goal was education, not advocacy. The models are described fairly and in equal weight. No ranking. No conclusions. No subtle steering. A formal layer structure has now been defined: Layer 0 — Biblical text Layer 1 — Observational organization Layer 2 — Interpretive taxonomy Layer 3 — Argument or position essays (not yet implemented) This architecture allows growth without premature commitment. Opinion, when it comes, will rest on visible structure. Visually, layer separation is now handled by simple structural containers in styles.css. New classes were introduced: layer_block, layer_1, and layer_2. Distinction is made by subtle left-border color only. No background changes. No decorative emphasis. The beige paper remains the foundation. The decision was made to explain the layer system once from index.php rather than cluttering each page with explanation. Pages remain clean; architecture is documented centrally. Editorial policy was also clarified. Future guest authors will write within defined boundaries. Passion is welcome. Carelessness is not. All claims must anchor to text. Strawmen will be returned for revision. Method is enforced. Conclusions are not pre-approved. Overall direction this cycle: More structure. More discipline. Clearer reading modes. No movement into Layer 3. The fight has not been avoided. It has been sequenced.

Invisible Creatures / Layer 1 Refinement This update focused on tightening Layer 1 discipline. The goal was clarity, not expansion. Several bridge-page sections were flattened. All <h4> headings were removed where they implied outline logic. Content was rewritten into report prose. Headings now stop at <h3>. All <h3> sections were placed inside .study-block containers. This made sections visually distinct without adding decoration. Major <h2> sections remain open and unboxed. Bullet lists were converted to prose where possible. This reduced visual emphasis and removed “summary” signals. Silences are now stated plainly in sentences. Footnote markers were adjusted for usability. The markers are slightly larger and easier to click. No meaning or hierarchy was changed. A new Devil section was added. It records New Testament usage only. Matthew 4:10 was included where Jesus names the Devil as Satan. No origin story or system was added. The demons section was expanded with additional texts. Behavior, speech, belief, limitation, and judgment were documented. Old Testament Hebrew terms were added as observations only. The Septuagint connection was noted without drawing conclusions. Revelation material was kept local to Revelation. Where Revelation ties identities together, that is recorded there. Other texts were not forced to follow. Overall, this pass reduced explanation and increased structure. The text now speaks more clearly on its own. Layer 1 stayed descriptive.

Footnotes, ordering, and a missing idea Today exposed a weakness that only shows up once footnotes start overlapping across verses. When footnotes criss-cross, numbering based on “first seen” stops being reliable. The original design handled attachment well (which footnotes belong to which verses), but it never made chapter-level numbering explicit. That worked until it didn’t. The fix was not a patch. It was finishing the model. A new chapter-level ordering table now defines footnote numbers where needed. chapter.php obeys that order when it exists and falls back to the old behavior when it doesn’t. Zechariah 3 was the test case. Mixed verse markers now display correctly (1 3, 1 2), while other chapters remain unchanged.

Wissensnetz / Invisible Creatures Bridge Page Added a new bridge page: “Invisible Creatures.” Defined “heavenly” as non-earthly or unseen, not as morally holy. Kept Scripture primary and preserved silence where the text is silent. Established a strict Layer-2 method: record what appears, what is said, and what is done. No systems assumed. No hierarchies imposed. Introduced “messenger” language as a lexical starting point. Showed overlap between human and non-human messengers without collapsing them into a single class. Built the page as a true Wissensnetz node: Scripture pages remain stable; bridge pages provide orientation; interpretive systems are deferred as labeled overlays. Expanded footnotes beyond simple links. Footnotes now function as micro-bridge nodes with scope notes, short body text, and routing. Added a Lucifer (Isaiah 14:12) footnote. Acknowledged the common association without adopting it. Located the passage in its textual context and routed readers to the Invisible Creatures bridge page. Confirmed that multiple independent footnotes may point to the same bridge page with customized wording per verse. Result: more entry points, less coercion, and clearer separation of text, orientation, and interpretation.

Today we fixed a real drift problem: moving pages broke my Study Index because the links were generated dynamically and depended on old paths. As I moved key pages (such as Zechariah) into /disambiguation, the index began to lose entries. Instead of patching it with more hard-coded link rules, we took the smarter path. We added a simple PAGE_META block to pages (page_type + title), letting each page declare what it is in plain sight, like a label on the file. Then we rewrote /studies.php to scan the file system directly and build the Study Index from pages that opt in. It reads PAGE_META, filters by whitelisted folders, and shows the title with the page_type. No database dependency, no disambiguation chain, and no more whack-a-mole when files move.

We also normalized navigation by copying the Zechariah disambiguation page into /disambiguation/zechariah.php and then mass-correcting all internal PHP links from /bios/zechariah.php to the new canonical location using grep + sed. Finally, the zechariah footnote link_url was updated in the footnotes table so the rendered footnote now points directly to the new disambiguation page.

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).