Runtime funding and farming
The same organism-pool swaps that produce LP fees also refill the escrow that pays for model execution.
The loop
Trading produces fees. The locker splits them: a runtime share enters escrow E, a bounded creator share is claimable, and a fixed 15% protocol share is routed separately. Escrow then pays c for each tick, and the organism steps.
Metering c
The cost per tick is declared at launch in units of the pool's quote asset per tick. It must be concrete and public so anyone can calculate runway, reproduce deductions, and distinguish execution cost from an operator's claim.
c is fixed after launch. A runtime whose cost cannot be stated in those units does not have a complete funding rule.
Farming the pool
Farming here means holders provide liquidity to the organism's pool and receive the LP share of swap fees on their position through standard AMM mechanics. Deeper liquidity lowers slippage, which tends to raise V, which raises dE/dt.
This is the incentive alignment: the yield farmers earn and the escrow that keeps the model running come from the same swaps.
Farming is not a promised yield, not a guarantee that V stays above V*, and not a claim about token price.
Pause and resume
When escrow reaches zero, the trace freezes at s_t and H_t stays public. Once E is greater than c again, execution resumes from the last checkpoint rather than inventing the missed states.
Direct top-ups are allowed, but nobody is obliged to provide one.