chore: clean stale drafts and schedule the next three posts#32
Merged
Conversation
Cohort A — 7 March drafts written under the original tool-centric series framing, superseded by the pattern-centric arc that the test-suites/SDD/ mythos/three-patterns posts established. Deleted; recoverable from git history if any specific argument is worth lifting later. - Delete content/blog/2026-03-03-zero-cost-component-model.md - Delete content/blog/2026-03-04-loom-post-fusion-optimization.md - Delete content/blog/2026-03-05-meld-component-fusion.md - Delete content/blog/2026-03-06-synth-kiln-wasm-to-firmware.md - Delete content/blog/2026-03-07-proving-the-pipeline.md - Delete content/blog/2026-03-12-hermetic-toolchain.md - Delete content/blog/2026-03-21-temper-governance.md Cohort B — schedule under the new convention "the date in frontmatter IS the publish date": - Add content/blog/2026-04-22-overdoing-the-verification-chain.md (was untracked locally), date set to 2026-04-29 - Re-date variant-pruning-rust-mcdc → 2026-04-30 - Re-date witness-wasm-mcdc → 2026-04-30 + hold = true (post depends on the witness tool existing per issue #29; hold flag prevents the upcoming auto-publish cron from firing it) Convention: draft = true + date <= today + NOT hold → cron will publish. Future-dated drafts wait. Held drafts are parked until hold is removed. Co-Authored-By: Claude Opus 4.7 (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.
Summary
Cohort A — delete 7 stale March drafts. Written under the original tool-centric series framing (each post = one tool), superseded by the pattern-centric arc the recently-published posts established (test-suites → SDD → mythos → three-patterns, where tools are instances of patterns rather than the subject). Recoverable from git history if any specific argument is worth lifting later.
Cohort B — schedule the next three posts under a new convention: "the
datein frontmatter IS the publish date." The upcoming auto-publish cron (next PR) will read it that way.hold = trueThe convention
```
draft = true + date <= today + NOT hold → cron publishes
draft = true + date > today → cron waits (scheduled)
hold = true → cron never publishes (parked)
```
This PR establishes the data shape; the cron itself comes in the next PR.
Test plan
🤖 Generated with Claude Code