How every number is made. Check us — the sources are one click away.

Every tracked asset gets a fresh dossier version once a day, committed at 00:10 UTC. A version is a frozen slice: the day's closing price, computed technicals, relative performance against a benchmark, risk measures, fundamentals from regulatory filings (stocks), sentiment, and timestamped headlines — each block traced to a primary public source listed in the dossier's own footer.

The boards and mastheads follow the market between commits; the dossier documents stay the committed end-of-day record. When a feed is down we show the last committed number with its honest date — this site never fabricates a value to look fresh. A failed read is treated as a failure, never as "no data".

One row per tracked asset, generated from the same registry the pipeline reads — this table cannot drift from the code that fetches the numbers.

Every dossier is built on one ordered skeleton. A report renders only the sections that apply to it — a treasury yield has no fundamentals to report, so that section simply doesn't exist for it — and the printed numbers renumber contiguously, so every asset class reads as a complete document rather than a form with blanks.

A report is marked stale when its data date is older than the market's own rhythm can explain: crypto trades seven days a week, so silence beyond 2 days means the feed slipped; everything else gets 4 days, so a Friday close stays fresh through the weekend plus one holiday. Stale reports say so — an amber marker on the board and the version plate — instead of quietly presenting old numbers as current.

Feeds break. When one does, the policy is heal forward with a visible notice: history is append-only, so a version committed while a feed defect was live keeps its published numbers forever — but it must never present them as clean. Detection is signature-based (impossible values like a zero 52-week low or a −100% drawdown), which cannot false-positive on healthy data. Affected versions carry a data-quality notice pointing at the corrected latest; the next daily run heals the record going forward. Published documents never change under their permalinks.

• · Append-only. A committed version is never edited or deleted. The archive is the record of what we published, including our mistakes.
• · Version numbers are positional. v3 is the third commit for that asset, derived from position at read time — permalinks can never renumber.
• · Out-of-order commits are refused. A late-arriving close can never insert itself behind history and shift the chain.
• · Failure is failure. A failed store read aborts the run rather than being treated as an empty archive; a broken upstream throws rather than serving fabricated zeros. Stale-and-real beats fresh-and-fake, everywhere.

PakupAI is a research publication, not an investment adviser. Nothing on this site is investment advice, an offer, or a recommendation to buy or sell anything.

Every number is a computed description of publicly available end-of-day data — never a prediction. We take no custody of funds, execute no trades, manage no accounts, and sell no picks, signals, or results. Reports are general-circulation research: the same document for every reader, personalized for no one. If a read would change, the condition that would change it is printed in the report itself.