Disclosure
reout · Systematic BTC
This document sets out what the repository publishes and what it deliberately does not.
1Status
The program trades the proprietary capital of reout, which is not registered with any financial regulator. The account traded as a pilot before the record began. The pilot's results are published separately and are not part of the record (Methodology, section 1).
Nothing in this repository is an offer, a solicitation or investment advice, and reout does not
sell signals or solicit investors. Inquiries from institutional allocators and independent
verifiers may be sent to ops@reout.io. The program is not open to individual investors at this
stage.
2Published and not published
| Item | Published | Not published |
|---|---|---|
| NAV and cash flows | Daily returns and a net asset value index, every external transfer and daily totals of realized P&L and of costs (commissions and funding combined), each as a share of net asset value, produced by a public workflow | Currency amounts, including the size of the account; the income ledger record by record; commissions and funding separately |
| Positions | Whether, how many, which side and what size | |
| Trades | Trade statistics and individual fills | |
| Kill criteria | Thresholds, and the program's position against them each month | Specific form of the system-fault signals |
| Configuration | Hash, anchored before deployment | Model, parameters, filters |
| Documents | Methodology, version register, incident log, corrections | |
| Research | Research process, experiment results, rejected variants, development data |
Items not published would disclose either the program's current exposure or its implementation. A verifier under NDA may confirm the sealed configuration against its hash in the pre-registration manifest, which establishes that it was fixed before the record began (Methodology, section 11).
3Disclosure of the method
Information about how the strategy makes decisions is provided at three levels.
| Level | Content | Audience |
|---|---|---|
| Category | Systematic, directional, single instrument, long and short; signals from a learned model | Public |
| Thesis | The inputs the model conditions on, the reason the edge is expected to exist, and the reason it is expected to persist | Verifiers under NDA |
| Implementation | Model, development data, parameters, gates and execution rules | Not published. An independent verifier under NDA may inspect the sealed configuration only to confirm it against its pre-registered hash |
Public material about the strategy (monthly reports, methodology notes) remains at the level of category and measured properties, such as drawdown and correlation with the benchmark. It does not describe the thesis.
The deployed model was developed on data that end before the live period, so all live results are out of sample.
4Incidents
From the start of the record, every operational incident is disclosed in the monthly report for the month in which it occurred, including incidents with no effect on P&L. The list is not edited. Manual actions on the account are also logged in the intervention log at the time they occur.
5Contact and identity
ops@reout.io, for institutional and verification inquiries.
The channels of reout are the domain reout.io, the GitHub account reouthq, of which this is
the only public repository, and the X account @reouthq. Any other site, account or address
claiming to represent reout is unrelated.
This page renders DISCLOSURE.md at track commit cbdaf12, built by d2a944c of the site. What is anchored is the file, not this page.
SHA-256 c00e94214f53cac2282f30d2e2675323b0582ccfd4a866ff05df72967da63b72