Definitions before conclusions
Polytrack publishes code-reviewed notes on how to interpret monitored trades, severity, wallet activity, aggregates, rankings, and alert delivery. Each note names its sources, states what the evidence can support, and preserves the limitations that should travel with any quotation.
Current library
A useful alert system reduces a large stream to a smaller review queue. It does not turn unusual activity into proof. This note explains the reasoning boundary behind Polytrack severity labels and the checks a reader should make after a record is flagged.
Read the noteWallet-level research is valuable because one address can connect trades, positions, and repeated patterns. The same convenience creates an attribution trap. This note separates address-level evidence from claims about people, teams, services, or ownership.
Read the noteAggregates become misleading when their denominator disappears. This note defines the difference between volume in Polytrack's monitored records and total Polymarket activity, then gives a checklist for reading rankings and trends consistently.
Read the note“Real-time alert” language can hide several independent systems. Polytrack instead documents the path from upstream availability to ingestion, classification, eligibility, Telegram delivery, and the subscriber's device so users know what a message can and cannot promise.
Read the noteA public note should be easy to quote without becoming less true after the quote is shortened.
Methodology explains how records and metrics are built. Data Sources shows provenance. Limitations defines the claims those facts cannot support.
