The May 2026 Distressed paper-test aggregate contains 369 entries: 361 closed at the simulated 1¢ entry price, eight remained open, no closed position hit the target, and realized paper P&L was $0. That is a failed test of the intended exit behavior, but it is not 369 realized losses.
Correction, September 9, 2026: the original headline described 369 losses, and later prose still inferred intraperiod prices, inevitable losses, and a successful replacement strategy from an aggregate that cannot establish them. This revision removes those conclusions. The historical counts remain unchanged. We do not have a new validated outcome for the proposed replacement.
What the retained record supports
The numerical account uses the retained aggregate CSV, whose basis column points back to the previously published operator summary. It preserves that account; it does not independently corroborate the original database. This was a separate historical strategy simulator, not the current Bot Builder Paper Account, and the export is not a trade-by-trade execution ledger.
| Recorded metric | Value | Interpretation limit |
|---|---|---|
| Entries | 369 | Entry count is not the closed sample. |
| Closed at the snapshot | 361 | All recorded simulated closes equal the 1¢ entry price. |
| Still open | 8 | Exclude these from closed-result conclusions. |
| Closed target hits | 0 | The configured target was not achieved in the closed sample. |
| Realized paper P&L | $0.00 | This is the recorded simulator output, not a fee-complete live result. |
| Side counts | 211 NO; 158 YES | These sum to the entry count and do not establish independent observations. |
| Average recorded hold | 55 minutes | An average cannot reconstruct the price path or the cause of any close. |
The aggregate labels zero trades as moving off 1¢. Without the underlying tick history, we interpret that narrowly: the export does not establish an exit above the entry price. It cannot prove that no executable quote ever changed between entry and close.
What the strategy was trying to test
The historical configuration described a scanner for cheap Bitcoin event contracts, with a 1¢–10¢ ask filter, a time-to-close window, five contracts per entry, up to eight concurrent positions, and a 90¢ exit target. These are the operator's recorded configuration notes. The aggregate itself does not independently reproduce the scanner, selection logic, or point-in-time inputs.
The hypothesis was that some selected cheap contracts would move enough to reach that target. The closed sample did not show that behavior. Price alone does not measure mispricing, and choosing the cheapest candidate does not establish that its probability was underestimated.
We cannot infer from this sample that every cheap contract is untradeable, that another threshold would have earned money, or that a particular volatility filter would have fixed the strategy. Each proposed change is a new hypothesis with a new test requirement.
What the aggregate cannot answer
- Which source response and market rules were available when each candidate was selected.
- Whether a quoted price had enough executable depth for the requested size.
- Why each simulated close used the entry price, and how missing quotes were handled.
- The price path between evaluations, queue position, partial fills, rejections, and latency.
- A complete live-equivalent fee, spread, and settlement reconciliation.
These are missing observations, not zero-valued metrics. The old article's precise volatility and price-path claims exceeded this evidence. More explanation cannot repair missing records; the next test must capture them.
The review guard we needed
Before another run, preserve a rule version, exact market identity, input timestamps, selection and skip reasons, order intent, simulated fill assumptions, closed/open counts, and reconciliation status. Set a review checkpoint in advance. Reaching a checkpoint should prompt inspection of the sample and failure modes; it should not automatically loosen the rule or authorize live operation.
A correct skip is a useful result. If an entry ceiling rejects the current ask, inspect that receipt before changing the ceiling. An error or missing source is different from a successfully evaluated false condition. Our Operator Note on reading a Paper decision walks through that distinction.
The earlier article described a replacement with a higher entry floor, a strike-distance filter, a volatility gate, and tiered exits. Those remain unvalidated ideas in this record. This revision makes no claim that a replacement is currently running or has improved results.
Inspect a smaller rule in Paper
The Paper limit-entry and exit-target recipe is a separate, authored Builder exercise. It does not recreate the historical exchange-wide Distressed scanner. Select one real market, review one contract at a 50¢ entry limit and an absolute 60¢ sell target, and inspect the supported order semantics before saving the stopped draft. The target is an order instruction, not a promised fill or a stop-loss. It keeps one open position at a time; after an exit, it may enter again if the same conditions hold and the five-minute action cooldown has elapsed.
For a reproducible gate check, we supplied the registered evaluator a synthetic market named KXRECIPE-26SEP09-DEMO with a YES ask of 55¢. The export labels that synthetic observation September 9, 2026 at 12:00 UTC; the price-only evaluator does not read that clock or check the close window. Against the 50¢ entry condition, the observed result is false. Download the observed condition output and compiler fingerprint. The file labels synthetic inputs separately from its actual generation timestamp.
This check covers the price gate only. It does not reproduce the old test, evaluate the complete runtime, demonstrate funded Paper execution, or establish profitable live performance. In your own connected account, review the full draft and its first explained Paper evaluation before drawing conclusions about how it behaves.
Methodology: historical numerical statements above come from the retained aggregate; historical configuration details come from the operator notes; the new condition check uses explicitly synthetic inputs. The correction preserves those boundaries so later work can build on what was observed without inheriting unsupported conclusions.
Frequently Asked Questions
Quick answers to common questions about 369 Paper Entries: 361 Closed, 8 Open, $0 Realized.
What happened in the 369-entry paper test?
The retained summary contains 369 entries: 361 closed at the simulated 1-cent entry price, eight remained open at the snapshot, no closed position hit the target, and realized paper P&L was $0. It shows that the intended exit behavior was not observed in the closed sample; it does not establish a complete root cause or 369 realized losses.
Does a 1¢ quote establish a useful opportunity?
A low quote alone does not establish mispricing or executable liquidity. This historical aggregate does not establish the probability or price path of every cheap contract; it only records the summarized test outcomes.
Were these real-money losses?
No — this was a paper-trading run, which is exactly the point. Paper trading surfaced the strategy's structural flaws before any real capital was at risk, which is why testing in paper mode first is a core discipline rather than an optional step.
What are the transferable lessons from the postmortem?
Preserve the rule version and input timestamps, distinguish open from closed observations, record skip and order reasons, and predefine when to stop and review. Missing price and execution records must remain unknown; a different threshold is a new hypothesis, not a proven fix.
Does a sound-sounding thesis mean a strategy will work?
No. “The thesis was sound” is exactly the trap — a plausible narrative can hide structural flaws that only show up in the math and the backtest. Disciplined testing, not conviction, is what separates a real edge from an expensive story.
Bring a strategy. Watch it become a bot.
Join the free live build on September 29 at 6:00 PM Pacific. Bring a market and a rule, or just watch. We’ll build a draft, review the workflow, demonstrate paper mode, and answer your questions.
We'll email the calendar invite and reminders for this webinar. Registering does not create an account. See our Privacy Policy.