> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rotascale.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ledger Remedies

> Which control would have prevented this, and what would it have cost?

A remedy that prevents the incident is easy. A remedy whose cost elsewhere
you can state is usable. Each candidate is replayed across the same grant's
history so the second number is real.

**Who may call it:** any role. A workspace API key is refused here: this is an act that belongs to a named person.



## OpenAPI

````yaml /api/openapi.json get /v1/ledger/{ledger_id}/remedies
openapi: 3.1.0
info:
  title: RotaGrant API
  version: 0.1.0
  description: >-
    The HTTP API of a RotaGrant deployment, made from the product's own route
    definitions at the commit named in `x-rotascale-source`. Nothing here is
    written by hand.


    There is no shared endpoint. RotaGrant runs in your environment, and your
    deployment serves its own copy of this description at `/api/docs`. That copy
    is the authority on what your version has and which features are switched
    on; this one is the reference for one commit of the main line. The version
    is 0.1.0: routes and shapes can still change.


    Every route says who may call it. Most need a bearer token from the identity
    provider your deployment uses, held by a person with the role named. The
    routes an SDK calls also accept a workspace API key. A few are open, and say
    why.
servers:
  - url: https://{deployment}
    description: Your own deployment. There is no shared endpoint.
    variables:
      deployment:
        default: rotagrant.internal.example
        description: The host your deployment answers on.
security: []
paths:
  /v1/ledger/{ledger_id}/remedies:
    get:
      tags:
        - Authority
      summary: Ledger Remedies
      description: >-
        Which control would have prevented this, and what would it have cost?


        A remedy that prevents the incident is easy. A remedy whose cost
        elsewhere

        you can state is usable. Each candidate is replayed across the same
        grant's

        history so the second number is real.


        **Who may call it:** any role. A workspace API key is refused here: this
        is an act that belongs to a named person.
      operationId: ledger_remedies_v1_ledger__ledger_id__remedies_get
      parameters:
        - name: ledger_id
          in: path
          required: true
          schema:
            type: string
            title: Ledger Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RemediesOut'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - bearerToken: []
components:
  schemas:
    RemediesOut:
      properties:
        ledger_id:
          type: string
          title: Ledger Id
        replayable:
          type: boolean
          title: Replayable
        why:
          anyOf:
            - type: string
            - type: 'null'
          title: Why
        recorded_outcome:
          type: string
          title: Recorded Outcome
        candidates:
          items:
            $ref: '#/components/schemas/RemedyCandidate'
          type: array
          title: Candidates
        reading:
          type: string
          title: Reading
      type: object
      required:
        - ledger_id
        - replayable
        - recorded_outcome
        - candidates
        - reading
      title: RemediesOut
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    RemedyCandidate:
      properties:
        label:
          type: string
          title: Label
        proposal:
          additionalProperties: true
          type: object
          title: Proposal
        would_have_prevented:
          type: boolean
          title: Would Have Prevented
        outcome:
          type: string
          title: Outcome
        reason:
          anyOf:
            - type: string
            - type: 'null'
          title: Reason
        would_also_refuse_elsewhere:
          type: integer
          title: Would Also Refuse Elsewhere
        out_of_decisions:
          type: integer
          title: Out Of Decisions
      type: object
      required:
        - label
        - proposal
        - would_have_prevented
        - outcome
        - would_also_refuse_elsewhere
        - out_of_decisions
      title: RemedyCandidate
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    bearerToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        A token from the identity provider your deployment federates with. It
        identifies a person; their roles in the workspace decide what they may
        do.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.