Transparency — how you check the numbers yourself

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

• V01 — The verdict text is number + numeric band + comparison; no judgement adjective enters, and the 'adjective' mode in the configuration file is OFF — it only turns on by an explicit decision, for the day a licensed analyst signs.
• V02 — The top sentence has at most 25 words and is deterministic: the same input always yields the same sentence, with no language model in the request path.
• V03 — Special cases have their own text and never an invented number: negative profit (P/E does not apply, P/B still does), negative EBITDA, net cash, banks (ROIC and debt/EBITDA do not exist), a young company without history, a value carried with a declared note, a flagged value that is not published, and a multiple flag that belongs to another field.
• V04 — The confidence flag speaks about the SNAPSHOT, with reasons: green when nothing is off; yellow when a central number is withheld by a flag, when a material restatement (≥5% in a key account) happened in the last three years, or when the last annual statement is over 15 months old; red when the snapshot may mislead — the year's own statement was restated by more than 10%, or the regulator already holds a newer statement than the one computed here.
• V05 — The configuration file is coherent with the codebase: every flag it names is produced in precos.py or indicadores.py, the not-applicable map equals the company page's, the forbidden-terms list catches what it must and ignores the standard disclaimer, and the translator never queries the database directly.
• V06 — Run over every traded company: no forbidden term in any text, every top sentence within 25 words, every non-green flag carries a reason, the flag is not uniform (if 90%+ were one colour it would inform nothing), and the same ticker yields the same verdict twice.
• V07 — The 'below the Selic rate' cut for ROIC is switched on and off by the configuration file: off, the fixed band applies; on and with the fiscal year's average Selic, the band says below/at-or-above with the year and the rate; on without that year's Selic, it falls back to the fixed band and never invents the rate. No new label carries a forbidden term.
• V08 — Every cut in the configuration file falls on its declared side: a band's lower limit belongs to it; a zero ROIC with the Selic cut on is 'below', not 'negative'; the company's own history enters with 3 years, not 2; a restatement counts within the last 3 years, from exactly 5%, and only with a known difference; red needs MORE than 10% in the year itself and yellow-by-age MORE than 15 months. Born from the code mutation run of 26/09/2026: each of these comparisons could be flipped and the whole suite still passed.
• V09 — The top sentence is only shortened when it EXCEEDS the word limit, and the cut removes exactly the 'against X for the sector' clause (then the reason for red) — nothing else; zero net debt reads as '0.0x', not net cash; a zero margin with a flag is not narrated as a loss; a FLAGGED number is never narrated as 'not applicable'.
• V10 — The flag text states the filing date and how many central numbers were published, exactly — and the restatement reason quotes the cut as written in the file. The earlier test only checked the start of the sentence, and mutation showed that a date with one extra character or a doubled count went through.
• V11 — The verdict comes out in both languages: the top sentence, the six lines, the questions, the flag (text and reasons) and the note have an English version with the SAME numbers in English format (decimal point), with no Portuguese word; every band, “does not apply” mark, note and Selic band in the configuration has a translation; a bank’s “does not apply” and a caveat do too; no banned term in English.
• V12 — The top sentence of the verdict says the date of the P/E price (the first session after the statements became public) and the P/E at the latest close, plus the sector median, in both languages and within 35 words; the pl and pvp items carry valor_preco_atual and data_preco_atual (same earnings or book value, only the price changes), the text says which is which, and the value stays point-in-time.
• V13 — The P/E at the latest close multiplies the stored multiple by the latest close over the statement-day price and by the share factor of the confirmed events in between (a 2-for-1 split with half the price leaves the P/E equal); an event with no known quantity, or a missing or zero price, leaves the value out and the sentence cites only the point-in-time figure.
• I-V01 — `as_of` on /fatos returns, for each period, the highest filing version whose receipt date is on or before the date asked, with the version and receipt date on every row. The day a version arrived already counts as that version; the day before does not; before the first filing the period does not exist.
• I-V02 — When the version in force on the date asked existed but its values were not kept (the regulator publishes only the latest), the period comes back flagged and WITHOUT numbers — never with the next version's figures, which would be the leak of the future that `as_of` exists to prevent. A database from before the version tables still answers.
• I-V03 — The quarterly `as_of` applies the same rule per year and quarter; annual filings never leak into the quarterly answer.
• I-V05 — Ingestion archives the version about to be overwritten: only the key accounts, only when the incoming version is higher, before the upsert; every version of the filing is kept with its date and document id; re-ingesting or a late older version changes nothing. Annual and quarterly.
• I-V07 — The rule that decides which accounts are kept covers every account the standardisation reads and rejects the ones no item uses: an account forgotten here disappears from the past without a trace.
• I-V08 — A build from scratch loses no versions: what the previous database still holds in a lower version is captured, the history already archived is inherited, a missing or incompatible previous database changes nothing, and the archive count is among the shrink-guarded counts.
• I-V10 — A past version read from the filing XML on the regulator's portal is stored in the same convention as the current version: only the current period, consolidated and individual kept apart, scale applied, both number formats read correctly (with and without the thousands dot), the cash-flow method kept, equity only in the total column, quarterly filings only for the isolated quarter, unused template accounts left out, nothing already stored overwritten, and a file that cannot be read or does not match is counted by reason instead of stopping the load.
• I-V11 — A past version read from the old-format filing file (2020 and earlier) is stored in the same convention as the current version, even though that file names neither the company, the version, the period nor the scale: the document comes from the list and the scale from the total assets the base already holds. Annual filings read the first value column, quarterly ones the second (and the fourth for the first-quarter cash flow and income statement); consolidated and individual stay apart, direct and indirect cash flow stay apart, equity is read only from the current period and the total column, a statement left entirely at zero is not stored as if the company had reported zero, and a file with no total assets to compare, an unclear scale or a layout that contradicts the list is counted by reason instead of being guessed.
• I-V12 — `as_of` on /fatos also picks up the figure RESTATED as a comparative in the next year's annual filing, from the receipt date of that exact filing version (the day before it still returns the original). The row says where the number came from, when it became public and the original value; the old version fields keep describing the company's own filing. Without `as_of` nothing changes.
• I-V13 — A restated comparative replaces the original only for the SAME account: same label, not zeroed in the file, not off by a factor of a thousand, same consolidation basis; a later re-filing of the year itself wins over an earlier comparative; when the version in force has no stored numbers, only the items the already-public comparative covers are returned, never the newest version's figures.
• I-V14 — The /fatos route exposes the origin, public date and source document of each row and the count of restated items on the `as_of` path; without `as_of` the published (original) fact is returned, with no new field.
• I-V15 — Three real restatements from the restatement table (an ordinary company, a bank with its own chart of accounts, another ordinary company): the day before the next annual filing is received the original comes back, the day it is received the restated figure comes back, original and restated never swapped.

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

• I-V04 — The items rebuilt from an archived version are the SAME ones the standardisation writes from the same accounts, for an ordinary company and for a bank; only the origin gains the version suffix.
• I-V06 — The versions route lists each filing with every version, its date, the link to the original and whether its values are in the base, archived or not kept; between two versions with values it lists only the accounts that changed (before and after).
• I-V09 — The routes: /fatos without `as_of` is unchanged; with `as_of` it answers the version in force; an invalid date is a 422; /versoes lists the filing with both versions and filters the re-filed ones.

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: