Signal journal
Original levels. Every stored update. Visible receipt times.
Checking stored records…
Last successful read: pending. Auto-refresh every 30 seconds. Receipt history proves past delivery, not a continuously working alert or phone notification.
System delivery history · nine indicators
CyGuru Indicator
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
66 Trend
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
66 Reversion
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
66 Breakout
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
66 Upside Momentum
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
66 Downside Momentum
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
66 NSI
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
66 Hazem Signal
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
CyGuru Safe Signal
Checking- Stored entries
- —
- Outcome updates
- —
- Last entry received
- Not received
- Last outcome received
- Not received
- First stored receipt
- Not received
Loading…. The journal covers records retained on this site, not all chart history. Older original signals fetched only from CyGuru may appear on the terminal without a local journal entry.
Evidence and limits
SUCCESS means a script-reported target hit, not realised profit. TP1 can be followed by a stop. Final updates missing after the evaluation window are flagged, never invented as losses or expiry. Older CyGuru proposals have no outcome events. CyGuru v3.3 supports modeled entry and outcome updates after its new alert is connected. No broker fills or net P&L are inferred.
Accepted events are stored without overwriting an existing event ID. This is an operator-hosted record, not an independently notarised audit. Rejected webhook attempts and phone delivery confirmations are not recorded here.