Publish the queue — the commit that missed the #12 merge - #13
Merged
Conversation
Five posts were sitting on future dates as a weekly drip: 08-21, 08-28, 09-04, 09-11 and 09-18. A drip schedule is a marketing mechanism, and this blog is the running record of work in progress. Holding finished writing back for three weeks does not serve anyone reading it to find out what is happening. All five re-dated to 2026-08-17 and published. Explicit times in the frontmatter preserve the order they were written in, so the day reads in sequence rather than arbitrarily: 09:00 Below the waterline is not a stable state 10:00 Open source permanently, and how it gets paid for 11:00 Valuable real estate, claimed in the open 12:00 One standard, twice — and ninety-odd, never 13:00 Nobody should be writing industry rulesets No content changed. Times are for ordering only. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the queue-clearing work that missed the #12 merge.
PR #12 merged at
5a5fbf9— the exploratory post only. The commit re-dating the whole queue landed on that branch minutes afterwards and was never included, so five posts are still sitting on future dates and invisible. My fault: I pushed to a branch that already had a live PR.Same commit, cherry-picked onto current
main. No content changed — renames plus onedate:line each.What this publishes
Five posts move from future dates to 2026-08-17:
Times exist only to preserve the order they were written in, so the day reads as a sequence. Permalinks are date-based, so nothing depends on them.
A drip schedule is a marketing mechanism. This blog is the running record of work in progress, and holding finished writing for three weeks does not serve anyone reading it to find out what is happening.
Verified
jekyll build, no--future: nothing skipped, all six of today's posts render.feed.xmlcarry them newest-first in the order above, with the alias post published earlier today beneath them.