Product · Continuity · The Cognition Factory · v1.0

Between sessions — leave a clean stop, pick up without thrash

Skill that only works in unbroken four-hour blocks is a vacation plan. Real calendars have jobs, kids, noise, and tired evenings. Between sessions is how The Cognition Factory stays honest about that: you stop cleanly, and next-time-you knows where to begin.

In one line. Write where you were and what you meant to do next — then stop. Tomorrow starts from that note, not from scrolling old chat.

Why this matters

Most tools optimize for the session you are in. They forget the handoff: the two minutes that decide whether you restart or re-find the thread for half an hour. Save place is that handoff — simple on purpose.

Deep learning builds the map.
Practice proves the gaps.
Save place keeps the loop alive across messy weeks.

What “save place” does for you

When you leave

Capture a short Last left off picture (what you were in the middle of).
Write one concrete Next time I will… (deeper map work, more practice, or a real check).
Confirm the save — so the board, not your memory, holds the thread.

When you return

Open Save place (or Home, if it surfaces a resume line).
Read last left off + next steps.
Jump back into Deep learning or Practice without reconstructing the week from chat history.

A good park note (examples)

Short and specific beats long and vague.

“Next time I will re-sketch the CVP map without notes, then one closed-notes drill.”
“Next time I will rework the three method errors from tonight’s practice pack.”
“Next time I will finish the last section of the map, then a short teach-back out loud.”

Avoid: “keep studying” or “review everything.” Those dump the planning tax back on tomorrow’s tired brain.

What stays open vs what you park

Conversationally:

Live work in Deep learning or Practice can still be there when you come back — Save place is not “close and wipe.”
The park note is the intentional handoff: the one sentence you would want if the chat scrolled away and life got loud.
Earlier saves can be reopened when you need an older breadcrumb — secondary to the live board.

Interruptions are normal

Meeting pulls you out

Sixty seconds: write next step → save place → leave. Do not try to “finish the thought” in the hallway.

Only twenty minutes free

One map node or one short practice run still counts. Park what the next short block should be.

Days away

Re-entry tax is the enemy. A clean last note beats heroic memory. Open Save place first; then work.

How this shows up in the app

High-level only — the features you will actually touch:

Save place screen — resume board, next steps, park control.
Home — may surface a soft resume line when you parked something concrete.
Deep learning / Practice — where the work happens; each keeps its own chat context.

Product code for this engine is CSS (save place). You do not need the code to use the feature.

What this is not

Not surveillance of your study time.
Not a second LMS full of compulsory modules.
Not a dump of internal file layouts or operator warehouse rules — those stay off the public path.

Smell test. If your notes die when the chat ends, you have a mood, not a system. If next-time-you can start in under a minute from a clear note, the between-session loop is working.

Next steps

Desktop app overview — doors, quieter tools, short session recipe.
Solo path for busy adults — why the full loop exists.
Save place on the site — public narrative for the same idea.
Talk with us — if you want this loop for a team or household.

Public continuity overview · shallow depth · no implementation detail · v1.0