Insider trades became one layer, not the whole dashboard.
The project started as a portfolio Form 4 tracker, then expanded once it became clear that raw trades need market context before they are useful.
Market Intelligence
Insider Dashboard
A market confirmation surface that combines broad context with portfolio-specific insider activity so raw trades are reviewed in the right environment.
The useful signal was spread across different cadences.
Daily, weekly, monthly, and rolling 90-day inputs all mattered, but they were too fragmented to form one operational view.
Collection Pipeline
How the dashboard is actually built.
Scheduled Python collectors pull market context and portfolio insider activity into JSON files committed back to the repo. The walkthrough below shows how the GitHub Pages dashboard turns uneven inputs into one static review surface.
SEC EDGAR + Yahoo
AAII + NAAIM
CBOE PCR
GitHub Actions cron
static JSON publish
Inputs
Preparation
Scoring / Context
Outputs
Decision
Use cron jobs and JSON instead of a backend.
GitHub Actions runs Python collectors on different schedules, commits JSON files back to the repo, and the single-page frontend fetches those files client-side to render charts, panels, and trade signals.
The dashboard became a multi-layer market surface.
It stopped being just a Form 4 tracker once market context and historical insider behavior became part of the review surface.
Some sources are fragile.
PCR data needs manual fallback maintenance, source cadences are uneven, and the dashboard still depends on external public datasets staying reachable.
Tighten scoring across panels.
The useful next layer is making the regime, trade, and sector panels resolve into one clearer ranking instead of leaving some weighting in separate visual blocks.