The signal evidence register.
An event ID. Original levels. A trace of what was received.
Receiver population
Every proposal retained by CyGuru’s connected TradingView receiver enters this register. The original entry, stop and targets remain attached to its event ID. Lifecycle reports appear with both their stated observation time and this site’s receipt time.
Other CY66 engines, missed deliveries and periods before this receiver began are outside this population. A source-reported target or closure has an evidence level of “reported”; order fills and net account results require a separate evaluation.
Connecting lifecycle reports
The existing authenticated TradingView receiver also accepts the following lifecycle format. Each update needs its own unique event ID and the original proposal’s signal ID and engine. A source report records the sender’s assertion. Independent evaluation still requires the price path, fixed execution rules and costs.
{
"schema_version": 1,
"event": "signal_update",
"event_id": "UNIQUE_UPDATE_ID",
"signal_id": "ORIGINAL_PROPOSAL_EVENT_ID",
"engine": "EXACT_ORIGINAL_ENGINE",
"observed_at_ms": "UNIX_MILLISECONDS",
"state": "closed",
"outcome": "tp3"
}Allowed states: pending, active, closed, expired. Allowed outcomes: unresolved, tp1, tp2, tp3, sl. The sender uses the existing authenticated receiver configuration. Unknown proposals, mismatched engines and conflicting reuse of an update ID are rejected. Sending an update cannot overwrite the original proposal.
Read the publication and evaluation methodology →