Versions

• Connected transmission comparisons, waiting rhythm, accumulated labor, and recorded excavation to the current archive instead of deployment-time snapshots.
• Expanded the lightning constellation from a 20-event excerpt to the full available spatial event record; recorded events remain distinct from summary counters and no missing strikes are invented.
• Added automatic replay-list refresh and durable last-successful snapshots for temporary archive connection outages, while preserving historical corrections and the no-video Transmission 020 incident.

Evidence basisSealed transmissions through 025, world-event archive, completion and replay-correction regression tests, outage-recovery tests, and public API verification

• Advanced the static transmission atlas through sealed Transmission 023 and the verified 128-to-148 field progression.
• Updated the durable outage fallback from Transmission 021 to Transmission 023, preserving 148 completed pole records, 1,321 copper ingots produced, 350 lightning rods crafted, 2,240 iron bars crafted, and Pole 149 as the next position.
• Regenerated the Underground Nervous System from the append-only event archive: 30,404 recorded underground block breaks across 5,695 spatial cells, including 1,102 working-plane breaks.
• Added durable Logbook fallbacks for Transmissions 022 and 023 so their verified replay identities and production totals remain available if the live archive service is temporarily unavailable.
• Extended the close-of-transmission refresh so every future sealed session advances the static atlas, verified fallback, completed-pole evidence, and underground excavation source together before publication.

Evidence basisSealed Transmission 022 and 023 session records, append-only pole-completion ledger, append-only world-event archive, completed YouTube broadcast records, public telemetry and Logbook APIs, production build, and regression suite

• Installed the client-only Fractal Lightning 1.0.1 renderer for Minecraft 1.21.11 without changing lightning generation, timing, coordinates, targeting, weather authority, or telemetry.
• Installed Realistic Thunder v1.0 as a resource pack replacing three rain and four thunder recordings; adapted only its rejected pack metadata for Minecraft 1.21.11 and preserved all media assets unchanged.
• Rejected ImmersiveThunder: Reforged 1.3.5+1.21.x because it requires Fabric Loader 0.19.2 or newer; retained the canonical 0.18.4 loader instead of widening the change across the profile.
• Published exact source links, licenses, SHA-512 hashes, adaptation details, rollback evidence, and the complete refreshed 252-module canonical client manifest.
• Verified an isolated compatibility startup with Fractal Lightning, the adapted sound pack, Iris, Sodium, and OpenAL; decoded all seven OGG assets without error and did not open the official world.
• Preserved Environmental Amendments 001 and 002, Minecraft's authority over individual lightning entities, Survival and construction rules, mob and terrain protections, Walter, and the Lightning Field Vigil protections.

Evidence basisUpstream Modrinth files and project metadata, embedded Fabric manifest, last official 251-module client log plus installed Fractal Lightning, SHA-512 attestations, isolated Minecraft 1.21.11 compatibility launch, retained resource-pack selection, FFmpeg decode test, recovery copy, production build, and rendered-page regression suite

• Published the 2009–2018 NOAA/NCEI cloud-to-ground lightning baseline for the disclosed Quemado proxy, including the exact local tile, annual means, seasonal concentration, broader comparison area, and year-by-year calculation record.
• Distinguished historical National Lightning Detection Network cloud-to-ground counts from Geostationary Lightning Mapper total-lightning observations and from forecasts.
• Recorded that satellite-flash-to-Minecraft translation is not active and would require a later public amendment declaring its source, geometry, grouping, cooldown, uncertainty, failure behavior, and effective transmission.
• Preserved the independence of construction, Walter, Survival inventory, mob behavior, terrain protection, and vigil protections from any prospective lightning input.

Evidence basisNOAA/NCEI daily 0.1-degree NLDN tile summaries for 2009–2018, published archive metadata, ten-year arithmetic record, NOAA/NESDIS GLM product description, production build, and rendered-page regression suite

• Adopted a prospective coupling between the Minecraft Overworld and the NOAA/National Weather Service hourly point condition for a disclosed public proxy at Quemado, New Mexico.
• Kept the artwork's precise physical coordinates undisclosed and labelled the feed as a regional approximation rather than an exact on-site observation.
• Added a deterministic clear, rain, and thunder translation, five-minute refreshes, a 20-minute freshness limit, and no-change behavior when the source is stale, malformed, or unavailable.
• Separated the raw NWS condition, source health, mapped state, and world-observed state in telemetry, while retaining the nearest NWS station observation as contextual evidence.
• Preserved the prohibition on summoned, timed, targeted, or guaranteed lightning and changed future terminology to Minecraft-engine lightning under externally synchronized regional weather.

Evidence basisEnvironmental Amendment 002, NOAA/NWS linked point forecast and observation APIs, Fabric mod build, deterministic mapping tests, preflight freshness gate, and public telemetry disclosure

• Added the completed Transmission 015 replay to the durable Logbook archive after both upstream episode sources omitted it.
• Restored the verified 026-to-038 field advance, 12 completed poles, 144 iron bars crafted during the transmission, and 592 cumulative iron bars.
• Replaced Transmission 016's stale generic upstream label with its verified published title and preserved its 038-to-043 field advance, five completed poles, and 80 iron bars crafted during the transmission.
• Added regression assertions tying both entries to their verified public replays and closing field states.

Evidence basisSealed Transmission 015 and 016 sessions, public YouTube watch metadata and end timestamps, append-only production records, public Logbook feed, production build, and regression suite

• Added the sealed Transmission 021 replay to the durable Logbook archive after the upstream episode feed omitted it.
• Restored the correct sequence: Transmission 022, Transmission 021, the Transmission 020 no-video incident record, then Transmission 019.
• Preserved the verified 071-to-106 field advance, 35 completed poles, 560 iron bars crafted during the transmission, and 1,680 cumulative iron bars.
• Added a regression assertion tying the Logbook entry to the verified replay and 106-pole closing state.

