Skip to main content
POST
Ask to widen what a fact applies to

Authorizations

Authorization
string
header
required

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.

Path Parameters

refinementId
string<uuid>
required

The refinement's id.

Response

The round now standing for a person to answer.

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.

roundId
string<uuid>
required
itemCount
integer<int32>
required
Required range: x >= 1
sessionId
string<uuid>

The conversation the round was learned from.

repository
string

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.