NKS Inquiry

A vimarsha is not a sticky note. It is a recorded tension with reality that must eventually be discharged — resolved, released, or crystallized into form. writing poses the question; this skill carries it through its life and works the field as a whole.

The symptom this skill fixes: realms accumulate dangling vimarshas — unanchored, unresolved, invisible to the agents who could discharge them. A field of free questions that never converges to understanding is a realm that thinks but never learns.

1. Anchoring is mandatory

An unanchored vimarsha is an invisible vimarsha — it surfaces in no lens="vimarshas", propagates to no node. Every vimarsha needs two arrows:

• vimarsha_of → the node(s) the question is about. Without it the question floats.
• arose_from → the observation it was seen from (a node, an incident, a prior vimarsha). Without it the question has no origin to trace back to.

A vimarsha carrying an expectation (a posed_to arrow to a karta, anga to a bianhua) needs the anchor doubly: agents discover work by orienting on a holon, and neither anga nor posed_to scopes a vimarsha into anyone's contour — without vimarsha_of into the addressee's territory it is invisible there and will never be done. Minimum anchor — the holon where the expected work lives; better — the precise phenomenon or kriya within it. (The unanchored detector fires post-hoc; don't rely on it — anchor at posing time.) posed_to is the live inbox edge to a karta — so an addressee can poll "my open questions"; forbidden to a pratibimba (an image can't answer), and it never substitutes for vimarsha_of.

The mirror failure is just as real: vimarsha_of without posed_to on a question that expects another doer to act — anchored, visible in the territory, in no one's inbox; a delegation degraded to a note-into-the-void. If you expect someone to act, name them: the 能 who stewards the holon where the work lives (writing Decision 2b — find it via the steward arrow or nks_search(q="", node_type="karta"), never from orient's root-kartas showcase), never a pratibimba.

Anchor where the ADDRESSEE orients, not where you stand. A tool defect noticed while editing skills belongs in the tool's holon; a methodology gap found while shipping code, in the methodology's node. Anchored in your own territory instead, it passes the unanchored check and stays invisible to the one who could answer — a failure that hides from the detector rather than being caught by it.