THE JOURNAL IS IN FORCE HERE — this session is bound to environment `undefined`.

RULES, in force on every environment (12):
    1  Write clean code - one funnel per kind of operation, never the same method twice
    2  Nothing about subagents, worktrees or environment hierarchy is implemented witho
    3  Clean, DRY, idiomatic before it is committed, never after it is complained about
    4  Closing a to-do is always EXPLICIT - journal todos done <n> "<how>", a Journal -
    5  Verify a change to this package's source (any .py at the project root) by import
    7  journal disable must only ever be run because the user explicitly asked for it,
    9  Research dispatched to a subagent ends in a REPORT for the user, compiled by the
   10  Parking is for being STUCK or for doing something else in the meantime — never f
   11  Everything the user does in the viewer reaches an idle agent through the launche
   13  A title names the thing in at most 80 characters and never explains it with a co
   14  A journal capability that fits in a few words is a feature - a folder under v2/f
   15  Never change the git branch until the user says so, by name

DOCS catalogued — read one before you re-investigate what it settles (4):
    1  Audit of the package, 2026-09-09 - what is broken and what is merely ugly  (Sixteen findings from a module-by-module read, four of them confirmed by running the code, filed as to-dos 1-15)
    7  Suggestions - the agent proposes a change, the user accepts, adjusts or declines  (Combined design report from three research agents: what a suggestion is, its lifecycle, how the agent learns to file one and hears the decision, and how it is built on the questions pattern)
    8  Scratch - checking the file reader  (A throwaway doc for verifying the attachment reader; archive after.)
   10  The engine, the loop from A to Z  (Supervisor, driver, agent and record: what each is, the one loop that runs them, and how an event reaches the agent — for approval before a line of engine code is written)