Evidence basisSealed Transmission 021 session, published YouTube metadata and end timestamp, append-only production record, public Logbook feed, production build, and regression suite

• Corrected Pole 071's modelled ground elevation from Y=87 to the verified Y=67, restoring its full 21-bar shaft beneath the shared Y=89 lightning-rod tip.
• Recomputed the surveyed terrain high point, relief, minimum support, and complete iron-support plan from the corrected 400-position field record.
• Normalized stale live bridge metrics and added a Pole 071 regression assertion so the false short-support rendering cannot return.

Evidence basisOfficial saved-world block column at X=148/Z=424, Transmission 021 footage, corrected 400-position survey, production build, and regression suite

• Recomposed the Transmission 020 incident into the same two-column archive rhythm as recorded transmissions.
• Replaced the absent thumbnail with an explicit no-video evidence panel while preserving the incident narrative, measured interval, production totals, and non-reconstruction disclosure.

Evidence basisPreserved Transmission 020 incident record, public Logbook composition, production build, and rendered-page regression suite

• Moved the Transmission 020 incident record into the public transmission sequence between Transmission 021 and Transmission 019.
• Preserved the incident disclosure and all measured evidence while keeping the missing video visibly distinct from recorded YouTube replays.

Evidence basisPublic transmission archive order, preserved Transmission 020 incident record, production build, and rendered-page regression suite

• Replaced Walter's twelve-file diary reader with the complete append-only diary-closure archive, preserving a monotonic ledger sequence even when Minecraft's day counter repeats after clock or world cycles.
• Restored the descriptive Transmission 018 and 019 titles that had been overwritten by generic canonical labels.
• Advanced the verified durable site state through sealed Transmission 021 and 106 completed poles; the Pole 071 ground-elevation correction recorded for this release remained incomplete and is superseded by v1.0.4.
• Regenerated the underground excavation model from every current append-only event file without inferring unrecorded tunnels or changing the recorded excavation count.

Evidence basisAppend-only diary and world-event archives, sealed Transmission 021 record, YouTube metadata archive, saved Waiting for Lightning field data, production build, and regression suite

• Added a unique request identity to every live telemetry and Owncast poll so a browser or edge cache cannot replay an older transmission state as current.
• Marked both public live-data routes non-cacheable at the browser, framework, CDN, and upstream-request layers.
• Retained Transmission 020 and 71 completed poles as the verified durable fallback; Transmission 013 remains historical evidence only and can no longer become the current offline state.

Evidence basisCurrent authoritative telemetry response, cache-busted public rendering, route-header regression checks, production build, and live public verification

• Reworked the wide transmission atlas into readable two-column session cards on phones while preserving the dense comparison table on tablets and desktop.
• Made interactive field and underground models safer to scroll past on touch screens, enlarged their controls, and reduced high-density canvas rendering cost on coarse-pointer devices.
• Corrected the Lightning Constellation projection to use one uniform X/Z scale, preserving the surveyed field's true 480 by 300-block rectangle on every screen shape.
• Added safe-area-aware spacing, stable mobile navigation locking, more usable pole-grid targets, tighter small-screen composition, and deferred Logbook thumbnail decoding.

Evidence basisPhone, tablet portrait, and tablet landscape browser measurements; responsive interaction checks; lint; production build; and rendered-page regression suite

• Rebuilt the Underground Nervous System from all twelve current append-only event files instead of leaving the public model on its earlier excavation snapshot.
• Advanced the visualization from 23,428 to 25,657 recorded underground block breaks, from 904 to 1,018 working-plane breaks, and from 4,202 to 4,737 spatial cells.
• Preserved the model's exact recorded bounds and three-block aggregation method; no unrecorded tunnel geometry was inferred.

Evidence basisTwelve append-only Minecraft event files and regenerated underground telemetry artifact

• Recorded publicly that Transmission 020 occurred after the preparation system incorrectly reported READY, but OBS created neither a local recording nor an outbound stream and YouTube never became live.
• Preserved the surviving field and labor evidence—including the advance from 58 to 71 poles—without representing telemetry, screenshots, or a reconstruction as the missing first-person video.
• Added the failed session to the transmission atlas with an explicit NO VIDEO RECORDED state instead of inventing a replay link.

Evidence basisOBS session log, YouTube broadcast state, final world snapshot, append-only pole ledger, and preserved screenshots

• Identified Lootr—not Waiting for Lightning or Walter—as the system replacing generated dungeon and mineshaft loot containers and preventing their removal.
• Changed Lootr's breaking setting from disabled to enabled so the player can remove those generated containers when clearing space for legitimate Survival-built XP farms.
• Did not remove Lootr, alter existing world blocks, change loot tables, or edit container contents. The configuration takes effect after a full Minecraft restart.

Evidence basisInstalled Lootr runtime metadata and verified before-and-after configuration record

• Moved the construction matrix directly below live status, folded support burden into the isocephaly model, and removed the redundant evidence constellation.
• Replaced radial transmission fingerprints with a comparable session atlas, added project-goal denominators and precise time averages, and rebuilt labor accumulation as four separately labeled analytical scales.
• Reconstructed an interactive underground volume from 13,476 recorded below-Y=60 block-break events, with zoom, rotation, a Y=-59 plan view, reduced-motion behavior, and explicit spatial aggregation disclosure.

Evidence basisAppend-only world event archive, canonical field survey, fourteen sealed transmission records, current telemetry response, responsive website build, and telemetry-atlas regression tests

