theranosfilm / independent analysis

Participation / sources and corrections

Contribute evidence. Keep the history.

Make one claim precise, show its source, explain its limits—and leave room for correction.

Edited by the Theranos Film project · Briar assisted · . Editorial draft; not independently fact-checked. About this independent project · Corrections and review history.

A correction should leave a trace

Proposals stay proposals. A separate editorial record names the reviewed JSON digest, decision, reasons, sources and the GitHub discussion/revision. That is an accountable record—not proof that the contributor is a particular real-world person, or that acceptance makes a claim unquestionably true.

Two ways to contribute

  1. Open a source-backed evidence issue on GitHub. GitHub records the submitting account and discussion; you decide what to submit.
  2. Prepare one JSON proposal below and add it in a pull request under data/contributions/. Read the contribution rules and the schema.

No account or token is collected by this website. Nothing in the form is sent automatically, stored by this page or fetched from a submitted source URL. GitHub submission is a separate, explicit action.

Public proposals and decision history

Names/profile links below are recorded labels, not independently authenticated identities. Editorial decisions are version-controlled maintainer records. Acceptance is an editorial state, not a legal finding. An automated decision is labelled as automated.

Submitted as proposed

Film at Lincoln Center lists You Can See Everything with a runtime of 174 minutes and directors Nathan Fielder and Lance Oppenheim.

Contributor label: Project research — Briar assisted · self_reported

Recorded submission time: 2026-11-21T12:37:34Z

A listing does not authenticate an individual screening edition, every on-screen credit or footage provenance. Seed proposal authored for this project, not an independently accepted public contribution.

Canonical submission SHA256: 4cc3b4443c6a00660201e38c6f102b38e0089f2776cb9e4f6bc1d04c5266a9d2

Read the submitted JSON · Git revision history

Source · Director and runtime fields: The festival listing states these credits and runtime.

No editorial decision recorded. This is not an accepted finding.

How decisions and disputes work

  1. A proposal is validated as data, not accepted as fact. Public GitHub account history supplies attribution; profile fields alone do not.
  2. A maintainer records a separate decision using review.schema.json, the exact proposal hash and a source revision/discussion. Self-review under the same recorded profile is rejected. This check cannot prove distinct real people.
  3. Keep source support, counterevidence and reasons visible. Correct an existing record with a new proposal referencing supersedes; append a decision rather than overwriting history.
  4. Schema checks do not prevent a deceptive person inventing a different profile. Maintainers must check the actual GitHub provenance and evidence before publication; there is no automatic issue-to-accepted-fact importer.
  5. Privacy takes priority over preserving an exposed person's data. Report exposure without repeating the sensitive content; do not put secrets into public issues.