> ## 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. # Delete everything this home holds for one share > The INWARD half of revoking, served by the organisation's home and called by a developer's, exactly as the entries operation beside it is — the organisation's home is a narya host, so a revocation is one more operation on this contract rather than a second protocol. IT DELETES AND THEN ANSWERS. The copied entries are gone from this home's store when this returns, which is what lets the developer's home answer its own caller truthfully rather than reporting a queued intention. THE RECORD SURVIVES AS A TOMBSTONE, carrying the disclosure history and the revocation, so any entry offered for this share afterwards is refused 410 NRY-0031 — terminally, however long afterwards. A SHARE THIS HOME HAS NEVER SEEN IS STILL TOMBSTONED. A home learns a share exists from its first delivery, so a person who publishes and immediately revokes can have that delivery in flight while this is being served; writing the tombstone anyway is what refuses it, rather than letting a deletion turn back into a live share. Idempotent: the second call changes nothing and answers the same way, and the instant recorded stays that of the first revocation. ## OpenAPI ````yaml /pt/openapi/v3-current/narya.yaml delete /v1/shares/{shareId} 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/shares/{shareId}: parameters: - $ref: '#/components/parameters/ShareIdParam' delete: tags: - sharing summary: Delete everything this home holds for one share description: >- The INWARD half of revoking, served by the organisation's home and called by a developer's, exactly as the entries operation beside it is — the organisation's home is a narya host, so a revocation is one more operation on this contract rather than a second protocol. IT DELETES AND THEN ANSWERS. The copied entries are gone from this home's store when this returns, which is what lets the developer's home answer its own caller truthfully rather than reporting a queued intention. THE RECORD SURVIVES AS A TOMBSTONE, carrying the disclosure history and the revocation, so any entry offered for this share afterwards is refused 410 NRY-0031 — terminally, however long afterwards. A SHARE THIS HOME HAS NEVER SEEN IS STILL TOMBSTONED. A home learns a share exists from its first delivery, so a person who publishes and immediately revokes can have that delivery in flight while this is being served; writing the tombstone anyway is what refuses it, rather than letting a deletion turn back into a live share. Idempotent: the second call changes nothing and answers the same way, and the instant recorded stays that of the first revocation. operationId: revokeShare responses: '204': description: >- Nothing of this share's conversation is held here any more, and the tombstone that refuses further entries is in place. '403': $ref: '#/components/responses/Forbidden' '500': $ref: '#/components/responses/InternalServerError' components: parameters: ShareIdParam: name: shareId in: path required: true description: >- The share's id, as `SessionShare.shareId` reports it: 26 characters of RFC 4648 base32 drawn from a cryptographic source, carrying no encoding of anything. It is NOT a uuid and is deliberately unrelated to the session id it was published from — a share id travels, so an id derived from a session would make every leaked link a statement about the machine it came from. schema: type: string minLength: 26 maxLength: 26 pattern: ^[A-Z2-7]{26}$ responses: Forbidden: description: >- The caller is authenticated and is not allowed this operation (NRY-0028 or NRY-0030). 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' schemas: 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. 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. ````