mind: date the backlog — a Filed: header on all 150 draft prompts - #274
Merged
Conversation
The date convention covered the registries and `active/`, and missed the largest pool of tasks the Mind holds: `draft/` is 150 prompts against a handful of live rows, so the dashboard's Recent feed could reach only 10 of the 50 it holds. Most of what had been happening was invisible. Drafts now carry `Filed: YYYY-MM-DD` — the day the prompt was written — beside the `Issued:` an active prompt carries. A prompt keeps its `Filed:` when it advances and gains an `Issued:`; the later, more specific event dates the task. `lifecycle.py dates` covers both state folders, and the two want OPPOSITE readings of the same history — the switch is `--follow`. An `active/` prompt dates from the day it ARRIVED there (being issued is a `git mv`, so following the rename back would report the wrong day); a `draft/` prompt dates from the day it was WRITTEN, wherever it lived then. The 2026-07-13 lifecycle migration `git mv`-ed 42 prompts in one commit: without `--follow` all 42 date from the migration rather than from themselves. With it, the 150 spread across 53 distinct dates. All 150 backfilled from git history, none guessed — the Intake trailer and the claiming registry entry stand behind git as fallbacks, and every backfilled date still names its source in the file. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01L4HPWjv5rdzBAkKpfW1SbR
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
2 participants
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.
The date convention covered the registries and
active/, and missed the largest pool of tasks the Mind holds.draft/is 150 prompts against a handful of live rows, so the dashboard's Recent feed could reach only 10 of the 50 it holds — most of what had been happening was invisible.Drafts now carry
Filed: YYYY-MM-DD, the day the prompt was written, beside theIssued:an active prompt carries. A prompt keeps itsFiled:when it advances and gains anIssued:; the later, more specific event dates the task.The
--followswitchlifecycle.py datesnow covers both state folders, and the two want opposite readings of the same history:--follow?active/git mv, so following the rename back would report the wrong daydraft/This matters concretely: the 2026-07-13 lifecycle migration
git mv-ed 42 prompts in one commit. Without--followall 42 date from the migration rather than from themselves — a fact about the repo's plumbing, not about the work. With it, the 150 prompts spread across 53 distinct dates.The backfill
All 150 dated from git history, none guessed. The Intake trailer (
<!-- formalised by the Intake (Conception) Agent on … -->, carried by 53 of them) and the claiming registry entry stand behind git as fallbacks, and every backfilled date still names its source in the file:Note this required un-shallowing the working clone: a shallow checkout reports its boundary commit as the day everything older appeared, and the guard added in #270 correctly refused those. With full history git dated every prompt on the first source.
Testing
git mvdoes not re-date the backlog, and thatactive/takes the opposite reading of the same history.python3 -m pytest tests/— 181 passed.lifecycle.py checkclean;lifecycle.py datesreports OK.The renderer PR must merge first: this repo's
refreshcheck renders the dashboard using PyAutoBrain'smain.Generated by Claude Code