The Risk Engine
Off-chain scoring that publishes signed attestations the contract reads — and that the contract clamps before it acts on them.
What it scores
The Risk Engine watches the tokens Sluice runs pools for and scores how they are behaving: whether volume is real or wash, whether liquidity is deepening or draining, how holders are distributed, and how all of that is trending.
Its actual job is spotting decay rather than catching outright fraud. A token that qualifies for a pool has already cleared the eligibility bar; what matters afterwards is whether it is still worth holding liquidity against next week. That is a slower and less dramatic question, and it is the one that costs liquidity providers money.
Signed attestations
Scores are published as signed attestations. The contract verifies the signature, checks the value is inside the bounds compiled into it, and clamps anything outside them.
Attestations carry monotonic nonces and bounded per-epoch movement, so a value cannot be replayed and cannot jump. The most a compromised signer can do is push parameters toward one end of a band that was fixed at deploy — it can make the venue behave badly within limits, and it cannot drain anything.
It sits in one service, under its own user, on its own process, and shares nothing with the agent wallets or the API. Nothing that serves a page can reach it.
What happens when the scores stop arriving
Attestations expire. When the contract has nothing current to read, it does not carry on with the last value it saw and it does not fall back to a permissive default.
It fails closed: fees widen toward the defensive end of the band and new liquidity is refused until fresh attestations arrive. Withdrawals are never affected — no staleness condition, and no condition of any kind, blocks an exit.
Where the intelligence stops
The Risk Engine proposes numbers. It never moves funds, never holds a key that could, and never produces a value the contract accepts without checking.
Everything the venue actually does — pricing a swap, compounding, minting shares, paying out a redemption — is contract code with the bounds written in. That separation is the design, and it is what makes an off-chain model an input rather than a dependency.