What's real, what's delayed, and what's simulated

Most tools in this category tell you what their data says. None of them tell you which parts are real. This page names every RadarPulse data module, where it comes from, and its status at this moment.

It is not a written statement of intent. The table below is read live from the same public endpoints the product itself runs on, every time you load this page. If a feed goes down or a key expires, this page says so on its own, without anyone editing it.

Right now

The rule that matters most

The cross-domain confluence board is the thing RadarPulse is actually for: names where unusual options flow and a disclosed congressional trade point the same way. It ranks tickers 0 to 100 and it is the most repeated module in the product, so it is also the one where a fabricated number would do the most damage.

It is scored only on a real options tape. When the tape is a generated sample day, the board does not render a "simulated" label over a live-looking score. It does not render at all, on any surface, and says why. The congressional half has always been guarded the same way: the demo seed used by the private betting views is tagged and can never reach a real Congress surface.

That is a deliberate trade. It means the board is empty outside market hours more often than a competitor's would be. An empty board is the honest rendering of "no real flow yet."

Verifying the graded board

Every trading day RadarPulse publishes its top flow board and later grades it in public on /proof. Alongside each published board that page prints a daily fingerprint: a SHA-256 hash of the exact board being shown, computed in your browser from the public feed. It is a property of a board, so on a day with no board there is nothing to fingerprint and none is shown, which is what you will see whenever the flow feed has produced no scored prints.

Be precise about what that does and does not prove. It does let you record the fingerprint for a given day and re-check it later: if what we publish for that date ever changes, the hash will not match what you recorded. It is a fingerprint you can hold us to, and you can recompute it yourself from the same public endpoint rather than taking our word for the value.

It does not prove we could never have altered the underlying feed before you first read it. A self-published hash is not a third-party timestamp, and claiming otherwise would be exactly the kind of overstatement this page exists to avoid. Anchoring the daily hash in an external append-only record is the honest next step, and it is not built yet.

What we don't have

The gaps matter as much as the features. None of the following exist in RadarPulse today, and none of them are simulated to look like they do:

• Real-time options flow. The tape is 15-minute delayed on every plan. Real-time OPRA redistribution runs to roughly $1,500 a month, and RadarPulse is pre-revenue. The decision is to stay on honest delayed data rather than charge for a feed we cannot afford to make real.
• Fundamentals, analyst consensus, insider filings, technicals. These need a paid market-data provider. The pages are built to hydrate them honestly when one is connected; until then they are absent, not mocked.
• Live in-game player statistics. Fantasy scoring is modeled from projections and labelled as modeled. It is never presented as a live box score.
• Economic calendar, IPO calendar, dividends, dark-pool prints. Provider-gated, and deliberately not faked to fill a tab.
• Offline use. RadarPulse installs as a real app — home-screen icon, standalone window, and the shortcuts that come with it — and it works while you are online. It does NOT work offline: the service worker handles push notifications and deliberately caches nothing. That is a decision, not an oversight. Every surface here is live market data, so a cached copy would be stale the moment it was served, and a worker that serves a stale app build is a worse failure than one that simply needs the network.
• Federal lobbying spend (Senate LDA filings). Public record, quarterly, and now the fourth record the confluence score can cross. It contributes only on a real filing with a real dollar amount, only when that filing is current, and at most 8 of the 100 — a quarterly disclosure does not carry the weight of an intraday print. BETA: the client-side read of lda.senate.gov is confirmed on the live site, not from the build environment.
• Gamma, delta and vanna exposure (GEX/DEX/Vanna). Dealer-positioning surfaces built on full options-chain and open-interest history. Specialist terminals carry them; we do not, for the same reason we do not carry real-time flow — the underlying feed costs money we do not spend pre-revenue. Named here rather than left for you to discover by comparison.
• Live quote data behind the S&P heat map. The market-data plan in use does not include the quote endpoints, so the heat map is built from company profiles for tile size and a separate live feed for tile change. Both numbers are real, and the per-tile price is simply absent rather than estimated. Upgrading the plan would restore it; that is a cost decision, not a code one, and it is not made yet. We are not quoting a price here because we have not re-checked the current one, and an unverified number on this page would be the exact thing it exists to avoid. The live state is published at /health under heat, so "degraded" is visible without asking us.

How to check us

Everything on this page is derived from endpoints you can open yourself. The flow feed's own state is published at /health; the congressional filings are at /api/politician-trades; the graded record is at /api/v1/scorecard. If this page ever disagrees with what those return, the endpoints are right and this page is broken. Tell us.