j0osman/reamer-support

Reamer Support is not the actual Reamer software. It is a place to report problems with Reamer, a separate product that lives at reamerlabs.com. The real Reamer code is not public, so this repository exists purely so that bug reports, wrong results, and confusing documentation have a place to be tracked in the open, instead of being handled quietly through private email. Reamer itself is described as a local-first, deterministic backtesting engine built for systematic traders who work with OHLCV data, which stands for open, high, low, close, and volume, the standard columns used in trading price data. It combines a C++ execution core with a Python strategy toolkit, a published execution specification that defines exactly how trades should be filled, and a conformance suite of 282 checks that verifies every simulated fill against that specification. It is free to start and does not require a signup. If you find something wrong, you can open an issue in this repository describing a bad fill, a result that does not match the published spec, a misleading docs page, or a crash. The maintainer, who goes by j0osman, says they read every report personally: there is no ticket queue or support team in between. If a report turns out to be a real bug, they fix it and post publicly what was wrong, what changed, and confirmation that it is safe to try again. If something is not actually a bug, they explain why instead. Before filing a report, the README suggests checking the docs and the execution spec first, since many questions about whether something is a bug are already answered by the spec's rules for how ties and fill prices are decided. It also asks reporters to include their Reamer version, operating system, and Python version for SDK issues, and to attach the .reamer file for a disputed result, since that file is self-contained and lets the maintainer reproduce the exact run rather than guess at it. This repository is intentionally small. It is a support channel, not the product itself.