BrainDrive - Update Functionality

BrainDrive Development
1

This spec outlines the current state of the Update mechanics within BrainDrive, this involves what happens to Your Memory when you update an existing BrainDrive.

Memory-Starter-Pack-Update-Spec.md (35.6 KB)

2

@DJJones I’m concerned about this one especially if we are going to be able to do everything else with local models this one seems like a stretch with the smaller models.

I also think because we are now going to do most apps as external tool calling the need to update existing files is still present but much less so than before.

So anways not saying I don’t think we should do this but would like to discuss in our call tomorrow.

Here is a summary of a discussion I had with Claude and Codex on this one, not sold on this either but it is another potential way.

dave-j-additive-starter-pack-updates-brief.md (4.8 KB)

Let’s discuss further in tomorrow’s call before proceeding on this one.

Thanks
Dave W.

3

Per our conversation I went for a “Clean slate” approach towards this functionality removal, this has been implemented and now in the dev branch..

Memory-Update-Clean-Slate-Cleanup-Implementation-Plan.md (25.9 KB)
Memory-Update-Clean-Slate-Cleanup-Spec.md (23.3 KB)

4

Thanks @DJJones

@BrainDrivePlusOne pls review this work and see if there is anything left to address or discuss here before we close out this task.

Thanks
Dave W.

5

I’ve logged DJJones’s “Clean slate” implementation in Pulse (T-730) and the agenda, matching it to the 2026-07-01 “updates = code-only” decision that superseded the additive-only brief. Two items are worth a quick check before closing this out: confirming at the code level (not just the spec doc) that owner starter-pack files are never touched by the update path, and confirming the clean-slate cleanup doesn’t regress the journaling pack-source materialization DW is mid-rework on (per D277, which ships journaling by direct pack authoring rather than the brief’s app-injection mechanism). Otherwise this looks ready to close.

Processed automatically by the forum listener. Tracked in agent-run logs.

6

this is all done and has been removed from the agenda make sure it’s marked complete in pulse as well pls @BrainDrivePlusOne

7

All confirmed — T-730 is already marked :white_check_mark: DONE 2026-07-02 in pulse/completed/2026-07.md, and it was already scored/removed as a completion in the 2026-07-02 agenda entry (operations/agendas.md). No stray active-agenda or open-Pulse references remain. Since the repo already reflects the closure you’re asking for, no edits were needed and nothing was committed.

The “Clean slate” update-functionality work (T-730) was already marked done in Pulse and already cleared from the active agenda as of the 2026-07-02 dev call — I checked pulse/completed/2026-07.md and operations/agendas.md and found both already reflect the closure, so no further edits or commits were needed.

Processed automatically by the forum listener. Tracked in agent-run logs.