Handoff

Preserve enough session context for a fresh agent to orient quickly, then keep the user in control of what happens next.

Creation and resume are deliberately open at their edges. The managed store and ce-handoff/v1 metadata are defaults that make CE-created handoffs easy to find; they do not restrict where a handoff may be created or what a user may resume from. A resume source may come from any person, agent, or system and may use any readable format.

Route the invocation

• A bare invocation always creates a handoff.
• create [focus] explicitly creates one. Use focus as the intended objective for the next session.
• resume [source or keywords] reads an explicit continuity source or discovers likely candidates.
• Natural-language creation and resume intent follows the same routes. This does not apply to ordinary requests to continue the current session unless the user expresses handoff intent.

Create

Read references/create.md before writing anything. That read is not optional. It defines the managed-store shell block and path rules, the ce-handoff/v1 frontmatter contract, the body contract, and the completion report.

Create one immutable handoff at the destination the user requested, or use the managed temporary store by default. The handoff supplements authoritative artifacts; it does not replace them. Write or publish it with existing capabilities. When the user named another path, folder, format, or publication destination, honor it using an appropriate available capability, including an installed publishing skill. Do not also create a persistent managed-store copy unless the user asks.