What happens
The opener walks the context spine, in order and nothing else: the stable pole (the project’s vision and its current mode), then the active dynamic context (where the work stands right now, resolved through the routing index), then the newest handover record — what the last session left for this one — and finally the fieldnote buffer’s pressure reading. Four reads, no scanning: the memory is loaded by following pointers, never by crawling the repository.
Then it reports back and stops: where the project stands, what is queued, what stands open, what waits on the owner. The queue is an offer, never a mandate — the owner’s request is primary, and the session waits for direction before touching anything.
Why it’s shaped this way
One conversation, one open loop: entry declares the project, closing is universal. Giving each instance an opener in its own name does two quiet things — it makes the memory-load a single word, and it makes the session’s jurisdiction unambiguous from its first act. The specimen here is the baseline’s own fractal; a project born through begin gets the same file under its own name, pointed at its own spine.
The shipped specimen: fractal.md ↓ — the baseline’s working copy, verbatim, stamp and all. Its counterpart at the other end of the session is close.