Historical information sets
Effective, published, retrieved, and known-at clocks stay distinct.
Move from a delayed or realtime event feed into the exact evidence graph, known-at timeline, source policy, saved view, and delivery configuration without changing products.
Effective, published, retrieved, and known-at clocks stay distinct.
Events retain source documents, entities, revisions, and coverage state.
Serving checks the active source policy and withholds restricted text.
Filter stock, crypto, macro, regulatory, and protocol events; inspect citations and corrections; save views; and configure signed alerts.
/dashboard/intelligenceEvent feed → evidence drawer → asset timeline
Saved view → signed webhook
Coverage → source policy → known-at cutofffeed stateEvery card retains event identity, revision, source class, asset scope, and plan delay.
evidence drawerCitations, document display state, entity links, clocks, and correction history stay one click from the event.
asset timelineResolved stock, crypto, protocol, venue, and macro events share one chronological research view.
coverage panelSource freshness, universe, rights policy, latency, and missing states qualify every search result.
saved viewReusable filters preserve asset class, event type, source, query, time window, and display-state choices.
delivery stateWebhook endpoint, signing status, retries, last delivery, and automatic suspension remain account-scoped.
Filter the event feed across stocks, crypto, macro, regulators, exchanges, and official protocol sources.
Open a cluster to review primary evidence, source conflicts, resolved entities, and revision history.
Apply a known-at cutoff and use the asset timeline to see only evidence eligible at that point.
Save the view or create a signed webhook using the same filters and source-rights controls.
Eligibility depends on the account plan and source. The terminal states the applied latency class—15 minutes, five minutes, one minute, or realtime eligibility—instead of silently presenting delayed events as live.
Yes. The evidence drawer exposes display-safe citations, canonical source URLs, publication and known-at clocks, entity relationships, source policy, and event revision history.
Yes. A saved filter can become an account-scoped webhook subscription. Deliveries are HTTPS-only, HMAC-SHA256 signed, idempotent, retried, and disabled after repeated failures.
The source registry, coverage ledger, terminal, REST API, SSE stream, signed webhooks, and remote MCP server are live surfaces of the same rights-aware graph.