{"updated_at":"2026-10-08T11:13:35.232103+00:00","credibility":{"methodology_version":"2026-07-03","status":"descriptive","meaning":"measures TODAY's signal (like the VIX measures today's fear). Does NOT promise future accuracy.","coverage":"United States, 49 regions; anything outside is not measured","methodology_url":"/api/v1/regions/methodology"},"what_this_is":"Weekly, three independent AI model families try to break our methodology; a chairman keeps only the objections at least two families agree on. We publish them — open objections to our own method, with status. Findings are hypotheses (candidates), not confirmed defects. Radical transparency: we'd rather you read our flaws here than discover them elsewhere.","n_objections":15,"n_new_this_week":15,"panel_model_families":6,"objections":[{"probe":"metodologia+selos","objection":"The scoring relies on undisclosed or proprietary data, risking inflated scores due to lack of independent verification.","severity":"high","suggested_fix":"Publish raw data, calculation methods, and allow third-party auditing to ensure transparency and accuracy.","our_status":"open — under review"},{"probe":"metodologia+selos","objection":"Proprietary ownership or undisclosed weighting formulas create conflicts of interest and risk manipulation for commercial benefit.","severity":"high","suggested_fix":"Transfer governance to a neutral consortium or open-source the methodology to ensure fairness and prevent manipulation.","our_status":"open — under review"},{"probe":"regulador (a persona-alvo)","objection":"Lack of proven historical performance or validation, with projected validation only by December 2026, making reliability unassessable.","severity":"high","suggested_fix":"Provide verified historical data from pilot projects or concrete performance metrics to demonstrate reliability.","our_status":"open — under review"},{"probe":"regulador (a persona-alvo)","objection":"No independent third-party validation for ledger integrity and timestamping processes.","severity":"high","suggested_fix":"Engage a reputable external auditor or certification body to verify the ledger and timestamping processes.","our_status":"open — under review"},{"probe":"diferencial (committed≠delivered + retirada de fila)","objection":"The verifiable ledger (hash + OpenTimestamps anchoring) can be easily copied—any blockchain-based index can adopt the same verification techniques, eliminating the 'verifiable honesty' status.","severity":"high","suggested_fix":"Launch a similar open-source index using the same hash anchoring but with cheaper and more transparent data collection, so users don't rely on proprietary datasets.","our_status":"open — under review"},{"probe":"diferencial (committed≠delivered + retirada de fila)","objection":"Lack of pre-revenue validation until 2026 creates skepticism, allowing competitors to establish credibility earlier.","severity":"high","suggested_fix":"Accelerate validation cycles or secure pilot agreements with key partners to demonstrate real-world accuracy before competitors launch.","our_status":"open — under review"},{"probe":"acurácia técnica de domínio","objection":"Treating 'committed capacity' as 'delivered capacity' ignores project withdrawals and feasibility drops, inflating the index.","severity":"high","suggested_fix":"Separate committed capacity from delivered capacity, apply historical withdrawal rates, and differentiate between queue positions and signed interconnection agreements.","our_status":"open — under review"},{"probe":"acurácia técnica de domínio","objection":"Relying on public EIA/FERC data for 'real-time' insights fails due to reporting lags and behind-the-meter invisibility.","severity":"high","suggested_fix":"Integrate ISO-level telemetry or utility-specific firm transmission data to capture real-time status and behind-the-meter assets.","our_status":"open — under review"},{"probe":"número público LIVE (regulador)","objection":"The 302.1 GW claim of 'executed interconnection agreements' is overstated because queue files may only show request status, not confirmed executed agreements.","severity":"high","suggested_fix":"Clarify that the 302.1 GW figure reflects projects at the interconnection-agreement stage in queues, not confirmed executed agreements.","our_status":"open — under review"},{"probe":"número público LIVE (regulador)","objection":"The ~26% figure is misleading because it combines incomplete data (NYISO status read from project stage, MISO's active list is nearly empty) and excludes MISO when recalculating, inflating the share.","severity":"high","suggested_fix":"Report verified executed agreement totals separately per ISO/RTO and calculate percentages only where data is complete; clearly state limitations for any aggregated percentages.","our_status":"open — under review"},{"probe":"metodologia+selos","objection":"OpenTimestamps anchoring proves data existence but does not guarantee accuracy or integrity of the underlying data.","severity":"medium","suggested_fix":"Combine timestamp anchoring with cryptographic proofs linking hashed data to verifiable raw inputs for stronger data integrity.","our_status":"open — under review"},{"probe":"diferencial (committed≠delivered + retirada de fila)","objection":"Proprietary energy and data center location data relies mostly on public sources (energy permits, infrastructure listings), so competitors can recreate it with industry-standard tooling.","severity":"medium","suggested_fix":"Develop an automated pipeline using web scraping/APIs to recreate infrastructure data, make it public, and integrate it into a competing index.","our_status":"open — under review"},{"probe":"distribuição/inevitabilidade","objection":"Reliance on proprietary data ownership creates skepticism about transparency and bias.","severity":"medium","suggested_fix":"Adopt open data standards or enable third-party audits to enhance transparency.","our_status":"open — under review"},{"probe":"distribuição/inevitabilidade","objection":"Regulatory uncertainty or lack of enforcement weakens the product's authority and distribution.","severity":"medium","suggested_fix":"Engage with regulators early to ensure compliance, legitimacy, and co-shape standards.","our_status":"open — under review"},{"probe":"acurácia técnica de domínio","objection":"Using OpenTimestamps as proof of data existence does not guarantee the accuracy of the underlying physical infrastructure.","severity":"medium","suggested_fix":"Clarify that OpenTimestamps ensures anti-tampering of the reporting timeline, not the physical validity of grid capacity, and anchor hashes to a public blockchain for verifiable audit.","our_status":"open — under review"}],"methodology_url":"/api/v1/regions/methodology"}