# Deployment notes for IT

## Installation

Per-user. No administrative rights are required and no system services are
installed. The application writes nothing outside the user's own profile and the
folders the operator chooses.

## Code signing

**As at this release the builds are not signed or notarised.** macOS Gatekeeper
and Windows SmartScreen will warn. This is a known gap and is tracked; a
customer evaluating for production use should ask for a signed build.

## Network policy

The application requires no network access and makes no connections. It can be
run on a host with all outbound traffic blocked, and doing so is a reasonable
way for a customer to verify the claim independently. Every feature works in
that state; the only visible effect is that the website links in the interface
fail to open, since those are handed to the user's browser rather than fetched
by the application. See the Network section of the security overview.

## Filesystem access

The application reads the folders the operator selects and writes only into the
output directories listed in the security overview, plus its own storage under
the user profile. It never modifies an original document in place.

## What to give it

- Read and write access to the engagement folders the operator works on.
- Nothing else. No shared service account, no database, no inbound ports.

## Verifying the claims yourself

- Run it with the network disconnected; everything except nothing continues to work.
- Watch it with a network monitor; there is no traffic to see.
- Inspect `resources/sidecar` and confirm the process opens no sockets (`lsof -i`).
- The generated IPC and sidecar surfaces in the security overview are the
  complete list of operations the interface can trigger.

## Known limitations

- The Windows installer is not code signed. macOS is signed, notarised and
  stapled; the `.rpm` is GPG-signed.
- No independent penetration test.
- No SOC 2 or ISO 27001.
- **English is the only OCR language pack bundled.** The engine itself ships on
  all three platforms. Roman-script documents in other languages are recognised
  acceptably; a different script is not recognised at all, and the failure looks
  like a poor scan rather than a missing pack.
- The bundled Windows `tesseract.exe` carries a third-party signature whose
  issuing certificate has expired. It is the upstream UB Mannheim build and is
  unmodified, but an endpoint agent may treat an unvalidatable signature more
  harshly than an unsigned binary.