2026-09-07 to 2027-03-01
The publication calendar
This site has a finished distribution machine and an empty record of having used it. The graph maps 100 channels and 70 edges; nothing in this repository records a single outbound publication. So the schedule below is mostly not new writing. Sixteen of these twenty-six weeks release work that was finished months ago and sent nowhere.
The part that makes it real is not this page. It is a test. A slot missed by more than 3 days fails the build, the same way a leaked hash or a silent backup does, and the only way to clear it is to publish the thing or to log out loud that you decided not to.
01
The backlog band
Weeks 1 to 16 contain no net-new long-form writing, enforced by a test rather than by intention. Six hashed open-data releases, a submission-ready paper and a shelf of published-but-unsent essays are the calendar. Two weeks are dark for the November trip, because a calendar that schedules work during a flight is a calendar you abandon in week ten.
The Ukrainian frequency list, as an open release
Due nowrelease / via correspondence / then indexnow, site-feed, newsletter / needs indexnow-research-paths
First because reader one ranks first and a correspondence already exists. This is the only lane in the whole picture with a demonstrated result. Its prerequisite is the IndexNow path-filter defect from the inventory: research surfaces are content-as-code, so seed-content.yml has never pinged for them. Fix that in the same week and every later slot inherits a working discovery edge.
Counting the Killings, including the record-level overlap layer
Scheduledrelease / via newsletter / then indexnow, site-feed, correspondence
The first newsletter send. Aggregates only, never a re-hosted roster, and the non-partisan red line is doing real work here. The overlap finding (the trackers converged, and a two-source capture-recapture is invalid on nested lists) is the part a stranger can check.
Pingree Grove Studies, thread one: the rulebook as open data
Scheduledrelease / via correspondence / then indexnow, site-feed, newsletter
Reader three, and the slot most likely to convert into something concrete. Goes to village staff and the clerk directly, because that is where this audience is. The FOIA log is the second artifact in the same send.
One Load-Bearing Company, with its citation ledger
Scheduledrelease / via newsletter / then indexnow, site-feed
Thirty relationships, thirty disclosure sources, twenty-four of thirty deep-linked to a primary document and the other six honestly null. The published /audit ledger is what makes it citable rather than merely interesting.
SAGEN and SAGEN-Bench, submitted
Scheduledsubmission / via arxiv / then correspondence, site-feed
Submission-ready and unsubmitted since before this calendar existed. Submitting a finished paper is releasing backlog, not writing something new, so it belongs in this band. Highest-leverage single slot for reader two, and per the disclosure policy the follow-up correspondence stays private.
How Would I Know: the enforcement claims register
Scheduledpointer / via newsletter / then indexnow, site-feed
No hashed release, so it travels as a pointer with one finding attached: the denominator switcher, where swapping a counting convention flips a verdict in place. Symmetric scrutiny and the non-partisan line are the whole point of the piece and the whole risk of the send.
Italian as Black, and the trainer
Scheduledrelease / via newsletter / then indexnow, site-feed, social
The most human thing in the catalog: the legibility argument turned on its own author, 902 games, 95.1 percent carrying the same unexamined third move. The one slot where the social lane is worth spending, because it is the one piece that survives being seen out of context.
The Legibility Gap: Ukraine recovery field data
Scheduledpointer / via newsletter / then indexnow, site-feed, correspondence
Four threads of recovery legibility, quarterly refresh, and the empirical companion to the Wartime Edition essay. Correspondence lane overlaps reader one, so it goes to the same list built in week 1.
The Legible Fold
Scheduledpointer / via newsletter / then indexnow, site-feed
OUT BEFORE FRIDAY. Departure is 2026-11-06 and this slot's Monday is 11-02, so it ships at the start of its week rather than the end. Chosen for this position because it is self-contained: a rotatable prediction colored by the model's own confidence, nothing that generates follow-up needing attention from abroad.
Dark: traveling
Darkdark
2026-11-09 to 11-15. Abroad. Nothing is scheduled, nothing is owed, and the missed-slot gate does not fire, because a dark week is a decision rather than a gap. This is the difference between a calendar you can keep and one you abandon in week ten.
Dark: traveling and return
Darkdark
2026-11-16 to 11-22. Return lands 11-17 with a Taipei layover behind it. Publishing on the two days after a fifteen-hour flight is the kind of plan that gets a calendar thrown away, so the week is dark on purpose.
The Warehouse
Scheduledpointer / via newsletter / then indexnow, site-feed
Re-entry slot. Deliberately the lowest-effort send in the band: a finished essay, a pointer, one finding, no new assets. Coming back from two dark weeks is the second most likely place to drop the habit.
Ninety-Seven Percent Off
Scheduledpointer / via newsletter / then indexnow, site-feed
Finished, published to the site in July, never sent anywhere.
The Sorting Machine, Wartime Edition, plus the Claims Ledger
Scheduledpointer / via newsletter / then indexnow, site-feed, correspondence
Paired on purpose. The essay is the argument, the cross-paper Claims Ledger is the receipt, and the ledger re-verifies in the reader's browser. This is the send that demonstrates the house method rather than describing it.
Signed, With Assistance
Scheduledpointer / via newsletter / then indexnow, site-feed
Published to the site in July 2026 and never distributed.
The catalog: twenty-four entries and six open datasets
Scheduleddigest / via newsletter / then indexnow, site-feed, correspondence
Closes the backlog band. Nothing new is written: it assembles what the previous fifteen weeks sent, names the six hashed releases in one place, and gives readers one and three a single link worth forwarding. The last slot that can be filled without making anything.
02
The open band
Weeks 17 to 26 may contain new work, and every piece of it has to name what it pushed aside. That rule is also a test: new work in this band with no stated cost fails the build. The last slot publishes nothing and reads the ledger instead.
Between Systems, episode one
Scheduledepisode / via correspondence / then podcast-feed, site-feed, newsletter / needs backlog-band-complete
The standing advice for a year has been to ship one episode before building more infrastructure. Since that advice, two complete show architectures were built instead. This is the slot that stops being ironic. The guest page is the deliverable; the audio is exhaust.
Displaces: Two backlog slots' worth of effort, and concretely the /store and /reading distribution that would otherwise have filled weeks 17 and 18. Deferred to here rather than earlier because it is the only item in the picture that is new production work, and the backlog band exists to stop new work from displacing finished work.
Submit both feeds to the podcast directories
Scheduledsubmission / via directories / then podcast-feed / needs between-systems-ep1
Displaces nothing: it is unlocked by week 17 rather than competing with it. All seven directory edges in the graph are correctly marked planned today because a directory cannot ingest a feed whose only item has an empty enclosure. One episode makes seven edges legal at once.
The Legibility Desk, episode one: the self-audit
Scheduledepisode / via newsletter / then legibility-feed, site-feed / needs between-systems-ep1
The show opens the only honest way a critique show can, by scoring its own house first. Recording it is new work; everything it says was written months ago.
Displaces: A new research entry. The script, rubric, steelman and both receipts already exist and have since July 2026; only the audio is missing, so this is closer to backlog than the kind marks it.
Narrate the 2026 catalog, first batch
Scheduledaudio / via newsletter / then radio, site-feed
Closes the gap the inventory found: narrated audio exists on catalog entries 01 through 09 only, so the entire 2026 run, which is the strongest work, has nothing for the radio surface or any audio-shaped channel to carry.
Displaces: New writing. Nothing is authored here; prose that has existed since 2026 finally gets a voice.
Pingree Grove Studies, thread two: the money
Scheduledrelease / via correspondence / then indexnow, site-feed, newsletter
The money thread is marked planned in the dataset today and stays empty until there are real sourced figures. Reader three, public records only, and the thread most likely to matter to the people who live here.
Displaces: Nothing. By this week the finished backlog is exhausted, so this is the first slot where new field work displaces no published-but-unsent artifact. That is the milestone, not the thread.
The systems digest: store, benchmarks, architecture
Scheduleddigest / via newsletter / then indexnow, site-feed
Twenty-nine reusable systems with live usage metrics, the self-checking evals, and the architecture map. Nothing new is written. This is also the one slot aimed at reader four, who is ranked last and gets one send in twenty-six weeks, which is what ranking last means.
The frequency list, version two
Scheduledrelease / via correspondence / then indexnow, site-feed, newsletter / needs ukrainian-frequency-v1
Twenty-two weeks after version one, with whatever the correspondence from week 1 taught. A release that answers its own readers is the strongest evidence the correspondence thesis is right, and the strongest evidence against it if nobody replied.
Displaces: A fourth podcast episode. Reader one outranks the show, and a second version of the list is worth more to them than another hour of audio is to anyone.
Between Systems, episode two
Scheduledepisode / via correspondence / then podcast-feed, site-feed, newsletter / needs between-systems-ep1
The referral chain in the catalog exists for this: a guest who suggests the next guest is the mechanism, and it cannot start until episode one exists.
Displaces: One backlog-style digest. Guest-driven, so the date is a commitment to ask, not a commitment to publish; if no guest says yes, this slot must be logged as skipped with a reason rather than quietly re-purposed.
Unratified, finished
Scheduledrelease / via newsletter / then indexnow, site-feed
Catalog entry 13 has been In Progress since June 2026. Finishing something already begun is the cheapest new work available.
Displaces: Nothing. It completes a catalog entry that has been In Progress rather than starting a new one.
Review: read the ledger, plan the next twenty-six
Scheduledreview
No atom leaves. The ledger is the evidence: how many slots published inside their grace window, how many were logged skipped and why, whether correspondence produced replies, and whether the reader ranking survived contact. The calendar expires after this week, and the gate fails when it does, which is the mechanism that forces this review to actually happen rather than the schedule quietly running out.
03
What counts as published
A page going live at a URL is not a publication, which is how a catalog can be full of work marked Published and empty of distribution.
Published means an emission event with a date, an artifact, and an external witness: a broadcast id, a submission id, a named recipient. Something that would still show the send happened if this repository were deleted. Entries live in the publication ledger, the ledger is the only thing the test reads, and an entry with no witness is rejected as a claim rather than a record.
04
Where the slots come from
Elsewhere: the distribution graph this schedule feeds, the research catalog it is emptying, the open notebook that carries most of the sends, the interview show waiting on week 17, and the radio, which has nothing from the 2026 catalog to play until the narration slot lands.
This is the list you would be on
Most of the slots above are sent to the newsletter. Subscribing is how you find out whether the schedule survived contact.