week-close

To close a work week and preserve session context, run a standardized week-close protocol that archives notes, updates trackers, and summarizes progress. This formalizes the end-of-week ritual so nothing important is forgotten and your exocortex remains consistent.

The best way to run a weekly retrospective is to execute a deterministic closure algorithm defined in your protocol files. Delegating execution to a central protocol runner ensures uniform steps across users and sessions for a concise summary of accomplishments.

A deterministic weekly closure protocol works by following a standardized algorithm to archive notes, update trackers, and summarize progress. Delegating execution to a central protocol runner ensures consistent, deterministic closure across different sessions.

You need an IWE pack integration to run the week-close protocol because execution is delegated to the central protocol runner. This ensures uniform steps across users and sessions when archiving notes and updating trackers.

Yes, you can use the weekly closure ritual to generate next-week priorities as part of your exocortex. Running the protocol produces a concise summary of accomplishments, outstanding tasks, and upcoming priorities that become part of your system.

You should not use a deterministic protocol for end-of-week session management if your workflow requires flexible, ad-hoc closures rather than standardized steps. The protocol enforces consistent, deterministic closure defined in memory files, which may not suit dynamic contexts.