Transparency — how you check the numbers yourself

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

• TL01 — The recorded Anatel file (one row per tax ID and product, one column per month) becomes the sum per operator and month: Vivo in August 2026 has 85,818,766 mobile accesses WITHOUT M2M and service points (which go to the other column: 20,141,773), and the August TOTAL adds up to 220,921,381, equal to Anatel's official total; an operator under 100 thousand accesses stays out (only in the TOTAL); an empty file, one without the checked fields or without month columns returns nothing and the reason; an empty cell is "no data", not zero; a malformed tax ID drops the row.
• TL02 — The Anatel ZIP is read by byte range: the central directory comes from the end of the file and only the requested member is downloaded and decompressed as a stream; a missing member returns None; ZIP64, an unknown compression method, a file that is not a ZIP and a server that answers HTTP 200 instead of 206 all stop with an error instead of downloading gigabytes.
• TL03 — The collection writes both services, checks the TOTAL against Anatel's official total month by month (0.0% difference) and stores the result in the telecom collection record; a source that is down, a file without the checked fields, a value outside the plausible range, a summed total more than 5% away from the official one or an exception writes nothing for that service, deletes nothing, never raises, lets the other service go on and leaves the reason in the record; repeating the collection does not duplicate rows.
• TL04 — The batch of files: the history reads from 2023 (mobile by semester, broadband by year), the recent run reads the current period (broadband also reads the previous year in January and February); the night only collects again when it never collected, the last run had an error or it is more than 6 days old.
• TL05 — The telecom accesses table is part of the inheritance of external series: in a from scratch build where the source failed the rows of the previous database come back, the fresh row wins over the old one, and the shrink guard counts the table.
• TL09 — With no telecom accesses table in the database the filtered JSON route answers 503 with Retry-After, the unfiltered one answers 200 with a notice, the page answers 200 in both languages with the series being collected notice, noindex, the licence and the agreed use but no number, no table and no link to the JSON route, the health route does not fail and shows the telecom block as null, and the sitemap does not announce the page.

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

• TL06 — The ranking uses the consolidated month (the one before the newest): TOTAL first, then Vivo 85,818,766 (38.85% of 220,921,381; +1.60% against 84,463,402 a year earlier), Claro, TIM (-2.60%), Surf; the preliminary month comes apart and is not in the calculation; broadband falls in September (as in the official total) so the ranking stays in August; the monthly series flags the newest month as preliminary.
• TL07 — The link to a stock exists only when the full tax ID of the operator is the one of a company with a ticker: Telefonica Brasil links to VIVT3 from the register, TIM S.A. links to TIMS3 from the main row of the ticker table, Claro never links, and a company with the same name, the same 8 digit root (another branch) or no ticker never links; with no register row nothing is invented.
• TL08 — The accesses route returns the ranking of both services with source, the CC BY-ND 3.0 licence (never CC BY), the use arranged with Anatel, the required attribution and a citation line, with no municipality, technology or product rows; with a service and a tax ID (with or without punctuation, or TOTAL) it returns the monthly series cut by from and to months; CSV has a fixed header; bad parameters give 400 and an unknown operator 404.
• TL10 — The telecom page in Portuguese and English opens with the sentence of totals and leaders, the attribution to Anatel at the top, the two tables with the Vivo line (85,818,766, 38.85%, +1.60%), the preliminary month apart, the notice that M2M and service points are left out, that the sums, the TOTAL, the share and the change are our calculations and that an operator is not the stock, the source with both files, the CC BY-ND 3.0 licence, the use arranged with Anatel, the citation line, the canonical link and a JSON-LD dataset; only Vivo and TIM link to a stock and only with the identical tax ID; no browser script other than JSON-LD.
• TL11 — Without a register row with a ticker and an identical tax ID the page links to no stock at all, neither by the name Vivo or TIM nor by the group.
• TL12 — The health route carries the telecom block (newest month, age per service, 75 day limit, last collection) and raises attention only past the limit, not at it; the Macro hub in both languages and the API hub carry the page and route cards; the sitemap announces the page with the first day of the newest month as last modified and never in the future; llms.txt cites page, route, licence and the agreed use; the methodology pages exist in both languages with the source, the CC BY-ND 3.0 licence (never CC BY), the agreed use and the attribution.
• TL13 — The telecom connector tool calls the same route as the page: with no argument it returns the ranking with source, licence and attribution, with a service and a tax ID it returns the monthly series, and a bad request comes back as an error field and never as an exception.

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: