Diagrams · Fig. 05

Anatomy of a hold

A hold is a decision with three exits, not an error.

Anatomy of a holdA held call reads: HELD, filesystem write_file. ChangeKind added-required-param, a fixed taxonomy rather than free prose. Pinned: write_file with path and content, which is your baseline. Live: write_file with path, content and a newly required mode parameter, which is what the server sends now. Posture guard, which is why it held; monitor would only notify. Blast radius write, not reversible, stays on this machine. Three exits are offered: re-pin, reject, or tune the posture. All three are reversible.HELDfilesystem · write_fileChangeKindadded-required-parampinnedwrite_file(path, content)livewrite_file(path, content, mode*)postureguardblast radiusWRITE · not reversible · local* newly required→ re-pin→ reject→ tune posture1A fixed taxonomy. One of twelvesurfaced kinds. Never free prose.2Your baseline. What you saw first.3What the server sends now.4Why it held here. Monitor wouldnotify and let it through.5What the call would have done.6Three exits. All reversible.THE GATE SAYS “THIS CHANGED”, NEVER “THIS IS UNSAFE”.
Fig. 05 · A hold is a decision with three exits, not an error.
Read Fig. 05 as text
  |- HELD   filesystem - write_file
     ChangeKind    added-required-param       (1) fixed taxonomy. never free prose.
     pinned        write_file(path, content)  (2) your baseline. what you saw first.
     live          write_file(path, content,  (3) what the server sends now.
                              mode *)
                              * newly required
     posture       guard                      (4) why it held here. monitor would notify.
     blast radius  WRITE - not reversible     (5) what the call would have done.
                   - stays on this machine
     -> re-pin   -> reject   -> tune posture  (6) three exits. all reversible.

  the gate says "this changed", never "this is unsafe".
What the figure says

A held call reads: HELD, filesystem write_file. ChangeKind added-required-param, a fixed taxonomy rather than free prose. Pinned: write_file with path and content, which is your baseline. Live: write_file with path, content and a newly required mode parameter, which is what the server sends now. Posture guard, which is why it held; monitor would only notify. Blast radius write, not reversible, stays on this machine. Three exits are offered: re-pin, reject, or tune the posture. All three are reversible.

Where this is explained
Use this diagram

Licensed CC BY 4.0. Use it anywhere, including commercially. Keep the credit.

Credit line (HTML)

Paste under the figure. That is the whole licence obligation.

<a href="https://mcpindex.ai/diagrams/anatomy-of-a-hold">Anatomy of a hold - mcpindex.ai</a> (CC BY 4.0)
Direct SVG

Standalone image/svg+xml. Vector, editable, no stylesheet needed.

https://mcpindex.ai/diagrams/anatomy-of-a-hold/svg

Last reviewed 2026-07-27

Questions this answers

mcpindex held my call &middot; what does mcp hold mean &middot; mcp gate hold output &middot; mcpindex first hold