brain:update

To save conversation context for cross-session task tracking, scan the active session exchange and write new entities, relationships, and decisions to a shared project brain database. This captures full context so important facts are not lost across terminal resets or parallel workstreams.

The best way to resolve memory sync conflicts is to compare new session information against the current project brain state. This conflict-aware comparison preserves newer or more advanced task statuses during the ordered write process to prevent overwriting updated data.

To log end-of-session events and tasks into a persistent project brain, invoke a session capture process that reviews the entire conversation. It identifies new tasks and events, applies deduplication rules, and executes ordered writes to the database.

Yes, project memory synchronization requires brain database detection to function. The process reads the current state from this database to perform conflict resolution and deduplication before safely writing approved updates and mirroring results to connected memory stores.

Yes, you can mirror ordered writes from a project brain database to connected memory stores. After writing approved updates and completing the knowledge refresh, the synchronization process mirrors the results into available memory stores with safe fallbacks.