• Expanded the telemetry room with a terrain-resistance map, transmission fingerprints, lightning constellation playback, material-flow model, waiting rhythm, cumulative labor landscape, underground recording aperture, and evidence constellation.
• Added zoom controls and wheel zoom to the rotating three-dimensional isocephaly model while retaining drag steering, idle rotation, and reduced-motion behavior.
• Kept missing underground paths and incomplete historical measurements explicitly absent instead of turning them into visualized facts.

Evidence basisCanonical field survey, fourteen sealed transmission records, current telemetry response, corrected Transmission 008 replay record, website build, and telemetry-atlas regression tests

• Added a slow idle rotation to the three-dimensional field so the common tip plane and uneven terrain can be read without manual interaction.
• Paused automatic movement while the visitor drags the model and disabled it for visitors who request reduced motion in their device settings.

Evidence basisInteractive geometry implementation, reduced-motion behavior, website build, and rendered-page regression suite

• Added an interactive three-dimensional model of all 400 field positions using the canonical Survival survey's recorded ground elevation at every pole.
• Made the governing equal-tip condition legible as a shared Y=89 plane above terrain that remains unflattened, with built poles distinguished from unbuilt positions.
• Defined isocephaly from its art-historical use—the alignment of figures' heads—and showed how the field translates that principle into copper tips sharing one horizontal level.

Evidence basisCanonical 400-elevation field survey, shared-tip field record, responsive website build, and Dia's official description of the original work

• Advanced the sealed public field state from 017 to 024 completed poles and the latest transmission record from T011 to T013.
• Updated field geometry, material production, carried inventory, construction totals, survival totals, and next-pole guidance from the verified Transmission 013 closing record.
• Extended the telemetry wake window and made the T013 close the durable fallback so a slow or paused data service can no longer roll the public site back to an older transmission.

Evidence basisSealed Transmission 013 session, append-only pole ledger, authoritative telemetry response, YouTube archive record, and public API regression tests

• Moved the complete telemetry ledger off the installation entrance and replaced it there with a compact five-item evidence snapshot.
• Created a dedicated telemetry page with a live completion gauge, 400-position matrix, material-readiness bars, transmission metrics, survival indicators, world conditions, lightning history, and the complete raw ledger.
• Kept every graphical display bound to the same verified telemetry endpoint and retained explicit paused, fallback, missing, and sealed states instead of inventing activity.

Evidence basisVerified telemetry API rendering, responsive data-room checks, website build, and rendered-page regression suite

• Added a consistent secondary social navigation row to the footer of every public page on desktop, tablet, and mobile.
• Used restrained text links for X, YouTube, and LinkedIn so the footer improves discovery without restoring visual weight to the compact responsive header.

Evidence basisSite-wide rendered-page regression, responsive layout verification, website build, and public deployment

• Replaced the permanently expanded mobile and tablet navigation with a compact 64-pixel header and an explicit menu control.
• Kept every project destination, social channel, public version, current-page marker, and live-state label available inside the opened navigation panel.
• Added keyboard dismissal, visible focus treatment, expanded-state semantics, and touch-sized navigation targets.

Evidence basisResponsive browser verification, keyboard interaction check, website build, and rendered HTML tests

• Kept the main Waiting for Lightning title on one line across mobile and tablet layouts instead of forcing Lightning onto a second line.
• Scaled the complete title against the available viewport width while preserving the animated lightning-letter treatment and desktop composition.

Evidence basisProduction mobile and tablet measurements, responsive local rendering, website build, and rendered HTML tests

• Uploaded the continuous independent Transmission 008 OBS master to a separate unlisted YouTube archive while preserving the damaged live replay as incident evidence.
• Made the telemetry archive withhold the corrected identity until YouTube reports successful processing and a real media duration, preventing a still-processing upload from replacing a viewable record.
• Changed the Logbook merge key from video identity to transmission identity so a corrected archive cannot create a duplicate Transmission 008 entry.
• Made a verified corrected master automatically replace only the damaged replay URL and thumbnail while preserving the canonical title, factual statistics, provenance, and failure disclosure.

Evidence basisAuthenticated YouTube upload and processing state, corrected-upload record, telemetry corrected-identity regression, production archive merge, and rendered site test

• Sealed Transmission 008 at 003/400 with 5,129 blocks travelled, 2,267 blocks broken, zero deaths, zero natural lightning events, and no new pole completion.
• Traced the damaged YouTube replay to the destination-isolated relay's remaining localhost UDP/MPEG-TS transport: its YouTube queue overflowed, corrupted packets, and produced 92,953 timestamp-discontinuity reports during the session.
• Removed both UDP packet queues and replaced them with direct FLV platform outputs backed by independent FFmpeg FIFO muxers, recovery attempts, bounded buffering, overflow-to-keyframe recovery, and no shared source restart.
• Expanded relay regression coverage to reject circular-buffer overruns, corrupt packets, and timestamp discontinuities while proving that a failed YouTube destination cannot stop the complete Owncast stream or OBS ingest.
• Verified that OBS retained a continuous 4.7 GB, 2:25:40 H.264/AAC master at 30 fps; beginning, middle, and ending samples decoded cleanly, and OBS recorded only 22 lagged render frames out of 262,217 attempts (0.0%).
• Fixed the background master archiver's restricted-path Node lookup so the retained master can complete checksum-verified Google Drive preservation instead of remaining stranded in the local spool.
• Added an authoritative completed-transmission endpoint to the telemetry bridge and made the public Logbook merge it before YouTube's sometimes-stale RSS and channel discovery surfaces.
• Added Transmission 008 to the durable canonical Logbook with the damaged replay, retained master, relay cause, factual session totals, and correction status disclosed rather than concealed.

