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

# FAQ

> Direct answers, including the ones that aren't flattering.

<AccordionGroup>
  <Accordion title="Does Parmana prevent an AI from executing an unauthorized action?">
    Within a scope that's now the default, yes, see [Content Binding &
    TOCTOU](/concepts/content-binding-toctou) and [The gateway](/concepts/the-gateway). As of
    commit `651497a`, the default local server wires the Execution Gateway unconditionally,
    every `POST /execute` gets independent content-binding re-verification, and the one
    registered connector runs behind [credential isolation](/concepts/credential-isolation),
    so the calling AI never holds that connector's credential. What's still scoped: only one
    connector is registered by default, adding another today is a bootstrap code change, and
    Parmana enforces nothing at the network level, this is a property of a gateway-integrated
    system, not a network guarantee. That's the explicit subject of the [Roadmap](/roadmap)'s
    three "unavoidability" moves.
  </Accordion>

  <Accordion title="Is Parmana's signing key stored securely?">
    Today it's a PEM file on disk, read by `FileKeyProvider`, the only implemented key
    provider. There's a live incident on record: an earlier committed key was publicly
    exposed and is permanently compromised (rotated 2026-07-05). KMS/HSM custody is
    designed but not built, see [Cryptography](/cryptography/overview) and
    [Roadmap](/roadmap).
  </Accordion>

  <Accordion title="Which SDK should I use?">
    Either — both are \[AVAILABLE] and actively maintained. Python's models are generated
    from the same TypeScript domain types the server uses, drift-guarded in CI; the
    TypeScript SDK's models are hand-maintained but spot-checked against the real schemas.
    Both raise a typed exception per HTTP status and are tested against a real running
    server, not just mocks. The TypeScript package is private and not published to a
    registry (`@parmana/sdk` in `typescript/package.json`, install from a local path or git
    reference); Python installs with `pip install -e ./python`. See [Python
    SDK](/sdks/python) and [TypeScript SDK](/sdks/typescript).
  </Accordion>

  <Accordion title="Can I use Go / Java / .NET?">
    Not via an SDK, none exists. Call the [REST API](/api-reference/introduction) directly;
    it's 14 small, documented routes. See [Other Languages](/sdks/other-languages).
  </Accordion>

  <Accordion title="Does Parmana support post-quantum signatures?">
    Yes, ML-DSA-65 (FIPS 204), selectable via `PRIMARY_SIGNATURE_PROVIDER=dilithium3`, real and
    tested. Requires Node ≥ 24. Its signatures are randomized, not deterministic, don't
    build tooling that assumes otherwise. See [Cryptography](/cryptography/overview).
  </Accordion>

  <Accordion title="What does 'replay' actually do?">
    Two different things share the name, and neither is what you might assume. See
    [Replay](/replay/overview), this is worth reading in full before relying on either.
  </Accordion>

  <Accordion title="Is there an 'Execution Permit'?">
    Not anymore, under that name. An early prototype used it; it was deleted the same
    session it was replaced by the current `SignedExecutionAuthorization` + Execution
    Gateway architecture, which is what actually ships. See [Glossary](/glossary).
  </Accordion>

  <Accordion title="Is this API authenticated?">
    Yes. Every route except `/health`, `/ready`, `/openapi.yaml`, and `/documentation`
    requires a bearer key and fails closed with a `401` if it's missing or wrong
    (`createCallerAuthenticator.ts`, commit `5c688b4`). See
    [Authentication](/api-reference/authentication). This is a separate question from
    whether the underlying business action was authorized, see
    [Security](/security/overview) for that boundary.
  </Accordion>
</AccordionGroup>