# Runtime Bound — Set the limits. Keep control. 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. Runtime Bound: an institution-owned execution boundary for agent-driven actions, in development. Local reference demonstrator with simulated interception. --- Institution-owned execution control ## Set the limits. Keep control. Connect an institution’s authority and limits to the exact action an agent proposes. Runtime Bound is being developed as an institution-owned execution boundary for agent-driven actions: it checks the exact proposal against the institution’s adopted limits, reserves capacity, and intercepts forwarding unless the required authorization is valid. [Explore the local demonstration](https://bounddesk.com/demonstration) [How it is built](https://bounddesk.com/architecture) Local demonstration with simulated interception. No live institutional activation is claimed. > Illustrative simulation > > Latest order > > USD 250,000.00 > > AAPL · Example account · XNYS > > Counted against today’s limit > > (25 percent of the daily limit counted) USD 1,000,000.00 daily limit > > USD 750,000.00 remaining > > 1. **Checked: permitted** Within the authority granted and today’s limit. > 2. **Approved: capacity reserved** A signed approval was issued for this order only. > 3. **Accepted by the destination** Its signed answer was verified. Execution and settlement are not reported. One order as the operator console reports it, with synthetic values. ### Before forwarding Check authority and capacity. ### At the boundary Refuse actions outside the approved limits. ### After the decision Keep a linked, inspectable record. ### Three outcomes, as the console reports them. Illustrations with synthetic values. They explain the behavior; they do not run the admission engine or submit orders. Illustrative simulation #### Accepted by the destination USD 250,000.00 proposed; USD 750,000.00 of capacity remains. The order is checked, approved with capacity reserved, and forwarded. The destination’s signed answer is verified. Accepted is not executed or settled: those are not reported to the runtime. Illustrative simulation #### Refused before forwarding USD 900,000.00 proposed with USD 250,000.00 already counted against a USD 1,000,000.00 daily limit. This order would take the day’s counted notional over the limit. Nothing is approved or forwarded, and the reason and the exact arithmetic are recorded. Illustrative simulation #### Outcome unknown; needs a check with the destination A send may have started, but no verified answer came back. It stays counted in full against the limit until a check with the destination settles it. The same order key is reused, so nothing is sent twice. A missing answer is not permission to send a new order. Illustrations with synthetic values. Institutional integration is required for real use. ### Scope and current status Runtime Bound brings the discipline of pre-trade limits and approval controls to a named runtime. The first demonstration is a trading instruction. The broader direction includes payments, procurement and infrastructure, each needing its own validated action contract and execution adapter. The institution owns its policy, trust configuration and execution boundary. The resulting record separates what was authorized, what was evaluated, what the interceptor did and what the destination acknowledged. [How it is built](https://bounddesk.com/architecture) [Explore the local demonstration](https://bounddesk.com/demonstration) #### 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. #### Relationship to QIS [QIS](https://qisfund.com/) publishes the reference concepts, research, source provenance and crosswalks. Runtime Bound is a separate, institution-local execution boundary; its admission core does not retrieve public QIS services to authorize an action. Upstream references: [MARQUE](https://qistrust.com/marque/), the eight authority questions its model draws on; the [crosswalk](https://qistrust.com/crosswalk/) of MARQUE against 230 control objectives; and the [reference gate (RG-01)](https://qistrust.com/reference-gate/), a nonbindable reference evaluator that never authorizes an action.