SignalRadar Global Manual

This is not a generic news surface. It compresses live intake into a 72-hour risk frame, a small set of validation points, and a shorter impact-asset list that can be checked quickly.

• Frame the dominant path before reading secondary narratives or isolated headlines.
• Reduce the screen to a few validation points that can confirm, weaken, or break the current path.
• Map the first transmission into sectors, assets, and timing instead of treating all incoming news as equally important.

The homepage is the terminal view. Its job is to tell you what matters first, what must be verified next, and where pressure is landing.

• Read the lead event and risk gate before drilling into any lower-level page.
• Use the checkpoint stack to decide what would keep the path alive and what would downgrade it.
• Use the live feed chronologically so the order of catalysts is visible before you infer causality.

The thesis engine is where the system expands the homepage frame into a base path, alternative branches, and a more explicit explanation of transmission.

• Read the base path first, then compare alternative branches instead of mixing them together.
• Use the validation conditions to judge whether the thesis is strengthening, stalling, or failing.
• Treat the thesis as a probability-weighted narrative surface, not as a single irreversible call.

Validation points are more important than elegant narration. A path should survive contact with observable catalysts, market transmission, and timing.

• Prefer validation points that are observable within the next 72 hours.
• Watch for mismatches between the narrative, the catalyst calendar, and the assets supposedly benefiting or absorbing pressure.
• If validation becomes vague, delayed, or contradictory, downgrade confidence rather than adding more words.

Impact assets are the shortest list of sectors or assets where the current path is transmitting first. They should narrow the search area, not expand it blindly.

• Use impact assets to see where the path is landing before looking for secondary beneficiaries.
• Cross-check impact assets against crowd heat, macro timing, and whether source flow is broadening or narrowing.
• When impact assets keep rotating without confirmation, assume transmission is unstable.

The protocol page is a secondary object layer. It records scenario objects, consensus snapshots, and resolution history after the lead path has already been framed elsewhere.

• Use it to inspect a standardized scenario object, not to discover the dominant path from scratch.
• Read the current consensus, participant spread, and resolution method as audit data around the thesis.
• If the object layer disagrees with the terminal frame, review the validation points before trusting either side.

This system is a public research terminal. It helps structure observation, but it should not be mistaken for personalized execution advice.

• Start from the path and validation points, not from a single asset move or headline.
• Treat probability, consensus, and impact maps as working surfaces that can degrade quickly under new information.
• If the terminal feels wrong, inspect source freshness, catalyst timing, and the last thesis update before drawing conclusions.