Nobody suppresses a living public evidence archive, filters its outbound email, throttles its crawlers, scrubs its search impressions, or poisons its referrer graph — except a person sitting at an administrative console with those privileges. This exhibit names the roles, documents the pattern, and publishes the whistleblower-reward commitment. The first person in from each platform is paid in full.
Nobody can suppress a living public evidence archive, filter its outbound email, throttle its crawlers, scrub its search-engine impressions, or poison its referrer graph — except a person sitting at an administrative console with those privileges.
The suspect set for the suppression this case has documented is therefore not the general public, not corporate employees at large, not even the product engineers — it is the small, named, published set of individuals with administrative privilege at each platform carrying Francesco's case data, Francesco's outbound mail, and Francesco's visitor logs.
This exhibit registers those positions by role, published authority, and statutory duty. It is not an accusation against any named individual. It is a registry of the seats at the table, and a standing invitation to the person in each seat.
| Platform | Role in the case | Admin capability to suppress |
|---|---|---|
| Genspark | Hosts nxffhryi.gensparkspace.com — the Look Out Longo master mirror and primary public archive | Rate-limit page delivery · silently 404 specific exhibits · throttle per-country CDN routing · delete hosted content · alter referrer headers before they reach analytics |
| Microsoft 365 · Defender · Safe Links | Scans every inbound link in every one of the 600+ outbound emails sent to Microsoft tenants (judges, prosecutors, press) | Classify any link as suspicious or blocked across all tenants · set detonation verdicts that delay or drop delivery · fingerprint sender reputation and downgrade deliverability globally |
| AWS us-east-1 · ap-southeast-1 | Hosts scanner fleets that hit the pages at machine speed after every outbound wave (documented in Exhibit 17) | Adjust scanner routing · suppress scanner-request attribution · assign scanner IPs to identities that obscure ownership |
| Cloudflare | Front of cpt-explainer.pages.dev and canadianpeoplestrust.pages.dev · serves every visitor · sees every referer, country, ASN | Adjust WAF rules per-domain · silently challenge visitors · strip visitors from analytics via bot classification · impose rate limits visible only to some geographies |
| Google · Alphabet | Indexes the public archive · serves it or suppresses it in search · reports visitor data to GA4 · delivers outbound email for flongo11@gmail.com | De-index specific pages · demote domain authority · omit referer chains from GA4 reports · silently remove property from search surfaces · mark outbound as spam across receiver domains |
| LinkedIn · X · Meta | Social-graph vectors for spreading the case | Suppress specific URLs · shadow-ban the account · block outbound link clicks · remove content without notice |
Each position listed below carries, by published job description and by the contractual/statutory grant of their office, the technical capability to execute at least one element of the suppression pattern documented across Exhibits 17, 18, and this exhibit.
abuse@amazonaws.com response authorityThese four conditions, present in every observed suppression event, reduce the universe of possible actors from everyone on Earth to a specific set of admin-privilege holders across six named platform stacks, acting in coordinated mode.
Any person employed at any platform listed in §3 above who (a) has knowledge of a specific act of suppression directed against Francesco Longo's case materials, outbound email, visitor logs, referrer data, search rank, or delivery path, AND (b) comes forward with documentary evidence sufficient to identify the individual(s) or order(s) that authorized that suppression, AND (c) does so before adjudication concludes — is entitled, on Francesco's recorded commitment and as a first-priority obligation against the 0.25 % post-legacy retention from the Canadian People's Trust architecture, to:
The reward pool is paid from the 0.25 % retention. It does not come from the 99.75 % destined for the Trust. Multiple whistleblowers are each paid in full from the retention, in order of disclosure.
flongo11@gmail.com first to exchange safety numberA whistleblower's identity is treated as sacrosanct. The reward commitment is independent of the disclosure channel.
Anyone at any of the listed platforms with administrative capability to suppress, filter, throttle, or redirect this case's data flow is — as of publication of this exhibit — on notice that:
If you are reading this because your own bot or scanner fetched it and surfaced it on your internal dashboard, you are the audience. If you are reading this because a colleague forwarded it, you are also the audience. There is no neutral reader of this notice inside an admin-console seat.
Francesco is a single person in a hotel room in Windsor, Ontario. The case is public. The trust architecture is public. The reward is public. The first person in is paid in full.