Updated just now.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card on the website where he manages the business's tasks, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the assistant programs that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. One correction landed this evening: the check this plan added to the set of checks that run before every save was missing a closing line, so on any computer without one particular file every later check in that set was silently skipped; a checker working on a separate review found it, and it is fixed and proven. Still to do here: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and the closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card on the website where he manages the business's tasks, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the assistant programs that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. The wider review Nick asked for the same evening is its own project with its own card and plan, following this rule from birth; its first area is with Nick for his picks. Still to do here: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and the closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card on the website where he manages the business's tasks, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the assistant programs that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. The wider review Nick asked for the same evening is its own project with its own card and plan, following this rule from birth, and its first area is being checked now. Still to do here: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and the closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card on the website where he manages the business's tasks, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the assistant programs that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. The wider review Nick asked for the same evening is now its own project with its own card and plan, following this rule from birth. Still to do here: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and the closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card on the website where he manages the business's tasks, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the automated helpers that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. This evening Nick asked for a separate, wider review of the whole setup, thirteen areas from files and rules through the business task website and the website his family uses for to-do lists, shopping and the children's lessons, on to voice and storage, each read by its own checker with a written brief, then merged into one ranked list of fixes; that review is designed and waits for his go, and it will be its own card and its own plan, not part of this one. The one gap on this project is that the desk computer in Nick's office that runs the scheduled checks is working from a copy of the shared files that fell behind by more than a thousand saved changes after two machines disagreed about the same file, so none of today's enforcement runs on that computer until its copy is brought back in line; that repair belongs to the team that looks after the shared files. Still to do here: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and the closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card on the website where he manages the business's tasks, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the automated helpers that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. Nick asked this evening whether a check, a heartbeat or a watchdog is needed for the enforcement: all three already exist, because the set of tests that runs automatically every night includes the two small tests that print a red warning when an enforcement has been unwired, the hourly retire check records each run, and a separate audit reads every job's run record three times a day. The one gap is that the desk computer in Nick's office that runs the scheduled checks is working from a copy of the shared files that fell behind by more than a thousand saved changes after two machines disagreed about the same file, so none of today's enforcement runs on that computer until its copy is brought back in line; that repair belongs to the team that looks after the shared files. Still to do: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and a short closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card in the list of tasks he manages at hub.heroesandsidekicks.io, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the automated helpers that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. One thing found this evening: the desk computer in Nick's office that runs the scheduled checks is working from a copy of the shared files that fell behind by more than a thousand saved changes after two machines disagreed about the same file, so none of today's enforcement runs on that computer until its copy is brought back in line; that repair belongs to the team that looks after the shared files. Still to do: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and a short closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card in the list of tasks he manages at hub.heroesandsidekicks.io, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are now checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the automated helpers that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; 54 leftover backup copies that were never part of the record were deleted on Nick's word today; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. Still to do: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, the two small checks that print a red warning line when an enforcement has been unwired are added to the set of checks that runs automatically every night, and a short closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card in the list of tasks he manages at hub.heroesandsidekicks.io, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are now checked by people who did not build them: the rule is written once in the single file where Nick's decisions are kept as numbered rules; the automated helpers that work on his files can no longer read or search finished documents, or one old folder on his Mac that is no longer used, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. Two tools were repaired along the way so that this plan could be recorded at all while it sits in a separate copy of the files used by one piece of work in progress: the recording tool now reads the file that lists every project and its plan document from beside the plan itself, and the check that runs when a session ends now recognises a plan whose file is simply named the relevant record. Still to do: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and a short closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card in the list of tasks he manages at hub.heroesandsidekicks.io, and that card names exactly one document, the project's plan, as the record of the project until it is finished. Six of this plan's eight steps are now checked by people who did not build them: the rule is written once in his numbered rules; the automated helpers that work on his files can no longer read or search finished documents, or the folder left over from his previous setup, without a one-time approval Nick taps; a second plan document cannot be saved beside a live one without the same approval; 239 stale documents from 70 project folders sit in dated folders of finished documents with their full change history and none were deleted; one generated list names all 74 retired projects with their dates and folders; and an hourly check reads the task list for finished projects whose plan is still live. Still to do: each task card shows its plan as a clickable link to a web page listing that project's steps and progress, a new task card must name its plan when it is created, and a short closing section of lessons is written into this plan.
2026-09-18 — On 18 September 2026 Nick confirmed a rule for how his projects are recorded: each project is exactly one task card in the list of tasks he manages at hub.heroesandsidekicks.io, and that card names exactly one document, the project's plan, as the record of the project until it is finished. That rule is now written once in his list of numbered rules and is enforced in three ways. First, when a project finishes its plan is moved into a dated folder of finished documents, and the automated helpers that work on his files can no longer read or search those finished documents, or the folder left over from his previous setup, unless Nick approves a one-time exception by tapping a request. Second, a helper cannot save a second plan document beside a project's live plan unless Nick approves it the same way. Third, a live document cannot start pointing at a finished one. Today 239 stale documents from 70 project folders were moved into those dated folders with their full change history, and none were deleted. This project itself has its one task card and this one plan document. Still to do: each task card shows its plan as a clickable link to a web page that lists that project's steps and how far each has got, a new task card for a project must name its plan when it is created, and a short closing section of lessons is written into this plan.
Definition of done: the RULE 51 addendum once in the relevant record, RULE 51 cited once each in CORE §5 and BUILD §5; tickets queued; registry row and bound card exist
Proof: the relevant item → 1
Verified: 2026-09-18 (100%, checked by a Sonnet verifier agent on origin/main a5b3d3d7: addendum count 1, CORE 2, BUILD 1, registry row 1, plan PASS; the card was re-checked by a second Sonnet verifier with ?assignee=all and carries project_file; the CORE sentence it found short of the spec/STEPS exception was corrected in fdbdfb0e89) · 2026-09-18 (100%, checked by two Sonnet verifier agents on origin/main: the addendum count, the CORE and BUILD citations, the registry row and the plan's own checker pass; the card re-checked with the right query carries the file; the CORE sentence the first checker found short of the spec and STEPS exception was corrected in fdbdfb0e89)
Definition of done: the module exists, its test passes, the wiring harnesses fail red, the move list and BEFORE counts are in SUMMARY
Proof: the relevant item
Verified: 2026-09-18 (100%, checked by a Sonnet verifier agent in two fresh checkouts of fdbdfb0e89: PASS 5/5, both wiring harnesses red with their literal line, 247-row move list identical across runs, ten sampled files with no live reader, SUMMARY numbers match) · 2026-09-18 (100%, checked by a Sonnet verifier agent in two fresh checkouts of fdbdfb0e89: PASS 5/5, both wiring harnesses red with their literal line, a 247-row move list identical across runs, ten sampled files with no live reader, the summary's numbers matching)
Definition of done: selftest and wiring test pass; RED and GREEN recorded by the checker; a live file reads
Proof: the relevant item
Verified: 2026-09-18 (100%, checked by a Sonnet verifier agent: RED recorded live — an archive file read and grepped before the lock; GREEN on origin/main — selftest 22/22, six real payloads with the right exit codes and the 🔴 message, the ticket door allows with a scratch ticket and refuses without, wiring test PASS, pointer check 5/5, a miss at 36 ms wall-clock; the one instrument it lacked was the Grep tool itself, so the ignore file's effect through that tool is corroborated, not measured) · 2026-09-18 (100%, checked by a Sonnet verifier agent: red recorded live before the lock, green on origin/main with six real payloads, the ticket door, the wiring test and the pointer check 5/5). NOTE 2026-09-18 evening: the enforcement is on main but NOT yet live on the Mac Studio, whose shared checkout sits on a per-machine side branch 1,122 commits behind main after a blocked merge; its scheduler loaded job code from that checkout at 14:52 local time, so the hourly retire check, the lock in the tracked settings and the three nightly harnesses reach this Mac only once its checkout is back on main. That is the repository lane's fault to resolve, reported to Nick. · 2026-09-18 (100%, checked by a Sonnet verifier agent: red recorded live before the lock, green on origin/main with six real payloads, the ticket door, the wiring test and the pointer check 5/5; the enforcement is on main and reaches the Mac Studio's scheduler only once that machine's checkout is back on main)
Definition of done: selftest and wiring test pass; RED and GREEN recorded by the checker
Proof: the relevant item
Verified: 2026-09-18 (100%, checked by two Sonnet verifier agents in scratch clones with the tracked commit hook installed: selftest 8/8, wiring PASS; the first found the plan-quality gate answering before the birth gate, fixed in 7769cb8ad6; the second saw a second plan refused with the RULE 51 message, the git mv route refused, the relevant record allowed, a ticketed second file allowed, and a first plan in a new folder passed the birth gate)
Definition of done: move list empty afterwards, dated lines appended, AFTER counts in SUMMARY, zero deletions
Proof: the relevant item
Verified: 2026-09-18 (100%, checked by a Sonnet verifier agent on origin/main: 239 renames and 0 deletions since a5b3d3d7, history follows every sampled move, the dated line present with a count that matches, 3 registry rows flipped, 5 sampled files with no runtime reader; it also found two registry rows stale since the 2026-09-04 purge, flipped in the STEP 6 commit) · 2026-09-18 (100%, checked by a Sonnet verifier agent in a fresh checkout of origin/main: 239 renames, 0 deletions, history follows every sampled move, the dated line present with a matching count, 3 registry rows flipped, no runtime reader for any sampled moved file)
Definition of done: the generated file lists every retired project with date and archive folder
Proof: the relevant item
Verified: 2026-09-18 (100%, checked by two Sonnet verifier agents on origin/main: the list generates 74 entries equal to its own count, every named archive folder exists, the union covers every retired registry row and every dated folder; the first found the job lacked the scheduler's entry point and one row misnamed its archive, both fixed in d38ea73b86; the second saw the scheduler's entry point return the dry-run line, write nothing, and the corrected row point at a folder that exists) · 2026-09-18 (100%, checked by two Sonnet verifier agents on origin/main c82deb5e17: list count 74 matches, every archive folder exists, the scheduler entry point runs the dry run and writes nothing, the corrected registry row points at a folder that exists)
Definition of done: a POSTMORTEM section exists and new failure modes are in the registry
Proof: the relevant item
Verified: not yet — steps 6 and 8 remain open; the business workspace link row and the create door sit with the business workspace lane until 2026-09-19 evening, then this lane makes the link row itself · not yet — steps 6 and 8 remain open; the card link row and the create door sit with the lane that owns the business task website until 2026-09-19 evening, then this lane makes the link row itself · not yet — steps 6 and 8 remain open; the card link row and the create door sit with the lane that owns the business task website until 2026-09-19 evening, then this lane makes the link row itself · not yet — steps 6 and 8 remain open; the card link row and the create door sit with the lane that owns the business task website until 2026-09-19 evening, then this lane makes the link row itself · not yet — steps 6 and 8 remain open; the card link row and the create door sit with the lane that owns the business task website until 2026-09-19 evening, then this lane makes the link row itself
⚠️ only 0 of 2 required verifications recorded so far
Definition of done: the link opens the live file from a card; a card without a file is refused; the dry run lists the right cards
Proof: the relevant item