# 000001 Session Closing Ritual

**Date:** May 2026\
**Status:** Active\
**Owner:** NikiDigitals\
**Version:** GitBook — Thinking Layer

***

## What It Is

At the end of every working session in the LES project, ten minutes are spent on four things: updating the master context document, running a documentation check, committing everything to GitHub, and writing a short journal entry. This is the session closing ritual. It takes ten minutes. It is not optional.

That last sentence deserves unpacking, because the temptation to skip it — especially after a long and productive session — is real. Understanding why it is not optional requires understanding what happens to a project that lacks it.

## The Problem Without It

A project built session by session, over five years, with an AI assistant that has no memory between conversations, is inherently vulnerable to drift. Decisions made in one session are forgotten by the next. Documents produced in a chat but not committed disappear when the chat is closed. The reasoning behind an architectural choice fades within days if it is not written down while it is fresh. Progress that felt clear and solid in the moment becomes ambiguous in retrospect.

The session closing ritual is the mechanism that prevents all of this. It is not overhead — it is the minimum viable discipline for a project of this duration.

## The Four Steps

{% stepper %}
{% step %}

### Step one — update the master context

The master context document is the memory of the project. Every completed task, every new decision, every change in status is recorded here before the session closes. This document is what the next Claude session reads to understand where the project is. If it is not updated, the next session starts with stale information.
{% endstep %}

{% step %}

### Step two — documentation check

A brief review against the GitBook trigger point framework. Did this session produce a decision worth an ADR? A learning milestone worth a journal entry? A completed piece of work worth a GitBook narrative? If yes, the document is written now or logged as an explicit task for the next LES-DOCS session. If no, nothing is produced and nothing is missed.
{% endstep %}

{% step %}

### Step three — commit to GitHub

Everything produced in the session — the updated master context, any new documents, any updated documents — is committed to GitHub before the session closes. This is the rule that makes the project real. If it is not in GitHub, it did not happen.
{% endstep %}

{% step %}

### Step four — journal entry

Three to five sentences. What was done, what was the most significant moment, what comes next. Written while the session is still fresh. Over five years, these entries become a complete record of the learning journey — honest, timestamped, and impossible to reconstruct after the fact.
{% endstep %}
{% endstepper %}

## Why Ten Minutes

Ten minutes is enough. The ritual is not a writing exercise — it is a closing procedure. The master context update is structured and fast. The documentation check is a brief scan against a known framework. The commit is a mechanical action. The journal entry is three to five sentences.

If the ritual takes longer than ten minutes, something is wrong — either the session ran too long without intermediate commits, or the documentation check revealed a significant gap that should have been caught earlier. Both are signals worth noting.

## The Long-Term Return

A project that closes every session with this ritual builds something over time that cannot be recovered if the ritual is skipped: a complete, honest, timestamped record of how an expert was made from a beginner. That record is the most compelling portfolio artefact the project produces. It is also the thing that is most easily lost — not through catastrophe, but through the accumulation of sessions that ended without ten minutes of discipline.

The ritual is ten minutes. The return is five years of recoverable, credible, professional work.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nikidigitals.gitbook.io/les/02-project-governance/session-and-chat-protocol/000001-session-closing-ritual.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.