PUBLIC TIMESTAMPED RECORD
The calls. The follow-through. The failures.
Evidence overview: historical practice, forward prices, costs and missing results →
This archive shows saved APEX and Cascade state changes, including inactive states and missing outcomes. A repeated active state is not counted as another call. No sign-in required.
Earlier snapshots were recorded privately and are labeled prior private archive. They are not evidence that these calls were publicly visible at the time. Research candidates stay separate from confirmed calls.
Loading the saved record…
Timestamped state log
Original database publication time is shown in UTC, alongside the source-price time. Outcomes use a fixed 30-minute horizon; no stop-based trade profit is implied.
| Record / cohort | Published / source time | Instrument / engine | State / direction | Reference / invalidation | 30-minute signed move | Outcome / failure evidence |
|---|---|---|---|---|---|---|
| Loading… | ||||||
How the numbers are counted
Failure visibility: every completed negative directional outcome remains in the adverse count. Flat, pending, missing and outside-session cases remain visible. Observed invalidation only means a saved price crossed the original risk line; sparse samples can miss crossings.
Integrity: original snapshot IDs, versions and SHA-256 digests of the public record projection are exposed in JSON. These help compare downloaded records; they are not cryptographic proof of an immutable database or an independent timestamp authority. Outcome fields can mature later. A collector outage is a coverage gap, not a winning or losing call.
Scope: underlying-price observations before costs, not fills or options P&L. The archive covers the automated APEX/13-instrument and stock-discovery collectors. Unsaved on-demand lookups, private chat statements and ARM experiments are not retrospectively invented as published calls.