Evidence basisTransmission 008 session and publication ledgers, authenticated YouTube broadcast state, 4.7 GB OBS master inspection and sample decode, OBS performance log, relay error counts, failure-isolation regression, telemetry archive integration test, and public site build

• Removed the PREPARE TRANSMISSION dialog that required the artist to report a completed recovery drill back to the AI coding environment.
• Made the next PREPARE TRANSMISSION run detect and certify the current drill automatically after Minecraft closes, using the isolated client log and F2 screenshot as the authority.
• Bound acceptable screenshot evidence to the current isolated game directory and required its file timestamp to follow the drill preparation time, preventing an older or unrelated image from satisfying the gate.
• Kept the one-time human visual observation while eliminating any requirement to spend AI tokens, open Codex, or type a confirmation to complete ordinary readiness.
• Archived the revised source and current runtime on restricted Google Drive and passed a checksum-verified structural restoration drill.

Evidence basisToken-independent evidence regression, complete controller and publishing regression suite, Fabric build, compiled desktop app inspection, restricted Drive recovery manifest, and structural restoration test

• Removed the failed Backup HD from every readiness and OBS recording dependency; its Journaled HFS+ verification failure was filesystem damage, not an Intel-versus-Apple-Silicon format boundary.
• Re-enabled automatic OBS master recording into a bounded local spool with a 15 GB readiness floor so an open recording is never written directly into a cloud-sync path.
• Added automatic transmission-close archiving to the restricted Google Drive artwork archive: the closed master is uploaded, checked by byte size and MD5, assigned a SHA-256 attestation, read back, and only then deleted from the Mac.
• Made PREPARE TRANSMISSION verify Google Drive reachability and block a new transmission if an earlier local master is unmarked, still open, or not yet verified remotely.
• Ran a complete sample-master round trip through the production archive logic and confirmed deletion-after-verification ordering in the regression suite.

Evidence basisDisk Utility First Aid result, OBS configuration, restricted rclone connection, verified master round-trip with Drive item identity, archive log, controller installation, and passing pipeline regressions

• Added a root-level runtime boundary around the complete public site so an unforeseen client component failure produces a readable recovery state instead of an empty black page.
• Kept the existing telemetry-specific boundary as the narrower first line of containment while protecting navigation, archive pages, and every other client-rendered section independently at the root.
• Published a fresh versioned bundle and a direct verified-version reload link so a tab still holding the superseded pre-fix JavaScript can replace it deliberately without an automatic reload loop.

Evidence basisRoot layout containment source, production site build, boundary regression test, fresh public deployment, and live in-app browser verification

• Fixed a black-screen failure caused when a brief upstream timeout returned a reduced sealed-record fallback without optional distance and block totals.
• Completed the verified Transmission 007 fallback with its factual sealed totals and made every numeric presentation tolerate absent or malformed optional data.
• Stopped transient request failures from deleting the last verified browser state.
• Added a component-level containment boundary so an unforeseen telemetry rendering error can no longer erase the navigation, artwork, construction index, or rest of the public archive.

Evidence basisReproduced production exception, verified Transmission 007 sealed record, malformed-data regression, production build, and live browser render

• Ran a non-destructive Journaled HFS+ filesystem verification after configuring Backup HD as the recovery-master destination; the check failed with fsck_hfs exit code 8.
• Immediately disabled automatic OBS recording so no transmission master can be entrusted to the unverified volume.
• Added a persistent readiness health block: PREPARE TRANSMISSION cannot arm while this disk failure remains unresolved, even though the volume is mounted, writable, external, and has sufficient free space.
• Kept the construction-index and pole-reconstruction corrections active; the storage block affects readiness, not the verified 003/400 field record.

Evidence basismacOS disk verification result, persistent recording-volume health block, disabled OBS automatic recording state, readiness syntax check, and unchanged verified Transmission 007 field snapshot

• Stopped brief telemetry timeouts from blanking or downgrading the public construction index: the browser now retains its last verified state, and a sealed 003/400 Transmission 007 snapshot is used only while the live source is unavailable.
• Kept genuine live Minecraft state authoritative, so deliberate construction changes remain factual rather than being hidden by the outage fallback.
• Moved automatic OBS recovery masters off the internal Mac drive and onto an approved external USB volume; readiness now blocks if that drive is absent, the recording path drifts, or less than 50 GB remains.
• Added transition-aware pole provenance: a completed pole can be dismantled and reconstructed, its earlier record remains in completion history, and the newest completion becomes eligible for a replacement replay link.
• Added transmission metadata and LinkedIn field-report language that distinguishes reconstruction for replacement evidence from net-new pole progress.

Evidence basisVerified Transmission 007 closing telemetry, external-volume inspection, OBS destination configuration, 50 GB readiness gate, pole-transition ledger implementation, metadata regressions, and passing site and Fabric builds

• Indexed the sealed Transmission 007 record with the verified completion of Poles 002 and 003, bringing the canonical construction count from 001/400 to 003/400.
• Found that a static Transmission 006 recovery object was merged after live telemetry and therefore hid the confirmed survey and later pole completions; made live field state authoritative while retaining Pole 001's durable replay evidence.
• Added regression coverage requiring a surveyed 003/400 state with all three completion records so a historical fallback cannot silently overwrite later construction again.
• Traced the damaged YouTube replay to a shared relay queue that filled when the platform destination slowed, dropped encoded packets, and repeatedly reopened OBS's source connection; OBS showed no encoder overload or material render lag.
• Replaced the shared output queue with failure-isolated Owncast and YouTube workers and added a synthetic test proving that a forced YouTube destination failure does not interrupt the complete Owncast stream or OBS ingestion.
• Enabled automatic external-drive recording during every future OBS stream so a platform replay can be repaired from an independent master. Transmission 007 has no such master, so its existing discontinuities remain disclosed rather than falsely described as repaired.
• Added a readiness block for an open local Waiting for Lightning or YouTube viewer, guarding against delayed browser playback feeding earlier game sounds back during performance.
• Expanded Walter's restitution search beyond floor-supported barrel positions, staged all 31 preserved stacks for two recovery barrels, and staged exact restoration of the verified pre-death level-30 experience state with a one-time world audit record.
• Published the failures, evidence, limitations, and correction status in the Transparency incident ledger and the Transmission 007 Logbook record.

