At full deployment.

A venue listing tokenized equities

A lending market or a perpetual venue that accepts tokenized U.S. equities has a problem every night and every weekend: the token keeps trading while its reference market is closed, and the price feeds it relies on may stop moving. The target: the venue reads a signed record of the off-hours gap, asks the gate whether the evidence supports its current parameters, and applies its own haircut or pauses new positions when the gate defers or abstains.

An agent that moves money

An agent that knows when it does not know is the one you can let run. The target: the agent brings its own model’s prediction and that model’s track record, the gate turns the prediction into a region, and the agent acts through its wallet policy only on commit. The wallet policy says what the agent may touch; the gate says whether the evidence supports acting at all. The two stack.

An oracle that wraps a verifiable record

A price network or an oracle can relay a value it did not compute. The target: an oracle that consumes MONARK Bell’s record checks each line’s signature and chain against the committed keyring, relays the value with the line’s hash, and lets any consumer trace the value back to the signed line and recompute it from the ledger.

A leveraged position that eases down

A leveraged position on a lending venue can be liquidated in parts when its collateral falls. The target: before it clears, the position reads an upper bound on what the protocol’s rule would liquidate, asks the gate whether the evidence supports that bound, and eases its exposure down on commit.

A treasury that holds a stablecoin

A treasury, a DAO or an agent that holds a stablecoin wants to know early when redemptions speed up. The target: the treasury reads the daily redemption-flow record, asks the gate on the stable-run class of its population, and rebalances on commit.

Every application named here has its page on the applications page; every piece, on the pieces page.