Scheduled public intelligence
The daily edition, separated from the homepage and designed for focused review.
Slice now gives public intelligence its own light route. The page reads one retained edition, displays source and freshness state, and performs search and category filtering locally after the response arrives.
Publication model
A calm daily surface backed by a scheduled intelligence process.
Scheduled for 6:00 AM Eastern Time.
Six selected public stories per completed edition.
Provider and official-feed source health retained.
No continuous polling or background animation loop.
Public intelligence is context for professional review. Source evidence, freshness, suitability, and client-specific implications still require judgment.
Completed daily edition
Sourced intelligence without a visit-triggered provider scan.
This page reads the retained scheduled edition, keeps source evidence attached, and filters six selected stories locally after the first response.
Edition
Loading
Waiting for retained edition
Selected stories
—
Fixed public article limit
Source health
—
0 source items evaluated
Priority review
—
Awaiting edition
0 matching stories
All selected stories in the completed daily edition.
Loading the completed intelligence edition…
The page shell is already usable while one cached public response completes.
Publication safeguards
Fast public reading without sacrificing evidence or review controls.
The new route limits provider work, keeps article provenance visible, and clearly separates public intelligence from protected advisor analysis and client-specific action.
One scheduled response
One completed edition
The public route reads a retained scheduled snapshot instead of starting a new scan for every visitor.
Source evidence attached
Publisher, provider, timestamps, themes, tickers, score, urgency, and source health remain visible.
Priority is review—not automation
Alert candidates are surfaced for advisor review without turning a public story into an automatic client action.
Local search and filters
After the single edition response loads, search and category changes run entirely in the browser.