> ## 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. # List the rounds waiting on a person > The rounds standing on the consent surface, newest first. It is the recovery road for a client that was not attached when `refinement-proposed` went out — a round proposed by last night's scheduled fire is answered the next morning, and an announcement nobody heard must not be the only way to find it. A round is NEVER expired by the boot-recovery pass, unlike a permission or a question: nothing is blocked behind it, so a host restarting leaves it exactly where it was. ## OpenAPI ````yaml /pt/openapi/v3-current/narya.yaml get /v1/refinements/rounds 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/rounds: get: tags: - refinements summary: List the rounds waiting on a person description: >- The rounds standing on the consent surface, newest first. It is the recovery road for a client that was not attached when `refinement-proposed` went out — a round proposed by last night's scheduled fire is answered the next morning, and an announcement nobody heard must not be the only way to find it. A round is NEVER expired by the boot-recovery pass, unlike a permission or a question: nothing is blocked behind it, so a host restarting leaves it exactly where it was. operationId: listRefinementRounds parameters: - name: status in: query required: false description: >- Which rounds to list. `pending` is the default and the one a client draws an affordance from; `answered` is the audit of rounds already decided. schema: type: string enum: - pending - answered default: pending x-enum-varnames: - RefinementRoundStatusPending - RefinementRoundStatusAnswered - $ref: '#/components/parameters/CursorParam' - $ref: '#/components/parameters/LimitParam' responses: '200': description: One page of rounds. content: application/json: schema: $ref: '#/components/schemas/RefinementRoundPage' '400': $ref: '#/components/responses/BadRequest' '500': $ref: '#/components/responses/InternalServerError' components: parameters: CursorParam: name: cursor in: query required: false description: >- Opaque pagination cursor from a previous page's nextCursor or prevCursor. schema: type: string maxLength: 1024 LimitParam: name: limit in: query required: false description: Maximum items per page. schema: type: integer minimum: 1 maximum: 100 default: 25 schemas: RefinementRoundPage: type: object description: One page of rounds waiting on a person. required: - items - limit properties: items: type: array items: $ref: '#/components/schemas/RefinementRound' limit: type: integer minimum: 1 nextCursor: type: string examples: - items: - roundId: 2f7c1b93-4a5e-4d6f-8b0c-1e3a5c7d9f2b sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d repository: /Users/dana/repos/midaz itemCount: 4 limit: 25 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 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' 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. ````