# Renigma local application 0.2.0

The application opens Renigma's workbench in your browser using a server bound
to `127.0.0.1`. It provides guided synthetic examples, visible application and
engine status, reviewed memory scenarios, explicit imports and exports, and
retained discrepancies. It uses a finite authored grammar, not unrestricted
language understanding. Imported words never authorize external actions.

Application release **0.2.0** identifies this interface and launcher. The Python
distribution metadata remains **0.1.0** to preserve the existing dependency lock
and historical research identities. These version numbers describe different
release surfaces. Research receipts continue to identify their original source.

## Open the application

From the public repository or an authorized, verified local application ZIP, open
PowerShell in the folder containing `Launch-Renigma.cmd`.

If the isolated environment has already been prepared, double-click
`Launch-Renigma.cmd`, or run:

```powershell
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\start-workbench.ps1
```

The Windows launcher uses `-ExecutionPolicy Bypass` for that spawned PowerShell
process so the trusted local launch script can run under Windows' default
restricted policy. It does not change a user-wide or machine-wide policy.

The launcher explicitly selects the `src` directory beside its own scripts.
An existing environment's editable installation therefore does not redirect the
application to a different checkout. The application starts with the labelled
dictionary reference unless a learned memory artifact is explicitly supplied.
Check the visible version and engine status before reviewing a scenario.

For a first setup, install the locked workbench dependencies:

```powershell
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\bootstrap.ps1
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\start-workbench.ps1 -CheckOnly
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\start-workbench.ps1
```

Bootstrap requires Python 3.12, `uv` and network access to obtain the locked
dependencies. The ZIP contains source and launchers, not Python, `uv`, dependency
binaries or a learned model. Setup reuses the configured isolated environment;
it does not install a global Python package or a background service. The default
environment and cache live under `G:\RenigmaLLM_Artifacts`. Use the same explicit
`-ArtifactRoot` for bootstrap and startup when an alternative storage directory
has been configured. A missing drive or environment produces an error instead
of silently using C:.

Readiness checks inspect dependencies, engine, artifact storage and local port
availability without leaving a server running. To start without opening another
browser tab, use `-NoBrowser`. The default address is `http://127.0.0.1:8765`.
If the port is occupied, choose another port explicitly, for example:

```powershell
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\start-workbench.ps1 -Port 8766
```

The launcher does not kill or silently reuse an existing server whose source or
engine could differ. Ctrl+C in its terminal stops this server. No scheduled task,
cloud model integration, remote hosting or background saving is enabled.

## Complete a synthetic scenario

Use the starting guide and the color example in **Scenarios**. The baseline
writes green, overwrites it with blue, then recalls blue. Its alternative omits
the overwrite and recalls green. Both branches begin with empty memory.

Review the proposed interpretations, ordered operations and any unsupported
wording before adoption. A synthetic report of green against the baseline's
blue prediction produces a discrepancy. It does not rewrite the prediction or
prove what caused the difference. No report and an explicitly missing binding
remain distinct observations.

Use explicit JSON export to preserve an accepted record before closing or
resetting. Original wording, corrections, observations and revision history
remain separate. Import validation checks the configured engine and canonical
replay; it does not establish that a reported event occurred.

## Verify a private application package

Keep the ZIP and its adjacent `.zip.sha256` together. From a trusted copy of the
repository or already verified package, run:

```powershell
& 'G:\RenigmaLLM_Artifacts\environment\Scripts\python.exe' -B .\scripts\package_application.py --verify 'G:\RenigmaLLM_Artifacts\releases\application-0.2.0\<release>\renigma-application-0.2.0.zip'
```

The verifier checks the detached ZIP checksum, path and size boundaries, exact
file inventory and individual file hashes in `application-manifest.json`. It
rejects unexpected files, duplicate paths, links and traversal. These checks
establish byte consistency, not the authenticity of an unknown sender. Verifying
or extracting a package never executes its contents.

The same command accepts `--extract-to` with a new directory inside the configured
artifact root. Existing destinations are rejected. You may instead inspect and
extract a trusted ZIP with Windows after verification; its top-level folder is
`renigma-application-0.2.0`.

The private package contains first-party application runtime source, locked
dependency metadata, launch/setup tools, this guide, README and license notices.
It excludes checkpoints, experiment runs, evidence archives, private records,
environments, Git history and the public website. README links to other repository
documentation require the full repository; this guide is the package's local
operating reference. Dependency and original-code licensing remain separate.

Release owners create a new package with the same script and no `--verify`
option. Output is confined to a fresh directory under the configured artifact
root's `releases/application-0.2.0/`; prior packages are never overwritten.
Packaging checks the version/status/guide contract and records hashes. Runtime
readiness, browser behavior and accepted workflows require their own execution
checks; packaging alone does not claim that they passed.