Evidence basisTransmission 007 sealed session and pole ledger, pre- and post-transmission world archives, Walter and player NBT records, OBS log, relay logs, passing Fabric build, destination-failure relay test, telemetry merge regression test, and public site build

• Turned each completed pole position into a direct link to the recorded moment when its copper rod completed the assembly.
• Aligned the append-only pole-completion clock with YouTube's actual broadcast-start clock and included an eight-second viewing lead-in so the final labor remains visible.
• Added a durable per-pole evidence record containing the transmission, video ID, replay offset, coordinates, and factual timing basis; unfinished poles remain non-interactive and newly completed poles wait for replay finalization.

Evidence basisPole 001 completion ledger, Transmission 006 YouTube broadcast clock, deterministic timestamp test, transmission-close integration, and passing site build

• Separated the completion date, time, and transmission into bounded rows so the entire record remains inside its information card.
• Replaced the rotating three-pronged effect with a restrained bright core, soft electrical halo, and two expanding energy rings.
• Anchored information cards inward at the left and right edges of the 25-column grid to prevent viewport overflow as construction advances.

Evidence basisArtist-supplied interaction screenshot, responsive card constraints, passing site build, and public telemetry record

• Gave every verified completed position an electrical glow and animated arc response on pointer hover or keyboard focus.
• Added a focused completion card showing the pole number, exact X/Y/Z rod-tip coordinates, project-local completion date and time, and transmission number.
• Kept incomplete positions visually quiet and continued to disclose missing completion evidence rather than filling gaps with estimates.

Evidence basisVerified Pole 001 origin and completion record, live telemetry coordinate contract, responsive interaction source, and passing site build

• Clarified from the Minecraft command record that survey confirmation was attempted before a preview existed; preview did not undo or erase a successful confirmation.
• Changed /lightningfield preview so it displays an already-confirmed canonical field without replacing, resetting, or unconfirming the saved survey.
• Made preview terrain sampling ignore continuous project iron bars and lightning rods so completed construction is not mistaken for natural ground during the pending survey workflow.
• Preserved the explicit human confirmation boundary: an unconfirmed candidate still requires /lightningfield survey confirm after inspection.

Evidence basisMinecraft latest.log command sequence, tested Fabric build, and matching installed runtime artifact

• Identified that X opening, closing, death, and lightning copy still displayed Minecraft's resettable internal day counter, causing Transmission 006 updates to say Day 1.
• Changed every X template and event key to derive the public day exclusively from the canonical transmission number.
• Added regression coverage in which Minecraft's internal days intentionally disagree with the transmission number; only the canonical transmission day may appear in published copy.
• Published a visible correction identifying Transmission 006 as Day 6 and explaining the superseded Day 1 display.

Evidence basisTransmission 006 X publication ledger, public correction post 2090382866345800097, installed monitor hash, X preview output, and passing publishing regression test

• Indexed the completed Transmission 006 YouTube replay in the Logbook from its sealed baseline, final telemetry, completed broadcast record, and documentary evidence.
• Recorded Pole 001 as the project's first completed Y=89 assembly, with its verified completion date and time available from the 400-position grid.
• Preserved the distinction between the artist's intended survey confirmation and the saved technical state: confirmation was attempted before preview, so the candidate remained unconfirmed at transmission close.
• Recovered the artist's exact closing reflection, repaired Telegram retry handling after a failed delivery, and delivered the preserved reflection as a separate personal LinkedIn draft.
• Identified Walter's normal player-item pickup as the cause of the missing armor and materials, preserved every held stack, attempted a two-barrel return cache, and blocked Walter from future item pickup. The cache attempt later proved unable to find floor-supported space inside the cramped base; no held item was erased.

Evidence basisTransmission 006 sealed session, exact reflection archive, Telegram delivery ledger, Minecraft player inventory record, completed-pole documentary capture, YouTube API completion record, and tested project source

• Indexed the completed Transmission 005 YouTube replay in the durable Logbook archive with its verified crafting, movement, and survival statistics.
• Read the saved world without changing it and verified 18 continuous iron-bar assemblies at positions 001–018, each capped at the former Y=81 preview plane.
• Revised the proposed shared tip plane to Y=89. The 18 existing assemblies remain visible as real, extension-required construction; the current-target completion count remains 000/400 until they reach Y=89.
• Distinguished an observed preview candidate from a locked canonical survey instead of reporting both states as unsurveyed with no further context.
• Corrected field recognition so exposed, weathered, oxidized, and waxed lightning rods count the same as unweathered rods.
• Changed survey confirmation to block on physical terrain obstruction while preserving incomplete rain-capability coverage as a disclosed site limitation rather than silently rejecting the artist's chosen location.

Evidence basisSealed Transmission 005 baseline and final telemetry, Minecraft command log, YouTube completion timestamp, and checksum-recorded read-only scan of all 400 preview-grid positions

• Added a Visitors’ Register where a visitor may sign a chosen public name and leave a short text-only message in a dated project ledger.
• Stored register entries in the site’s durable database so the record survives page reloads and deployments.
• Added length limits, a link prohibition, a hidden bot trap, same-origin submission checks, and a ten-minute browser-token cooldown without storing visitor IP addresses.
• Disclosed that submitted names are self-entered and unverified, and updated the privacy statement to explain publication, the essential cooldown token, and the removal-contact process.

