What PASO publishes
- Public dossiers and public risk logic.
- Public source links, source limitations and evidence status.
- Correction pathways and right-of-reply records.
- Public JSON, maps, timelines, release notes and file hashes.
This notice explains how PASO protects people, separates public evidence from protected material, welcomes correction, records pressure attempts, and uses a task-bound need-to-know structure that makes infiltration, doxxing, bribery and coercion low-reward. It also adds the resilience layer: no master key, multi-person approval, release hashes, public integrity status and evidence-poisoning safeguards.
Evidence corrects the record. Pressure becomes part of the record. PASO is transparent in method, not transparent in vulnerability.
PASO welcomes corrections, counter-evidence, official replies and rights of reply. It does not accept intimidation, bribery, doxxing, smear campaigns, fraudulent manipulation, platform degradation or coercion as a correction method.
Any person, institution, company, public authority, media outlet or organization named or affected by a public PASO record may request correction through the public correction pathway. Verified corrections may lead PASO to amend a record, update a score, publish a correction note, add a right of reply or issue a public clarification.
Corrections must be based on verifiable evidence: public documents, official records, court decisions, contracts, budgets, audit reports, transcripts, dated public statements, academic sources, archived pages or other source-linked material.
Attempts to pressure, intimidate, bribe, dox, threaten, smear, fraudulently manipulate, degrade, hack, suppress, censor or otherwise interfere with PASO, its contributors, reviewers, sources, partners, hosting channels, public records or correction process will not improve a score. Such conduct may be recorded as an accountability-avoidance, information-pressure, evidence-obstruction, retaliation or public-interest suppression signal.
Where necessary, PASO may publish a sanitized record of pressure attempts without exposing protected contributors, witnesses, survivors, sensitive locations, private communications or internal security procedures.
| Field | Public record may include |
|---|---|
| Date | When the incident or pressure attempt occurred. |
| Actor category | State body, company, official, media node, law firm, anonymous network or unknown actor. |
| Type | Legal intimidation, smear campaign, doxxing attempt, platform pressure, evidence obstruction, bribery attempt or cyber/degradation attempt. |
| Public evidence | Only public or safely publishable evidence, never protected identities or raw confidential material. |
| Correction opportunity | Whether the actor was offered a public correction/right-of-reply route. |
PASO is not a conventional club or broad membership organization. It is a decentralized, redundant, task-bound public-intelligence workflow. Participants do not normally know one another personally. Participation does not grant social access, network access, evidence access or identity access.
A contributor may be invited to perform one defined task, on one defined record, during one defined period, with only the minimum information required to complete that task. That person does not gain knowledge of other contributors, other cases, protected sources, witness identities, internal evidence holdings, reviewer chains, legal routes or future actions.
Each ordinary task is designed to be low-criticality on its own. A participant may verify one public source, review one paragraph, check one quote, classify one claim, translate one public excerpt or test one link. When the task ends, access ends.
Reviewers normally do not know protected sources. Protected sources do not know reviewers. For sensitive matters, tasks are split: one reviewer checks sources, another legal wording, another risk score, another safety/publication boundary.
PASO does not operate through open folders or unrestricted evidence dumps. Files are converted into role-specific packets: public-source packet, redacted review packet, legal annex packet, technical publication packet, correction packet or press packet.
No single person should control evidence custody, publication, domain/hosting, correction decisions, protected source identities, legal submissions, final scoring, takedown response or mirror archives.
An infiltrator should discover that there is no exposed social map, no general membership list, no open evidence room and no route from one small task to the full architecture.
| Attempt | Why it fails by design |
|---|---|
| Pressure one member | Ordinary participants do not know protected sources, other members, unrelated cases or legal annexes. |
| Join to map PASO | Participants are task-bound and do not receive contributor directories or reviewer-chain maps. |
| Ask for raw evidence | No ordinary task includes raw protected evidence or unrestricted files. |
| Sabotage one assignment | Small tasks are low-criticality and can be checked through double-blind or split-blind review. |
| Threaten publication staff | Public publishers receive approved public material only and do not control protected evidence. |
| Level | Access | Typical users |
|---|---|---|
| L0 Public | Public site, public JSON, public PDFs, public correction pages. | Everyone. |
| L1 Task public | One public-source task, translation, link check or quote review. | Temporary contributors. |
| L2 Redacted review | Claim matrix, redacted summary, uncertainty note, public-source packet. | Double-blind reviewers. |
| L3 Protected evidence | Restricted evidence without full identity where possible. | Evidence custodians / authorized legal handlers. |
| L4 Identity-bound | Witness identity, exact sensitive location, protected legal annex. | Only authorized handler, only at time of need. |
No person should hold the full map, full archive or full release authority. No individual controls identity, evidence, publication, scoring, legal submission and infrastructure at the same time.
Sensitive actions should require 2-of-3 or 3-of-5 approval depending on severity: opening protected evidence, removing a record, changing a major score after pressure, publishing a high-risk dossier, submitting a protected annex, responding to legal threats, or changing domain/mirror settings.
Every public release should have a version number, date, changelog, public file hashes, correction notes, source additions and a ZIP archive. Silent alteration becomes detectable.
PASO may maintain a public status block showing current version, last verified release, public hash, known takedown pressure, known legal intimidation and correction-channel status.
Task packets, review links, correction roles and protected legal packets should expire after the task, deadline, decision or submission. Trust does not create permanent access.
No single protected submission becomes a public claim. Suspicious, rushed, sensational or unverifiable submissions are treated as possible poisoning attempts until corroborated.
| Role | Safe answer |
|---|---|
| Public contributor | I do not have access to protected sources, evidence vaults, witness identities, reviewer chains, legal annexes or unrelated cases. PASO is deliberately structured that way. Please use the public correction pathway. |
| Reviewer | I only reviewed a redacted task packet. I do not know the source, submitter, witness identity or full case chain. |
| Technical maintainer | I maintain public static files only. I do not have access to protected evidence or source identities. |
| Public spokesperson | I can discuss only approved public material. I do not have protected source identities or confidential annexes. |