BSP / Buying analysis
Methodology Transparency: Know the Rule and the Limits
A readable mechanism makes a claim inspectable. It does not establish that the mechanism has an advantage.
Required rule fields
Identify the eligible instrument, condition, time window, exit owner and amendment policy. A provider can keep proprietary details private, but a buyer still needs the operating instructions necessary to use the product without guessing.
Version control
Save the active rule or product version. A changed script, indicator input or published policy can create a different workflow. Do not assume that a current chart or revised document reconstructs past instructions.
Undocumented choices
If ambiguous cases are resolved only after an outcome, the method cannot yet support a reproducible comparison. Preserve the ambiguity and request a prospective rule. Transparency can justify further examination without implying audited performance.
Decision Record
| Decision question | Record to retain |
|---|---|
| What should I request? | Identify the eligible instrument, condition, time window, exit owner and amendment policy. A provider can keep proprietary details private, but a buyer still needs the operating instructions necessary to use the product without guessing. |
| What should stay unresolved? | If ambiguous cases are resolved only after an outcome, the method cannot yet support a reproducible comparison. Preserve the ambiguity and request a prospective rule. Transparency can justify further examination without implying audited performance. |
Continue the Comparison
Source Documents and Scope
Primary documents support the stated mechanisms or attributed records. The buying procedure is BSP editorial analysis, not a paid-product, latency or subscriber-performance test.