> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # 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. ## OpenAPI ````yaml /es/openapi/v3-current/narya.yaml post /v1/refinements openapi: 3.1.0 info: title: Narya Host API version: 1.0.0 description: >- The contract between the Narya host and every client. One long-lived host serves this API over a Unix socket in your Narya home. The terminal client and the one-shot command that Lerian ships drive this API, and a client you write drives the same one. Requests authenticate with a bearer token issued by the identity provider the host is configured with. An operation that declares another security scheme also accepts that credential. A request without a valid credential gets 401 with NRY-0011. A caller whose role lacks the permission an operation needs gets 403 with NRY-0028. Submitting a message returns 202 with a turn id. Everything the turn produces streams over GET /v1/events as server-sent events with a typed envelope, and a stream resumes from a Last-Event-ID header. One error envelope: code, title and message. Codes are NRY- followed by four digits. Cursors are opaque. servers: [] security: - bearerAuth: [] tags: - name: host description: The host process itself — version, uptime, mode, store. - name: sessions description: Durable conversation containers. Archive, never destroy. - name: messages description: Submitting work into a session and interrupting it. - name: events description: The server-sent event stream every client consumes. - name: lanes description: Parallel tracks inside a session — main, subagent, side. - name: agents description: Named recipes — instructions, tools, model, policy. Read-only in v1. - name: ladder description: >- What a person can type: the skills and command files in force for one repository, and expanding one into text. Five origins merged, nearest winning a name, the repository's own rungs gated on trust. - name: permissions description: Pending permission asks, decisions, and the decision audit. - name: intercom description: Sessions on one machine finding and messaging each other. - name: packages description: The one thing a user installs — resources, Go code, or both. - name: extensions description: >- Host-side extensions and the operations each exposes over the wire. This is the generic lane a host extension uses to serve its own client half (a TUI component, a web panel) or any API-only consumer, without adding routes to this contract. - name: workflows description: Deterministic multi-agent orchestration runs. - name: providers description: Model suppliers, their auth state, and the model catalogue. - name: monitors description: >- Long-running watchers a session keeps beside its conversation — a test runner in watch mode, a build, a log being followed. Started by the model or by the person, always listed, always killable. - name: records description: The queryable local record of everything that happened. - name: environments description: >- Where a session's code lives and its commands run — this machine, or a container narya operates. A session that names none runs here. - name: schedules description: >- Work the host's own clock starts with nobody present — a repository, a prompt, a rule and what one fire may spend. Cancel, never destroy. - name: sharing description: >- Publishing a session from a developer's own home to the organisation's, and what is held back before a byte leaves the machine. - name: refinements description: >- What this owner has taught narya and allowed it to keep — distilled facts, and the skills, agents and commands the model wrote for itself. Propose, read, consent, roll back. Nothing here fires until a person answers. - name: platform description: >- Calls Lerian's control plane made to a home it hosts, as this home recorded them. paths: /v1/refinements: post: tags: - refinements summary: Teach narya something, and ask a person to allow it description: >- 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. operationId: proposeRefinement requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/RefinementProposal' responses: '202': description: >- Parked, waiting on a person. The round id is what an answer is posted against; nothing is in the ledger yet. content: application/json: schema: $ref: '#/components/schemas/RefinementRound' '400': $ref: '#/components/responses/BadRequest' '413': $ref: '#/components/responses/RequestBodyTooLarge' '422': $ref: '#/components/responses/UnprocessableEntity' '500': $ref: '#/components/responses/InternalServerError' components: schemas: RefinementProposal: type: object description: >- One refinement a client is asking narya to learn. It becomes a pending item and nothing more until a person allows it. required: - kind - scope - title - citations properties: kind: $ref: '#/components/schemas/RefinementKind' scope: $ref: '#/components/schemas/RefinementScope' repository: type: string description: >- The checkout a repository-scoped proposal belongs to. Required at that scope and meaningless at the owner's global one. maxLength: 4096 name: type: string description: >- The 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. maxLength: 128 title: type: string minLength: 1 maxLength: 200 body: type: string description: >- The fact's text, or the definition's prompt. A proposal with neither a body nor a script teaches nothing and is refused. script: type: string description: >- 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. citations: type: array minItems: 1 description: >- The turns this stands on. At least one is required — an edit citing no turn never becomes a row, whoever proposed it. items: $ref: '#/components/schemas/RefinementCitation' examples: - kind: memory scope: repository repository: /Users/dana/repos/midaz title: Migrations and the schema document are one change body: A new migration without its schema block fails two tests. citations: - sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d entryId: 8a1d3f5b-7c9e-4a2b-8d6f-0c2e4a6b8d0f RefinementRound: type: object description: >- 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. required: - roundId - itemCount properties: roundId: type: string format: uuid sessionId: type: string format: uuid description: The conversation the round was learned from. repository: type: string description: >- 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. itemCount: type: integer format: int32 minimum: 1 examples: - roundId: 2f7c1b93-4a5e-4d6f-8b0c-1e3a5c7d9f2b repository: /Users/dana/repos/midaz itemCount: 1 RefinementKind: type: string enum: - memory - skill - agent - command x-enum-varnames: - RefinementKindMemory - RefinementKindSkill - RefinementKindAgent - RefinementKindCommand description: >- What a refinement IS. Four values and no more — one vocabulary is what makes "everything this repository taught narya" one question. RefinementScope: type: string enum: - repository - global x-enum-varnames: - RefinementScopeRepository - RefinementScopeGlobal description: >- 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. RefinementCitation: type: object description: >- One pointer into the transcript that justifies a refinement. The admitted user entry's id IS the turn id, so citing the turns needs no second identifier. THE POINTER MAY DANGLE, and that is the design: nothing cascades from a purged session to a fact learned in it, because a person deleting one noisy conversation must not silently lose weeks of learning. A fact whose evidence is gone becomes `unverifiable` and keeps firing. required: - sessionId - entryId properties: sessionId: type: string format: uuid entryId: type: string format: uuid note: type: string description: What the review said about this turn. maxLength: 2000 examples: - sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d entryId: 8a1d3f5b-7c9e-4a2b-8d6f-0c2e4a6b8d0f note: the third attempt at the same import cycle Error: type: object description: >- The single error envelope every operation returns. Codes are NRY- followed by four digits and are catalogued in the top-level x-error-catalog extension. required: - code - title - message properties: code: type: string pattern: ^NRY-[0-9]{4}$ description: Machine-readable error code from the NRY catalogue. title: type: string maxLength: 256 description: Short human-readable summary of the error class. message: type: string maxLength: 4096 description: Specific, actionable description of what went wrong. fields: type: object description: Per-field validation problems. additionalProperties: type: string examples: - code: NRY-0002 title: Session not found message: >- No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host. responses: BadRequest: description: Malformed request — invalid parameter, cursor, or JSON body. content: application/json: schema: $ref: '#/components/schemas/Error' RequestBodyTooLarge: description: >- The request body weighs more than this operation accepts (NRY-0024). The host holds one ceiling per operation and refuses at the door, in front of every handler: a body whose declared Content-Length is past the ceiling is refused before a byte of it is read, and a body that declares no length is read only as far as the ceiling and refused there. Nothing was read past that point and nothing was written. content: application/json: schema: $ref: '#/components/schemas/Error' UnprocessableEntity: description: The request was well-formed but failed validation. content: application/json: schema: $ref: '#/components/schemas/Error' InternalServerError: description: The host failed — including a store that refuses writes (NRY-0012). content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- 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. ````