Methodology
AQ26 harvests primary observations first, applies quality controls and target-neutral screening, then executes transparent cross-source joins. Facilities are introduced only after discovery as possible context. Legacy Google Drive material is excluded unless the original source, date, authority, SHA-256, lineage, parser and scientific quality are validated.
How AQ26 works
Source-attribution caution
The automated site must not collapse these evidence classes into a single causal claim.
Evidence gates
- Source acquired
- Provenance recorded
- Parser validated
- Time alignment checked
- Monitor role checked
- Meteorology checked
- Comparator checked
- Reviewer challenge recorded
Matching discipline
Public records are linked to a target only by target-specific phrases or identifiers. Generic terms such as ERF, EfW, incinerator and energy recovery require a nearby target-specific anchor and are not enough on their own.
Public-safety rule
The public build excludes protected bundles, service-account keys, credentials, ZIP evidence packages and unredacted registers. The deployment guard fails if these appear in the public folder.
Forensic scientific evidence review
Inspect evidence coverage, freshness, source maturity, executed cross-references, uncertainty and explicit non-conclusions.
AI and model assurance
Review current deterministic execution, prohibited automated uses, evaluation gates and model provenance.
AQ26 Evidence Assurance Framework
Four controls govern every public release
VVIP is the internal technical shorthand. Public outputs use the full assurance language and never imply external approval or endorsement.
Requirements, source contracts, calculations, models, accessibility and publication rules are tested before release.
The live website and published social assets must match the exact reviewed evidence package and release receipt.
Secret leakage, unsupported claims, duplicate publication, unreviewed routes and evidence substitution are refused.
Sources, requests, transformations, model versions, artifacts, deployment and platform publication remain traceable.
Latest reviewed package timestamp: 2026-07-25T06:16:55+00:00. See sources, readiness and external review material.