This runs the real engine in your browser against an in-memory relay, so nothing is published and nothing is fetched. Change the evidence on the right and watch every surface re-decide.
Wrapped in a real <bitgate-veil>, using the marketplace preset.
One snapshot, evaluated four ways.
| Surface | Visibility | Transaction | Rank |
|---|
Everything here is signed state the engine reduces.
Capability checks are enforced in the command layer, not the UI.
In production the provider takes relay URLs. Here it is handed an in-memory runtime so the page works offline and publishes nothing.
<bitgate-provider relays="wss://relay.example" root="<root>" policy="commerce">
<bitgate-veil profile="browse" target-address="30078:<seller>:sku-001">
…your listing markup…
</bitgate-veil>
</bitgate-provider>