Transparency — how you check the numbers yourself

Level 1 — Integrity: does the data tie out? (14)

• VG01 — Each event type in the product instruction is detected — profit turned into loss (or the reverse), net margin and net debt/EBITDA changing band, restated statements, the confidence flag changing colour — each with the previous and new period, the number before and after, the date the revealing filing became public, the source and the data version. A restatement is dated by the NEXT annual filing, where the year comes back with a different number. A series with no change yields no event.
• VG02 — No number lives in the watcher's code: the bands are the verdict's, the restatement cut is the same as the flag's, and the quarter used for comparison is chosen in the configuration file — changing the file changes the event.
• VG03 — Only a number the verdict would publish becomes an event: a flagged value, a not-applicable value (negative EBITDA, zero revenue), an indicator that does not exist for banks, and an account that is zero on one side of a restatement (a missing line, not a republished number) are left out. A number the site withholds cannot change band in public.
• VG04 — No watcher text — Portuguese, English or the e-mail — carries a forbidden term, even when the company described the account as 'sales revenue': the text uses our own label and the filed description travels only in the JSON. The e-mail is a skeleton: it builds subject and body for the followed tickers only, and nothing in the module sends, schedules or stores subscribers.
• VG05 — The watcher reads only through the data layer and the verdict — no SQL in the module or its page — and imports neither the API nor the company page; the page only builds HTML. Deterministic: the same input yields the same events.
• VG06 — Run over every traded company: every event has a known type, both periods, both numbers, a date, a source and the data version; no text carries a forbidden term; all five types occur; the monthly counter adds up to the list; a restatement is never dated in its own year; the same ticker yields the same events twice.
• VG07 — /vigia and /vigia/eventos open without a key; the monthly counter on the page and in the JSON is counted from the list, never typed; each event on the page links to the company page and shows its source; filtering by ticker and type works; an unknown type is a 400; the page is in the sitemap and llms.txt.
• VG08 — REIT watcher, pure function: P/B, 12-month yield and vacancy changing band and unitholders changing beyond the cut-off come with both numbers, both periods, both bands and the date of the revealing filing. Only the immediately previous period is compared (a gap is no event); a flagged number is no event; the cut-offs come from veredito_config.json; unitholders need the minimum in both reports.
• VG09 — A report with version above 1 is an event dated by the delivery of the version in force; if the build captured the re-filing, the event carries the field that changed most (before and after) and how many others changed; without capture it says only what is known. Version 1 is no event.
• VG10 — /vigia?classe=fiis and /vigia/eventos?classe=fiis show what the REIT watcher returns, filterable by type and fund, with a SEPARATE monthly counter; /vigia without a class is still the companies' page; an unknown class or type is 400; no forbidden term in any fund event; the e-mail is only a skeleton.
• VG11 — The 12-month yield has no series at the source: each build snapshots fii_yield into fii_yield_historico (one row per fund and base date), with the versioned derived file in the symmetric step; leitura_fii reads on a read-only connection and accepts a database without the new tables; the REIT watcher has no SQL.
• VG12 — The text formats (reais in thousands/millions/billions in both languages, date, quarter), the detection edges (zero margin is neither profit nor loss; a restatement exactly at the cut-off counts; a number missing on one side makes no band event), the event direction both ways and in English, the restatement source, the flag periods, the counter by type and without date, and the empty, sorted e-mail.
• VG13 — REIT watcher: each band label in both languages; a value exactly at a cut-off belongs to the upper band; unitholders exactly at the minimum count; a fall is written as “fell” and “−”; unitholders with thousands separator and no decimals; on a re-filing, the field that changed most in RELATIVE terms and how many others; the counter by type and month; the filter by ticker and type; the e-mail empty, with inclusive `desde` and ordering.
• VG14 — The restatement text: one account (“one account changed ...”) or several (“N accounts changed ...; the largest”), with the fiscal year and the following annual filing, in PT and EN; among accounts with the same relative change, the one with the largest absolute change is chosen. In the REIT watcher: the English unitholders text without decimals; a capture with only “no field changed” gives the text without numbers; month distance with two-digit months; an undated event sorts after dated ones without breaking.

Level 2 — Semantics: does the account mean what the calculation assumes? (0)

Level 3 — Economic: is the result possible in the real world? (0)

Other product tests (0)

Access gate, navigation and the MCP connector — they test whether the product works, not whether a number is right, so they don't fit the 3 levels above by design. Still counted, still listed: