When multiple marks combine on one note, they stack in a fixed order outward from the notehead: fingering, then articulation, then ornament, then slur/tie, with dynamics/tempo text further out still

Fingering sits closest to the notehead; next out is articulation; ornaments sit outside articulation; ties/slurs are drawn outside all of the above since the curve must arc over everything attached to the note; dynamics and tempo/expression text sit outermost.

A note with both fingering '3' and a staccato dot renders the fingering further from the notehead than the staccato dot — this is now known to be IMPOSSIBLE via addModifier call order alone (the category table always wins), so a real occurrence would indicate a VexFlow version change to the category order itself, not a Gradus authoring bug.

Gould, Behind Bars, general discussion of combined markings across the Articulation, Ornaments, and Ties/Slurs chapters; Dorico's engraving-options grouping of note-attached items by vertical priority follows the same order. IMPORTANT MECHANISM CORRECTION from the source-verified draft: this order is NOT a consequence of the order Gradus calls `addModifier` (the earlier draft's claim). It is VexFlow's OWN fixed category order inside `ModifierContext.preFormat` (modifiercontext.ts lines 148-163): `Dot, FretHandFinger, Accidental, Stroke, GraceNoteGroup, NoteSubGroup, StringNumber, Articulation, Ornament, Annotation, ChordSymbol, Bend, Vibrato` — and FretHandFinger, Articulation, Ornament and Annotation all read/increment the SAME shared `state.text_line`/`state.top_text_line` counters IN THAT ORDER regardless of `addModifier` call sequence (confirmed by reading frethandfinger.ts, articulation.ts lines 234-245, ornament.ts lines 106-113, annotation.ts lines 150-168, all touching the identical state fields). Where Gould and Ross differ on fingering-vs-articulation priority for a rare combination, this rulebook follows Gould (fingering closest) since that is also what VexFlow's own hardcoded category table already does.

This rule needs the notated content and the rendered result together — the score says what should happen, the page says whether it did.