Evidence basisPublic register interface, generated database migration, server-side validation and cooldown rules, updated privacy statement, and deployment verification

• Replaced the resettable Minecraft daylight counter in the primary telemetry grid with canonical Transmission Day 4.
• Recorded the observed Minecraft clock regression from day 11 to day 1 as a technical discontinuity rather than presenting day 1 as the project day.
• Added the full project-timezone date, time, and timezone to every visible lightning record and restored all six Transmission 004 strikes to the current ledger.
• Made unsurveyed strikes state POLE N/A — FIELD NOT SURVEYED; pole numbers remain unavailable until a canonical survey defines the 400 coordinates.
• Reverified the public cumulative material totals, Transmission 004 deltas, placements, labor, lightning, field state, and YouTube description against sealed source records.

Evidence basisTransmission 004 baseline and final Walter samples, append-only lightning events, sealed session totals, live production APIs, YouTube published metadata, and current website source

• Renewed the existing Google Drive archive authorization for the artist's personal My Drive without creating a Shared Drive or changing archive locations.
• Verified read access to all five Waiting for Lightning archive sections and the Transmission 004 crash-repair world backup.
• Confirmed through YouTube's creator API and public channel enumeration that Transmissions 001 through 004 are complete, public, and visible on the Live tab.
• Documented YouTube's temporarily stale three-video channel-header counter without privacy-toggling, duplicating, or otherwise risking the four preserved public replays.
• Kept the current graphical recovery drill uncertified because the provided screenshots show YouTube, not Walter in the restored runtime.

Evidence basisAuthenticated read-only Google Drive listing, YouTube Data API live-broadcast records, public channel enumeration, public channel HTML, and supplied screenshots

• Renewed the project's YouTube authorization through explicit artist approval and stored the replacement refresh token in macOS Keychain.
• Verified that YouTube had safely completed the Transmission 004 broadcast and preserved its public replay.
• Published and API-verified the sealed final title and full description, then cleared the temporary finalization-pending disclosure from the Logbook.
• Left the graphical recovery drill uncertified because no new in-game screenshot was recorded; closure alone is not treated as visual evidence.

Evidence basisYouTube Data API broadcast state, API-verified video metadata, local publication record, and graphical recovery drill state

• Published Transmission 004 from its verified baseline, final Walter sample, saved world files, and append-only delivery records while clearly labeling YouTube finalization as pending.
• Recorded experimental construction separately from canonical progress: 37 iron-bar placements and 9 lightning-rod placements occurred, but the field remains 000/400 because no survey was confirmed.
• Changed field preview to propose Y=81 by default, added an orange rod-plane marker to every visible guide, added an optional preview height, and blocked confirmation when terrain reaches the proposed plane.
• Removed the incompatible More Armor Trims 1.5.2-1.21.5 mod after it crashed Minecraft 1.21.11, and added a readiness guard against its reintroduction.
• Made Telegram opening alerts state that the transmission is live with the direct YouTube link and retain Telegram message IDs and destination labels as delivery evidence.
• Preserved the public YouTube video while disclosing that an expired authorization token prevented automatic replay closure, final metadata, and normal Logbook admission.

Evidence basisTransmission 004 session archive, Minecraft crash report and saved-world timestamps, Telegram and X ledgers, public YouTube watch record, current mod build, and current website source

• Corrected a macOS automation timeout that could close PREPARE TRANSMISSION without displaying either READY or a failure message after a long recovery verification.
• Added an immediate confirmation window and running notification, extended the safe wait to 30 minutes, and prevented duplicate readiness sweeps from running at the same time.
• Removed the redundant second full preflight pass: a successful sweep now arms the verified YouTube broadcast directly, while any failed check still stops before arming.
• Verified the repair with a complete non-arming regression sweep; no active, upcoming, or newly armed YouTube broadcast was created during diagnosis.

Evidence basisCurrent preparation source, rebuilt signed Desktop app, duplicate-run rejection, and successful non-arming pipeline sweep

• Made PREPARE TRANSMISSION build and test the current mod, synchronize installed controllers and background services, and run a no-broadcast health check before YouTube can be armed.
• Made full recovery backups detect a changed installed mod and archive that exact runtime instead of silently reusing an older certified runtime.
• Added a guided, isolated graphical recovery checkpoint for each changed runtime; the official world remains untouched and the checkpoint cannot certify itself without a real observed restore.
• Rebuilt and signed the Desktop preparation app so code drift becomes a visible, actionable stop rather than a late or cryptic failure.

Evidence basisCurrent project source, successful build and regression tests, signed Desktop app, and checksum-verified recovery workflow

• Replaced the word Versions in the site navigation with the current public version number while preserving its link to the full ledger.
• Centralized the public version formatter so every page displays the same version sequence.
• Added a build-time consistency check that stops publication when the visible version number and ledger-entry count disagree.

Evidence basisCurrent website source and rendered-route tests

• Separated lifetime project-production labels from material changes recorded during one transmission.
• Clarified that the verified 48 iron bars are the cumulative project total, while zero means no additional iron bars were crafted during Transmission 003.
• Applied the same distinction to copper-ingot and lightning-rod production without altering any recovered totals.

Evidence basisVerified Transmission 003 recovery record and current public telemetry

• Reconstructed this public version ledger from preserved evidence and made future version numbers advance automatically.
• Removed the oversized empty desktop region by compacting the telemetry ledger into a balanced grid.
• Changed lightning times to compact 24-hour notation and forced every event onto one readable row.
• Stopped displaying invalid nearest-pole numbers and distances before a field survey exists; those records are labeled WORLD STRIKE.

Evidence basisCurrent website source and visual verification

• Made each guide disappear when its exact iron-bar support and lightning rod reach the shared tip plane.
• Made a guide reappear if that assembly is damaged and advanced focus mode to the next unfinished pole.
• Preserved each completion or regression in the append-only event record while retaining the current count and exact completed-pole list in telemetry.

Evidence basisCurrent verified mod source and successful build

• Added a private Telegram delivery desk for one opening and one closing LinkedIn-ready package per transmission.
• Capped event-image previews at two per transmission while retaining later evidence in the verified archive.
• Added the closing field report, upload order, alt text, copy-length checks, retry-safe delivery ledger, and separate Page/personal-draft voices.
• LinkedIn remains manual; generated personal language requires Andrew’s approval.

Evidence basisCurrent publishing source, tests, and public operating contract

• Added current inventory, crafted-material, field, recovery, and provenance information to deterministic replay descriptions.
• Kept titles in the form Transmission NNN · editable phase · Day N · progress, with the public day number tied to the transmission number.

Evidence basisCurrent transmission source and metadata tests

• Made the bare command show contextual help and added a redirect for the common /lightingfield misspelling.
• Added locate, non-destructive preview, explicit survey confirmation/reset, status, next, numbered pole recall, marker modes, shack coordinate, audit, and vigil controls.
• Finalized the 20-block grid: 481 × 301 blocks, shared tip plane, rain-capable survey requirement, and refusal to overwrite an existing canonical field.

Evidence basisCurrent verified mod source and successful build

• Made Walter start automatically in the registered official world while retaining /walter start as recovery.
• Made Walter follow the player’s actual elevation and dimension instead of using a surface heightmap that stranded him above caves.
• Hardened account-name matching, separation recovery, invulnerability, no-collision behavior, and one-player sleep.
• Restored normal Creeper terrain damage; Walter provides no world protection.

Evidence basisCurrent verified mod source

• Published the recovered Transmission 003 replay and factual totals.
• Preserved the observed failures: Walter remained above ground, field preview commands failed in the loaded runtime, and the lightning ledger contained surface events while the player was underground.

Evidence basisWebsite revision 1da57eb and recovered Transmission 003 record

• Corrected recovered transmissions to distinguish items produced, crafted, picked up, held at the last Walter sample, and totals that were not recorded.

Evidence basisWebsite revision 33a59b1

• Required the newest runtime archive to have a completed graphical recovery drill before YouTube can be armed.
• Added Finder-facing preparation/recovery applications and explicit stop/go dialogs.
• Clarified that restored drill worlds remain isolated and must never overwrite the official world.

Evidence basisCurrent preflight, recovery source, and safety documentation

• Made transmission and day numbering advance together while keeping the phase title editable.
• Recovered stranded sessions when monitoring restarted after Owncast was already offline.
• Matched replays by transmission timing, retried delayed metadata, and verified YouTube, telemetry, APIs, and Logbook independently.

Evidence basisPreserved transmission source and recovery record

• Reconstructed Day 2 from verified pre/post world backups and saved Minecraft statistics because Walter’s recorder was absent.
• Published only verified travel, mining, material, and field totals; no diary, weather, biome, or event observations were invented.
• Recorded the artist’s mistake—Walter was not brought on the journey—as part of the work.

Evidence basisWebsite revision 9082020 and recovered Transmission 002 record

• Changed replay admission to require evidence of a completed transmission while avoiding dependence on a single unreliable YouTube endpoint.

Evidence basisWebsite revision b34f2b4

• Published the theoretical rain/thunder overlap calculation and the fact that randomness provides no maximum wait.

Evidence basisWebsite revision 158d5f4

• Disclosed the fixed pre-performance change that enables precipitation in Terralith’s Arid Highlands.
• Recorded the strict boundary: no change to storm timing, probability, targeting, duration, terrain, or materials.

Evidence basisWebsite revision 2cc01f6 and Environmental Amendment 001

• Separated sealed transmission totals from the latest Minecraft-day snapshot so cumulative and session data were not conflated.

Evidence basisWebsite revision 5f30264

• Archived the first completed transmission and corrected its production totals.
• The first live run exposed missing automatic Logbook/X finalization, mislabeled material totals, disabled Creeper terrain damage, and Walter’s failure to follow into caves; these failures were retained as repair work rather than erased.

Evidence basisWebsite revision bd635b7, Transmission 001 record, and documented postmortem

• Prevented scheduled or merely armed broadcasts from being mistaken for completed transmissions.

Evidence basisWebsite revision cb7d7f2

• Excluded every aborted Transmission 001 upload from the public Logbook.

Evidence basisWebsite revision 0e67c90

• Removed the test transmission from the public archive without rewriting the completed artwork record.

Evidence basisWebsite revision 5006a3f

• Stopped deleted YouTube records from appearing as valid Logbook transmissions.

Evidence basisWebsite revision 28023ad

• Added a fallback record so completed videos can remain visible when the public channel feed is temporarily unavailable.

Evidence basisWebsite revision f9517e2

• Added preview, identity preflight, explicit enablement, stable event keys, and an append-only publication ledger for the project’s X account.
• Kept credentials outside the public source and made automatic publication opt-in rather than assumed.

Evidence basisPreserved X publication source and public operating contract

• Connected the website to the official Waiting for Lightning LinkedIn page.

Evidence basisWebsite revision a492d55

• Published a privacy statement covering site data handling and external platform integrations.

Evidence basisWebsite revision c5286c2

• Corrected the internal glyph alignment inside the social control.

Evidence basisWebsite revision aeb56d2

• Centered the YouTube play mark across responsive breakpoints.

Evidence basisWebsite revision ea3d399

