NKS Intake

External word — an issue, a README, a chunk of source, a conversation, an RFC — is шабда: testimony with existence outside the graph. It is not yet yours. This skill brings it in as a claim, never as a fact — mapped to the right node type, marked by provenance, deduped, anchored, and then verified by direct observation (пратьякша).

The symptom this skill prevents: external word dumped en masse as facts floods the realm with authoritative-looking garbage and false tensions, breaking «the graph is a tension with reality» and «systems grow, not get built».

Source-independence is the whole point. The source is an adapter; the intake discipline below is one. product-roadmap composes this layer with a GitHub adapter; a future verstakify seeding or a docs-intake composes it with another. Do not bake a source into the discipline.

The source adapter — its contract

Fetching external word is the adapter's job, not this skill's. Whatever the source (GitHub gh, file read, a conversation transcript), the adapter must hand the core, per item:

• content — the claim itself (title + trimmed body, or the prose chunk);
• form — what kind of utterance it is (a report of breakage, a wish, an open question, an opinion, a stated fact, a decision), so the core can map it;
• provenance — a stable back-reference to the origin (issue URL, file path + symbol, "conversation 2026-…"), so each node can arose_from it;
• authority — who said it and how directly it can be checked (a drive-by issue vs. the owner's decision vs. code you can read now). This sets the epistemic mode (step 3).

If the adapter can't supply provenance for an item, that item is not intake-able — it would land unanchored and invisible.