Teach narya something, and ask a person to allow it
Proposes ONE refinement. It creates a pending item — a one-item round on the consent surface, provenance api and the calling actor beside it — and it activates nothing at all. The prompt this host assembles is byte-identical before and after this call, and that rule is pinned by a test rather than stated here.
SEEDING IS NEVER ACTIVATING, and this operation is the one that must never become a back door: what a client proposes passes exactly the human consent anything the loop proposes passes. A person answers it in a client through POST /v1/refinements/rounds/{roundId}/answer, and the round the answer names is the one this call returns.
At least one citation is required. An edit citing no turn never becomes a row — evidence is a structural control and not a request for good behaviour.
Autorizaciones
Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation.
Cuerpo
One refinement a client is asking narya to learn. It becomes a pending item and nothing more until a person allows it.
What a refinement IS. Four values and no more — one vocabulary is what makes "everything this repository taught narya" one question.
memory, skill, agent, command How far a refinement reaches. repository is keyed on the canonical checkout path, the same key a trust answer uses; global is the owner's.
There is no session here and the absence is a decision: a session-scoped fact lives exactly as long as the conversation that gave it, so it is never a stored row at all.
repository, global 1 - 200The turns this stands on. At least one is required — an edit citing no turn never becomes a row, whoever proposed it.
1The checkout a repository-scoped proposal belongs to. Required at that scope and meaningless at the owner's global one.
4096The ladder identity the three definition kinds are resolved by. Required for them, refused on a memory, and it carries no space, slash, backslash or colon.
128The fact's text, or the definition's prompt. A proposal with neither a body nor a script teaches nothing and is refused.
A program to author, IN FULL. Only a skill runs one: an agent recipe is a system prompt and a command expands into one, so a script on either would be inert.
Respuesta
Parked, waiting on a person. The round id is what an answer is posted against; nothing is in the ledger yet.
A round of proposed refinements standing on the consent surface, waiting on a person. It is what proposeRefinement answers with, and the id an answer is posted against.
x >= 1The conversation the round was learned from.
The canonical checkout path the round is answered against, absent at the owner's global scope — the ledger's own repository column verbatim. It is what keeps a round a complete question after the session that proposed it has been purged.

