NKS Writing

You are about to write a node into the graph. Every node you write will be navigated by future agents, linked to other nodes, traced through estafetas. A wrong type, a lazy name, a mechanical mode — each one degrades the graph for everyone downstream.

Five decisions, in order. Do not skip ahead.

Before anything: realm and cross-realm

Every NKS tool call requires realm=<token>. Confirm which realm you're writing into before the first call.

Cross-realm arrows do not work. nks_arrow(action="link", source="739", target="29") resolves both seq numbers inside the current realm. If #29 in your realm is not the node you mean — you just created a wrong arrow. For cross-realm references, use text in the sense ("see #29") — never arrows.

Reader-and-use novelty gate

Before every create or semantic update, name:

1. the later role/session — or the named reader/query class — expected to retrieve this state;
2. the concrete decision, answer, verification, or handoff that retrieval can change;
3. what is new relative to the accepted requirement, repository, relay, and existing graph.