Wymcp tool references — the registry of pointers at where knowledge lives, and the cache of what their targets say.

A thin boundary over YmerNode.References: bare-verb actions over a single entity, with this module wiring the framework's callbacks and one clause of its own (below). What the registry and the cache are, and the rule between them, live in the context's own moduledoc (§ The membrane).

Open-world, because read on a miss, refresh and watch run the reference's script, and a script reaches the network with the node's own permissions. Destructive on account of remove alone: it hard-deletes a reference, and until registry sync lands the node database holds the only copy of it. Dropping a cache entry or a watch loses nothing a refetch does not restore.

The image clause

wymcp answers every action as one JSON text block, so an image read serves would reach a client as base64 inside text. The last run/2 clause here takes the read action alone: it runs the framework's own dispatch — every argument gate, the required and unknown-param checks and the defaults — and, when the answer carries an image, answers it as an image block beside the rest of the answer in JSON. Every other answer passes through as it came.