> ## 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. # Read the exact system prompt this session's next turn will send > The assembled system prompt, verbatim, plus the ledger's accounting beside it: which learned facts fired into it, and which the budget for this model's context window could not fit. It exists so a person debugging a strange behaviour can read what the model is actually being told instead of reasoning about it. HOW THE PROMPT IS COMPOSED IS NOT ON THIS SURFACE, and the omission is deliberate rather than an oversight: no combinator order, no wrapper template, no budget formula and no selection rule. A client renders what it is given and never recomputes it. ## OpenAPI ````yaml /es/openapi/v3-current/narya.yaml get /v1/sessions/{sessionId}/prompt 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/sessions/{sessionId}/prompt: parameters: - $ref: '#/components/parameters/SessionIdParam' get: tags: - refinements summary: Read the exact system prompt this session's next turn will send description: >- The assembled system prompt, verbatim, plus the ledger's accounting beside it: which learned facts fired into it, and which the budget for this model's context window could not fit. It exists so a person debugging a strange behaviour can read what the model is actually being told instead of reasoning about it. HOW THE PROMPT IS COMPOSED IS NOT ON THIS SURFACE, and the omission is deliberate rather than an oversight: no combinator order, no wrapper template, no budget formula and no selection rule. A client renders what it is given and never recomputes it. operationId: getAssembledPrompt responses: '200': description: The prompt as assembled, with the ledger's accounting. content: application/json: schema: $ref: '#/components/schemas/AssembledPrompt' '400': $ref: '#/components/responses/BadRequest' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' components: parameters: SessionIdParam: name: sessionId in: path required: true description: The session's id. schema: type: string format: uuid schemas: AssembledPrompt: type: object description: >- The exact system prompt this session's next turn will send, and the ledger's accounting beside it. THE ACCOUNTING IS DATA AND NOT A METHOD. Which facts fired and which were dropped are facts about this prompt; the order they were composed in, the wrapper they were drawn with, the formula that sized the budget and the rule that picked them are the engine's and are deliberately not here. A fact the budget dropped is STILL STORED and still listed — the ledger is not evicted, the render is — so it comes back the moment there is room. required: - system - fired - dropped - droppedCount properties: system: type: string description: The prompt, verbatim. fired: type: array description: >- The refinements that reached this prompt, in the order they were drawn. items: type: string format: uuid dropped: type: array items: $ref: '#/components/schemas/DroppedRefinement' droppedCount: type: integer format: int32 minimum: 0 description: >- How many were dropped. It is on the wire beside the list for the reason the model is told the same number: a person reading a short list wants to know whether it is short because little was learned or because little fits. examples: - system: |- You are narya… … fired: - 7d1e3a5c-9b2f-4e6a-8c0d-2f4a6c8e0b2d dropped: [] droppedCount: 0 DroppedRefinement: type: object description: One learned fact the budget could not fit into this prompt. required: - id - reason properties: id: type: string format: uuid reason: type: string description: Why it did not fire. examples: - id: 7d1e3a5c-9b2f-4e6a-8c0d-2f4a6c8e0b2d reason: the budget for this model's context window was already spent 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' NotFound: description: The addressed resource does not exist on this host. 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. ````