Core Loop

Open Plan (and the CharterPlan inspector) edits the core loop as a 4-step cycle, not four unlabeled dumps. Completeness still only requires loop verbs.

No extra menu. Use ArTchie / Charter / Open Plan.

Cycle

Step	Field	Role
1	Verbs	What the player repeatedly does
2	State change	What is different after those verbs
3	Feedback	What sells that the action worked
4	Hook (next loop)	Why they start the cycle again

MiniLabel: player verbs change state, feedback sells it, hook pulls the next cycle.

Empty fields stay empty. Charter does not invent sample gameplay. One-Page GDD still seeds short [prompts] you replace.

Mermaid text

Under the form, Charter emits a mechanical flowchart (text only — no renderer, no graph library, no GraphView):

flowchart LR
    verbs["…"]
    stateChange["…"]
    feedback["…"]
    hook["…"]
    verbs --> stateChange --> feedback --> hook --> verbs

Empty fields become placeholder labels ((verbs), (state change), (feedback), (hook)) so the graph still parses. User text is quoted; " becomes '; newlines collapse to spaces; labels truncate at 80 characters.

• Copy — mermaid text to the clipboard (EditorGUIUtility.systemCopyBuffer). Works even if the plan is not on disk yet.
• Save — writes {title-or-filename}-loop.mmd in the same folder as the plan asset (title if named, otherwise the asset filename). Overwrites that file. If there is no asset path yet, Save reports why it cannot; Copy still works.

This is not Export Markdown (full plan .md includes this mermaid in a fence — see Documentation/Export.md). Feature MoSCoW CSV is in the Features section. The .mmd save does not open Folio.

See Documentation/OpenPlan.md and Documentation/PlanAsset.md.