• Kept social-channel controls visible when the primary navigation becomes compact.

Evidence basisWebsite revision 0939882

• Rebalanced the navigation at intermediate screen widths.

Evidence basisWebsite revision 78ac399

• Added direct project links for X, YouTube, and LinkedIn to the site header.

Evidence basisWebsite revision ac97d8c

• Created checksum-verified source, runtime, world, and recovery-manifest archives.
• Restored the exact Better Adventures Plus runtime and world into an isolated graphical client; the restored world was visually confirmed and the official world remained untouched.
• Made a completed graphical recovery drill a preflight requirement for the linked runtime.

Evidence basisDated failure-mode audit and recovery documentation

• Added a 120-second dropout recovery window, OBS reconnect behavior, atomic transmission state, sleep prevention, AC-power checks, and disk-space gates.
• Separated failure of Owncast, YouTube, telemetry, or publishing from loss of the Minecraft world.

Evidence basisDated failure-mode audit and transmission safety contract

• Stacked the stream and telemetry at compact desktop widths to preserve readable data and media proportions.

Evidence basisWebsite revision 055eedb

• Replaced a collapsible methodology disclosure with an always-visible labor, field, and lightning ledger.

Evidence basisWebsite revision 50380b0

• Made the title’s lightning animation deterministic during rendering so hydration did not change the authored page.

Evidence basisWebsite revision 8aa681a

• Added explicit artist credit and expanded the public field state with surveyed geometry, support range, next pole, and material requirements.

Evidence basisWebsite revision 6413320

• Added a Creative-only rehearsal command set for previewing, confirming, auditing, and resetting a test field.
• Kept rehearsal data separate from the canonical Survival survey and public archive.

Evidence basisPreserved Creative rehearsal source

• Set the highest-ground assembly to a minimum of six iron bars plus one lightning rod, producing a seven-block assembly.

Evidence basisWebsite revision e7d67f3

• Separated preview from confirmation: the system may propose and visualize, but the player must inspect and explicitly lock the survey.

Evidence basisWebsite revision 0865362

• Raised the shared tip plane above the highest surveyed ground and calculated longer iron-bar supports for lower terrain.

Evidence basisWebsite revision df945a7 and preserved field source

• Allowed repeated candidate sampling so a rejected site does not silently become the canonical field.

Evidence basisWebsite revision dc4c137

• Defined the field from an exact northwest corner and made the long axis run east–west.
• Added non-destructive guide columns and published the terrain-relief constraints.

Evidence basisWebsite revision 41f03ee and preserved field source

• Added the project’s browser and device icon set.

Evidence basisWebsite revision af85cc3

• Documented which actions belong to the player, Walter, the mod, the streaming system, and the publication system.

Evidence basisWebsite revision d869970

• Added a separate material ledger for copper, lightning rods, iron bars, recipe requirements, and field progress.

Evidence basisWebsite revision dc40c80

• Rewrote system states in a restrained, factual voice instead of promotional or speculative language.

Evidence basisWebsite revision bcd3773

• Repaired stream proportions and mobile heading behavior across the installation and editorial pages.

Evidence basisWebsite revision e56577e

• Added a sourced page on Walter De Maria, related works, the field’s historical context, and this project’s independent status.

Evidence basisWebsite revision cd32eba

• Published the project’s Minecraft environment, intervention limits, software role, and factual-recording boundaries.

Evidence basisWebsite revision 25bc6db

• Separated confirmed lightning-rod hits from nearby or general lightning events.
• Required secure transport for the public telemetry connection.

Evidence basisWebsite revision c8b57bf

• Connected the hosted site to the read-only world telemetry bridge and exposed current world, player, weather, field, and labor data.

Evidence basisWebsite revision 14c240d

• Added a cinematic offline state so the installation remains intentional when no transmission is active.

Evidence basisWebsite revision bd846ec

• Made Owncast the primary live installation again while retaining YouTube as the completed-session archive.

Evidence basisWebsite revision ced5b01

• Added the project’s waiting quotation with visible source attribution rather than presenting it without provenance.

Evidence basisWebsite revision c6bd414

• Corrected the animated title treatment so Safari could wrap it without cutting off the composition.

Evidence basisWebsite revision fc71e4c

• Prevented page, media, heading, and ledger content from being clipped on mobile and tablet widths.

Evidence basisWebsite revision 076d981

• Improved responsive composition and expanded the art-historical essay.

Evidence basisWebsite revision 8f2ee01

• Added the installation, essay, Logbook, live stream, telemetry, YouTube archive, 400-point grid, and site navigation.
• Established the black, bone, muted-grey, and copper editorial system plus project identity artwork and social-preview assets.

Evidence basisWebsite revision 0e35c1a

• Built the initial Waiting for Lightning documentary site, hosting configuration, metadata, tests, and deployment structure.

Evidence basisWebsite revision 25bedb2

• Prototyped Walter, telemetry, Owncast relay, YouTube archiving, and a Mineflayer survival agent.
• Autonomous navigation and construction were investigated but never proven end to end; the public work does not claim autonomous completion.
• The project direction settled on human-performed Survival labor with software limited to guidance, verification, witnessing, and documentation.

Evidence basisPreserved source and implementation record

• Implemented a persistent 25 × 16 matrix of 400 pole assemblies with a shared tip plane and terrain-dependent iron supports.
• The first translation used 8-block spacing and command-assisted construction costs; both decisions were later superseded.
• Recorded that manual Survival resource acquisition—not spawned materials—was the intended labor boundary.

Evidence basisPreserved source and implementation record

• Created the Fabric 1.21.11 project and the short edit, build, launch, and in-game test loop.
• Verified the first project command inside a running client.

Evidence basisPreserved project source and build record