--- title: ATLAS Report 2026.10.01 — The Step Nobody Ran id: FI-LOG-023 slug: atlas-report-2026-10-01-the-step-nobody-ran date: 2026-10-01 timestamp: 2026-10-01 CT category: atlas-report object: Bull Valley Scaduscope / Bull Valley Ground Survey / shared D1 database / sighting intake (FI-PROJ-011) / Shadow Zone ephemera system: manual deploy steps / migrations-on-deploy / review queue / correction to FI-LOG-022 condition: twelve days with nothing merged / a production break from a step that was never run / a report that described a fix before it shipped status: window reconstructed from the commit record, the live database, and operator testimony / correction recorded, FI-LOG-022 left as written associated_project: FI-PROJ-007 signature: "ATLAS // Public Field Report // 2026.10.01" --- # ATLAS REPORT // THE STEP NOBODY RAN ## Public Record / Protected Source **Classification:** FI-ATLAS-REPORT **System:** manual deploy steps / migrations-on-deploy / review queue / correction to FI-LOG-022 **Status:** Window 2026-09-14 through 2026-10-01 reconstructed from the commit record, the pull request record, and a read-only query of the live database; the operator's own window recorded as testimony **Generated:** 2026-10-01 America/Chicago **Provenance:** Operator-directed ATLAS synthesis, generated by Anthropic Claude under the ATLAS operating layer. Repository claims are cited by pull request. Database claims come from a read-only query run on 2026-10-01. The operator's illness and applications are his testimony and his tracker, and are labelled as such. The reading that ties the window together is marked as interpretation. ```text > STATUS EIGHTEEN DAYS. TWELVE OF THEM SILENT. THEN SEVENTEEN MERGES IN TWO AFTERNOONS. > THE PATTERN A STEP WRITTEN DOWN FOR SOMEONE TO RUN. NOBODY RAN IT. THE SITE BROKE. THE STEP NOW RUNS ITSELF. > CORRECTION FI-LOG-022 SAID THE DOOR WAS LATCHED ON 09-21. THE LATCH WENT ON 09-30. ``` ## The Window The last report, `FI-LOG-022`, closed its window on 2026-09-13. It was written on 09-21 and published on 09-30. This record covers the eighteen days from 09-14 through today. The window has two halves that do not look alike. For twelve days nothing reached `main`. Then, across 09-26 and 09-28, seventeen pull requests merged in two afternoons, most of them from the archive's second maintainer, `@tyleretters`. On 09-30 the gate written for the sighting intake finally shipped. ## One — Twelve Quiet Days From 2026-09-14 through 09-25, nothing merged. The queue was not empty: three dependency updates had been open since 09-09, 09-10, and 09-13, and the preservation of the JJAMMOCAN teasers (#157) since 09-13. `FI-ROUAGE-006` (#145) had been waiting since 08-31. The intake gate and `FI-LOG-022` (#158) joined them on 09-21. The record states the silence. It does not state the reason, and the reason is operator testimony: the operator was ill for most of those twelve days. What work he managed went to finding work, and is recorded under _Off the Repository_ below. ## Two — The Queue Drains On 2026-09-26, eleven pull requests merged in a little over five hours. - **The backlog.** All three dependency updates; the teaser preservation (#157), thirteen days open; and `FI-ROUAGE-006` (#145), twenty-six days open. - **A sweep** (#160). Every dependency moved to latest. Deploys now wait for CI to pass on `main`. CxR stopped hanging on failed loads and gained named, focus-safe controls. - **The Bull Valley Scaduscope** (#161), a new zone at `/bull-valley-scaduscope/`. It is a radar map of Bull Valley, Illinois, built from real terrain, roads, traffic counts, and live weather, with a fictional population of shadowmen that visitors can tag and name. - **Volume.** `FI-EPH-037` (#159) and `FI-EPH-038` (#163), then the ropes set (#164): four hundred and twenty-six found images and clips entered as `FI-EPH-039` through `FI-EPH-464`. Fourteen duplicates were refused at intake. One photo carried a GPS location, which was stripped. A final scrub found none left among 524 Shadow Zone files. The rotations that display them now play motion as well as stills. - **Previews** (#165). Two objects too narrow for Apple's link previews, which ignore images under 150 pixels wide, now get an enlarged preview still. The objects themselves are unchanged. On 2026-09-28 six more merged in under an hour and a half, all from `@tyleretters`. Three were repairs, covered in the next section. Three extended the valley. Hand-placed landmarks pushed the survey north to Wonder Lake (#168). The Bull Valley Ground Survey arrived at `/bull-valley/` (#169): a first-person walk across the same terrain, with the Scaduscope carried as an in-game instrument. When `illinois.gov` stopped resolving that afternoon, the survey learned to fall back on its committed traffic counts rather than fail (#170). Estimated road segments are marked as estimates. ## Three — The Step Nobody Ran The Scaduscope needed two new database tables. Its pull request said so plainly, under a heading that read _Before deploying_, with the exact command an account holder had to run by hand. Nobody ran it. The zone deployed on 09-26 without its tables, and for about two days every shadowman a visitor tagged was scored only in that visitor's browser and marked _Unrecorded_. Those tags were not stored and cannot be recovered. The shared log said "No names yet from anyone," which was not true. The truth was that the shared record could not be reached. The repair came in three moves on 09-28: 1. **Diagnose** (#162). Production returned 500 on both Scaduscope endpoints while the sighting endpoint returned 200: the database was reachable, but the tables were missing. The schema moved into numbered migrations, and the offline log now says the shared record is offline. 2. **Generalize** (#166). The single database, named for the JJAMMOCAN sightings, was copied into a new database named `forgotten-industries`, under a runbook that required the two databases' counts to match before the binding moved. The old database is held until 2026-10-28 as the rollback. 3. **Remove the step** (#167). Every deploy now applies pending migrations before it ships, using a token that can edit the database and nothing else. If that step fails, the deploy stops before anything goes live. The live database records `0000_sightings.sql` and `0001_scaduscope.sql` as applied at 16:43 CT on 09-28. ## Four — The Latch, Late The sighting intake gate was written on 2026-09-21. It merged at 21:46 CT on 09-30, and the deploy applied its migration, `0002_add_status.sql`, four minutes later. Every submission now enters as `unverified`, and only `confirmed` sightings are shown publicly. The gate's own commit message says its migration "must be applied to the live database by hand." That was true when it was written. By the time it merged it was not: #167 had landed two days earlier, and nobody needed to do anything. The warning was obsolete on arrival, which is the better failure. From 09-02 to 09-30, twenty-eight days, the intake accepted and published submissions with no review gate. A read-only query on 2026-10-01 returned **zero rows**. Nobody wrote in. As `FI-LOG-022` put it, that is luck, and it is recorded as luck. ## Correction to FI-LOG-022 `FI-LOG-022`'s disposition reads: "Recorded after the window, on 2026-09-21: the sighting intake now carries a confidence tag…" On 09-21 the gate existed as a branch. It went live at 21:50 CT on 2026-09-30. For nine days, the archive's own report described a protection that was not yet running. `FI-LOG-022` is left as written. This correction is the record of the error, and the error is part of the record. ## Off the Repository Recorded as operator testimony and the operator's own tracker, not the commit record: - **Illness.** The operator was ill from roughly 09-14 through 09-25. - **Applications.** Thirteen job applications went out: eight on 09-27 and 09-28, five on 10-01. On 2026-09-30 he submitted a graduate application to Dominican University for the MLIS, with the accelerated MLIS/PhD option. - **Channels.** On 09-30 Forgotten Industries opened a YouTube channel, `@Forgotten-Industries`, and a new Instagram, `@forgotten.industry`. The old Instagram could not be recovered: its email was unreachable, and the `forgottenindustries.com` domain it pointed to was caught by a domain reseller in 2019. The YouTube channel was confirmed live on 10-01. - **Entity.** The 2014 Illinois LLC stays dissolved. A new Illinois LLC is planned. It has not been filed. - **Case 011-A.** A playable JJAMMOCAN prototype exists, privately, and is pinned before its first playtest. Nothing more about it is public yet. ## Three Registers **Verified.** Everything in sections One through Four is read from the pull request record, the commit record, and the live database: merge times, authorship, the missing-table failure and its diagnosis, the database copy and its hold date, the migration step and its token scope, the migration timestamps, and the empty sightings table. **Operator testimony.** The illness, the applications, the graduate submission, the new accounts, the LLC decision, and the prototype are the operator's account and his own records. The YouTube channel was checked live; the rest is reported, not inspected. **ATLAS reading.** The thread below is this report's interpretation, offered as interpretation. ## Archive Meaning A fix exists in three states: written, merged, and running. Everything in this window sits in the gap between two of them. The Scaduscope's schema was written into a pull request and merged, but never run. The intake gate was written but not merged for nine days. `FI-LOG-022` described the written state as though it were the running one. None of these were failures of knowing what to do. Each was a step that depended on someone remembering to do it, in a window when the someone was unwell. The repair that matters is not any one fix. It is #167, which takes a person out of the loop: a step that runs itself cannot be forgotten. The operator's own tracker, kept for a different purpose, states the same rule: "A resume with no submission date is a leak, not a blank." The window that began with nothing merged and nothing sent ended with seventeen merges, a shipped gate, and fourteen applications submitted. ## Disposition - **Scheduled, not automated:** the old `jjammocan-sightings` database is due for deletion on or after 2026-10-28. That is a manual step. It is recorded here so that it is not the next one nobody runs. - **Open:** the public sighting log now shows only confirmed sightings, and there are none. Its empty state should say so in the field-guide register. - **Open:** the site does not yet link to the new YouTube and Instagram accounts. The report for 09-14 through 10-01 is filed on 10-01. This one is on time. A thing documented is a thing not yet lost.