10. Conclusion

The argument of this document is that a trading system can harvest volatility instead of forecasting it. The rest follows from removing the stop-loss and moving risk control to the sizing layer: a survivable decline calls for holding capital sized to absorb it. The Capital Oracle sizes each asset against its own worst recorded decline, the strategy layer trades within that allowance, and the order path and connectivity carry the trades out. No layer predicts direction or times an entry.

Putting it into effect is undemanding. The mathematics lives in the oracle, which derives the drawdown reference, the floor, and the parameter search from the asset's own recorded prices; there is no model to build and no forecast to maintain. What an operator decides is a short list: an order size that stays small relative to the book, and whether the asset oscillates at the interval being traded. Section 8.3 lists the rest. The strategy shipped with the engine is 151 lines and is meant to be read top to bottom.

That design has a specific failure mode, stated plainly. If price stops oscillating at the interval the ladder trades, the ladder accumulates without realizing and no sizing rule repairs it. Section 2 states the premises the approach depends on and what happens when each one fails; section 9 lays out the risks that remain. Those are the terms on which the system should be judged, and they are the reason the source is public: a claim about survivability is worth something only if a stranger can check it. Strategies are files, so the same is true of whatever strategy is running.

The engine is pre-1.0. Jacobs Ladder is the strategy it ships with and the one running publicly at diophantsolutions.com; the same layers will run whatever is written next.