Read the explanation
The local check divides proposed position by capital and multiplies by one hundred. Four hundred over ten thousand gives four percent. Six hundred gives six percent. At forty pixels per exposure point the bars span one hundred sixty and two hundred forty. Against a five-percent positive cap the first receives Within limit and the second Pause. These are page labels, not order execution controls. This source never connects a broker, obtains market prices, dispatches an order, or guarantees a risk bound. The explanation is arithmetic from the local source, not investment guidance. The implementation explicitly assigns exposure zero when capital is falsy. With capital zero, a nonzero proposed position and positive five-percent cap can therefore receive Within limit. That is a source edge case, not a meaningful capital safety conclusion. A position of five hundred over ten thousand gives five percent exactly and passes because the comparison includes equality. At forty pixels per computed exposure the bars span zero and two hundred. Browser numeric minimum attributes do not replace domain validation in the check. The stop threshold and selected permission appear in status text, but neither enters the acceptance expression. Keep capital ten thousand, position four hundred, and cap five. Moving the displayed stop threshold from ten to ninety percent leaves exposure at four percent and the same result. The equal one hundred sixty pixel bars make that absence of dependency visible. Changing permission from read-only research to submit orders also does not change the arithmetic. Download writes a Markdown local plan including those descriptive settings. The reset handler sets an in-memory default, then immediately reads current controls back through save before load, so edited controls may remain. Preserve that original behavior while adding an explainer; do not interpret this local plan as enforcing broker permissions or stop orders.