Publishing principles
Editorial methodology and publication standards
Who creates and maintains the content
David Medeiros is the archive maintainer, the author of identified first-person reports and commentary, and the requester or recipient associated with many preserved records. When a source supplies a different author, agency, sender, recipient, or creator, the page should identify that source role separately. A byline or schema author field must not imply that the archive created an underlying government or third-party document.
Background and first-person context are available on the David Medeiros profile and About this archive page.
Source and evidence labels
Primary or original record
A document, filing, communication, export, photograph, recording, or dataset preserved from its identified source. Publication proves that the archive possesses and serves the identified copy; it does not automatically prove every statement inside it.
Technical verification
Filename, byte size, SHA-256 digest, and delivery path checks establish bit-level integrity for the published file covered by the manifest. They do not establish legal truth, motive, identity, or completeness of the underlying event.
Archive summary
A human- or automation-assisted description created to help readers find and understand a source. Summaries must point back to the source and must not be presented as adjudicated findings.
Personal testimony or allegation
A statement attributed to its identified author or filing. Inclusion records that the statement was made; it does not convert the statement into a court or agency finding.
Adjudicated or official finding
A conclusion should be described this way only when the cited final order, judgment, or formal agency disposition supports that characterization.
How automation is used
Automation assists with inventory, parsing, deduplication, route generation, hashing, metadata drafting, link checks, sitemap generation, and issue detection. Automated output is not treated as independent corroboration. Material descriptions, identities, legal characterizations, and completeness claims require source review.
Named people and organizations
Inclusion means a name or organization appears in a preserved source or contextual record. It is not a finding of misconduct. Name-targeted pages should become indexable only after identity, public-interest purpose, role, source references, and potentially disputed statements are reviewed.
Corrections and right of reply
Factual correction requests and source-supported replies are reviewed under the public corrections policy. A response may be published, linked, summarized, or declined with an explanation. Source records and the correction history should remain distinguishable.
Read the corrections processSearch and AI boundary
Structured data, sitemaps, HTML text, manifests, captions, transcripts, and descriptive links improve machine access. They do not guarantee indexing, ranking, citation, retention, factual agreement, or inclusion in any AI system.
Review requirements before publication
- • Confirm that the file or statement has an identifiable source and that the public page links to it.
- • Separate source text, archive summary, personal testimony, allegation, legal theory, and official finding.
- • Avoid inferring intent, identity, guilt, or causation from a filename, missing record, or automated name match.
- • Check privacy, health, contact, witness, authentication, copyright, and redaction concerns.
- • Record material corrections without silently rewriting the historical source.
- • Describe technical completeness and external indexing as measured states, never as guarantees.