learning

Learning

The loop runs session → diary → pattern → instinct → activation, and every step that could change future behavior waits for a person. Learning is off until someone enables it, and an instinct affects nothing until someone activates it.

Which job

The user wants	Go to
to record what this session decided or discovered	Capturing a diary
to know what keeps recurring across sessions	Reflecting over diaries
to remember one specific thing, right now	Saving an instinct by hand
to see or change what the subsystem has proposed	Reviewing what activates

For handing unfinished work to the next session, this is the wrong skill — /sessions writes handovers. A diary is for reflection, not continuity.

Capturing a diary

Step 1 — Check there is something worth recording

At least one must be true: a non-trivial decision was made, a challenge was solved, the user expressed a preference, or a technique was discovered. Pure Q&A, a retried build, exploration that decided nothing, and one-line fixes get no diary. Say so and stop.

• Done when one of the four criteria is named, or the session is declared not worth a diary.

Step 2 — Check for a draft before writing anything

Run arcforge learn diary path --draft --session <id> and read that file if it exists. A background pipeline writes one after a substantial session.

A draft that exists is the entry — never write a fresh one alongside it. Doing that leaves two diaries for one session: a duplicate final entry and an orphaned draft nobody reads.

Its ## Session Metrics section is already correct — preserve it verbatim.

Then take the enrichable sections one at a time. Which shape you write depends on one thing: were you in that session?

You were — replace the <!-- TO BE ENRICHED --> line with what happened.

You were not — the finished section keeps the marker and gains a note under it:

## Decisions Made

<!-- TO BE ENRICHED -->

_Not recorded — this session is not in this conversation's history._