Legacy Lens Offline Kit
=======================

1) Run the server:
   - Linux/macOS: ./run.sh
   - Windows: run.bat
   Keep this terminal open while using the UI.

2) Preferred: use the sealed kit ZIP returned by your vendor.
   If you receive only a signed license file, place it next to the launcher:
   - LIC_*.signed.json
   (vendor public key is included in this kit)
   (or set FORENSIC_LICENSE_FILE manually)

Hardware binding:
----------------
The base kit is request-only and cannot run without a signed license.
It generates a request file when no license is present.
You can also generate one manually:
  ./legacy-lens fingerprint --request HW_REQUEST.json --customer-id YOUR_ID

The signed license must include:
  - hardware_fingerprint
  - kit_manifest_sha256
  - rules_hash

3) Start the server and open the console:
   http://127.0.0.1:8080

Version Check:
--------------
See VERSION for build metadata (registry version, app.js version, git SHA).

Integrity:
----------
This kit is cryptographically sealed. Modifications invalidate authority.
If kit integrity fails, Legacy Lens will refuse to run.

CLI (evidence + governance):
----------------------------
Place license files next to the binary or set env vars:
  - FORENSIC_LICENSE_FILE

Evidence Mode licenses allow evidence-only analysis and verification.
Decision Authority licenses are required for governance decisions.

License Issuer:
---------------
This customer kit does not include the vendor license issuer or signing workflow.
License issuance is vendor-only and requires the vendor signing key.

Run evidence-only analysis:
  ./legacy-lens analyze /path/to/input --output /path/to/bundle

Run governance decision (authority license + context required):
  ./legacy-lens govern /path/to/input \
    --context-environment production \
    --context-regulatory-scope regulated \
    --context-business-criticality high

Verify an existing bundle:
  ./legacy-lens verify /path/to/bundle
