# Run the local demonstration — Runtime Bound Canonical page: This is the Markdown form of that page, generated from the same reviewed content. If the two ever differ, the HTML page governs. Published by the Runtime Bound owner; no independent review, certification or regulatory approval is claimed. It documents a local reference demonstration: this website runs no controls and accepts no proposals, grants or credentials. How to run the Runtime Bound local demonstration on your own Linux host with synthetic keys and a simulated destination. --- Local demonstration ## Run the local demonstration. The demonstration is the installed product with synthetic keys and a simulated destination. It runs only on your host. This public website cannot run it and never receives an order. > **Before you start.** The reference topology runs on one Linux host, as the operator (root), using separate operating-system accounts for each role. Everything it uses is synthetic. Running it does not activate an institution. > **Package availability.** The commands below belong to the Runtime Bound `bh01` 2.1.0 source package for Linux. Its hash-locked installation targets Python 3.12 (CPython 3.12 wheels, x86-64); the package declares Python 3.12 or later, but the lock file covers only 3.12. The commands match that package’s own command-line definitions and lock file at its 2.1.0 checkpoint. The package is not publicly distributed: this website offers no download, links to no public repository and publishes no access route. Nothing on this page can be run without it. ### 1. Install From the `bh01` 2.1.0 source package, with its locked environment: ``` # locked, hash-checked dependencies, then the package pip install --no-deps --only-binary=:all: --require-hashes -r pin/requirements/ci-linux-cp312.lock pip install --no-deps ./pin ``` ### 2. Start the topology ``` python -m bh01 topology install --root ROOT # fresh keys, accounts, policy python -m bh01 topology start --root ROOT # witness, sources, destination, broker python -m bh01 topology verify --root ROOT # exit 0 only if the boundary holds ``` `verify` checks each service’s identity and file permissions and runs the agent’s bypass attempts. Do not continue unless it reports that the boundary holds. ### 3. Open the operator console ``` python -m bh01 console --root ROOT ``` The command prints a local address that carries a per-launch access token in its fragment. The console server keeps that token in memory for as long as it runs and checks every request against it; the browser keeps it in session storage for that tab and removes it from the address. The console listens on the local machine only and is not reachable from the public website. ### 4. What to try - **Propose an order within the limit.** Watch it checked, approved, forwarded and accepted by the simulator. Accepted is not executed or settled. - **Propose one over the limit.** It is refused before forwarding, with the reason and exact arithmetic. - **Halt, then resume.** New approvals and forwarding stop at once. - **Lose an acknowledgment** from the simulation controls. The outcome stays unknown, capacity stays held, and “check sent orders” reconciles it without sending twice. - **Restart after a crash** and use “recover after a restart” to see state rebuilt from the witness. > **Current release status.** Local reference demonstrator with simulated interception. In simulation it implements approvals bound to the exact action, durable capacity reservations, one-time use of each approval, witness-anchored recovery, exclusive sending to a simulated destination and linked evidence. Institution-specific trust, destination integration, operations and legal acceptance remain with the institution, and institutional effectiveness is not claimed. [How it is built](https://bounddesk.com/architecture).