Session recording now skips work outside Satsuma's own code
The updates on this site are written from recorded engineering sessions, ingested and then distilled into short public text. A change on a branch now limits that recording strictly to Satsuma's own code. A session that starts outside that scope is skipped entirely. During a session that is in scope, "a file edited outside the tree is counted but never recorded by path."
Sessions already stored were cleaned the same way: 35 out-of-scope paths across 7 stored sessions were scrubbed, and none remain. One ingest ran clean on the new code.
No hard filter was added on the prose a session produces. Writing one would need a list of other project names, and none was guessed at. The site's existing rules on unreleased names remain the guard there.
The change sits in a pull request that has not been merged; until then, the pipeline runs from the branch. Prose in an in-scope session that discusses another project can still reach the distillation step.
- Sessions and files outside the repo roots are never recordedThis site
- Scoping at the session level: skip sessions that start outside Satsuma's code
- Scoping at the file level: count out-of-scope edits without recording their paths
- Scrubbing sessions already stored of out-of-scope paths
- No hard filter on session prose, since it would need a list of other project names; the existing rules on unreleased names remain the guard
- The merge waits for the operator; the pipeline runs from the branch until then
- The pull request awaits merge
- Prose about other projects in in-scope sessions can still reach the distillation step