DOCUMENTATION. RECORDS. TIMELINE. EVIDENCE.PUBLIC RECORD / COMPLETE CONTEXT
PROJECT DRTETHE COMPLETE RECORD

Project DRTE / An evidence-first initiative

The Truth Lives in the Complete Record.

Preserving documents. Connecting timelines. Examining what the evidence establishes—and what it leaves unanswered.

Every document. Every fact. Every side. The whole record.

01 / About DRTE

Preserve.
Examine.
Understand.

Project DRTE exists to preserve documentation, records, timelines, and evidence so that facts can be examined in their complete context.

We begin with documents and make the path back to the source visible. We distinguish what a record states from what someone alleges, what we infer, and what remains unknown.

A source can point us toward a question. Independently obtained records are the foundation for publication. Readers should be able to check our work and reach their own informed conclusions.

Read our editorial method →

Editorial foundation: DRTE Instagram Build Kit, 2026-09-08, pp. 2–6; Source Intake and Verification Protocol v1.0, 2026-09-08, pp. 1–5.

02 / Start Here

Follow the paper trail.

READER ORIENTATION

01 — UNDERSTAND

Know what the label means.

A record, an allegation, and an opinion carry different weight. Our labels keep them distinct.

Read the fact labels →

02 — EXAMINE

Go back to the source.

Read the cited document and its limits. Check who issued it, when, and what is missing.

Visit the record library →

03 — PARTICIPATE

Ask for the record.

Identify the records you want, locate their custodian, and preserve the complete response.

Use the request starter →

03 / Methodology

Documentation. Records.
Timeline. Evidence.

Documentation

Preserve the source, issuer, date, context, and how it was obtained. Keep originals separate from public copies.

Records

Obtain records independently from a custodian or public portal. Compare source accounts against those records.

Timeline

Distinguish an event date from a filing, receipt, or publication date. Mark missing or uncertain dates explicitly.

Evidence

Label each claim. Test alternative explanations. State what the evidence supports and what it does not prove.

Before publication: review source independence, corroboration, context, privacy, redactions, and the right of reply. Allegations involving a named person require additional scrutiny; a label alone never clears a claim for publication.

Source verification and publication safeguards
  1. Require a case number, file number, or agency identifier. Obtain the underlying record independently.
  2. Record whether the document confirms, partly supports, contradicts, or says nothing about the source's account.
  3. Check gaps, source interests, consistency, secondhand information, and plausible alternative explanations.
  4. Before identifying a person, require supporting records, a second source or record, official or professional conduct of public interest, written questions with a reasonable reply deadline, and any counsel clearance required by the protocol. The final publication must pass the editorial checks and be reread on a later day. We do not direct readers to contact, confront, or pressure a person or office.
  5. Remove private-party identifiers, indirect identifying details, signatures, minors' information, and medical or financial details from public copies. Apply permanent redaction and remove metadata; a visual overlay is not secure redaction.
  6. Publish the reply or the dated response status accurately. A missing response, a delay, or an absent record does not by itself establish misconduct.

Source: Source Intake and Verification Protocol v1.0, 2026-09-08, §§2–5; editorial web adaptation of the Instagram Build Kit.

04 / Record Library

Case Files

PUBLIC INDEX

Published case files will bring the source documents, chronology, claim labels, responses, and corrections together in one place.

Awaiting publication

No case files published on this website yet.

The library opens when a file has completed verification, privacy review, and publication review. No case findings are presented in this first website release.

See what a file must pass before publication →
Each file: source / issuer / date / record identifierPlus: limits / right of reply / revision history

05 / Fact Labels

Keep the distinctions visible.

These are editorial explanations of DRTE's seven labels. A label tells you how to read a statement; it does not substitute for its supporting source.

01 / VERIFIED SUPPORT

Confirmed Evidence

A specific claim supported by verified evidence. Read the cited material and the exact scope of what was confirmed.

02 / PRIMARY SOURCE

Official Record

Material issued or maintained by a court, agency, or other official custodian. A filing may contain disputed allegations; its official status does not establish every assertion inside it.

03 / ATTRIBUTED REPORTING

Publicly Reported

A statement attributed to an identified public report. Attribution is visible; independent DRTE confirmation is not implied.

04 / REASONING

Inference

A reasoned interpretation of identified evidence. The supporting facts and the reasoning remain separate, and alternative explanations are considered.

05 / UNPROVEN CLAIM

Allegation

An attributed claim that has not been established as fact. Attribution and labeling do not remove the need for verification, context, and publication review.

06 / EDITORIAL JUDGMENT

Opinion

An expressly identified viewpoint or judgment. Any factual assertions supporting it still need their own sources.

07 / LIMIT OF THE RECORD

Not Established in Current Record

The materials reviewed do not establish the proposition. That does not establish its opposite or prove that no further evidence exists.

How source-verification ratings differ from fact labels

A — Record-confirmed: the record states it. B — Record-consistent: the record fits the account but does not state it; any published reasoning is labeled inference. C — Uncorroborated: not publishable as fact. D — Contradicted or unverifiable: log the result and stop that publication path.

These source-verification ratings supplement the seven public labels. All applicable publication safeguards still apply.

Sources: Instagram Build Kit, 2026-09-08, pp. 5–6; Source Intake and Verification Protocol v1.0, 2026-09-08, §2.

06 / Ask for the Record

A better question starts with a document.

Identify the custodian, describe existing records as precisely as possible, and use the agency's current submission instructions.

Keep your request, acknowledgment, tracking number, fee correspondence, and complete response together.

General information, not legal advice. Requirements and access depend on the jurisdiction and the records.

OPINION / EDITORIAL REQUEST STARTER

To the records custodian:

I request copies of the following existing records: [describe the records], for [date range].

Please provide electronic copies if available. Please advise me of estimated fees before processing.

Please send your response to [preferred contact method]. Thank you.

Replace the bracketed text before sending. This wording does not guarantee access, a fee waiver, or compliance with every agency's requirements.

Federal FOIA request guidance ↗ (opens in a new tab)

Arizona public-records guidance ↗ (opens in a new tab)

Download the plain-text starter ↓

07 / Submit Documents

A source shows us where to look.
The record is what we publish.

Have documents or a firsthand account that points to a verifiable record? Read the safeguards first. This website has no upload form and does not receive or store submissions.

Secure document intake is not open on this website yet. The receiving address and transfer instructions must be confirmed before documents can be sent. Do not send sensitive material through social comments or direct messages.

Before sending anything

  • Do not send sealed records, protective-order material, medical or financial records, anything involving a minor, or anything obtained unlawfully.
  • Keep your originals. Never send your only copy.
  • Do not post names, addresses, contact information, or private case details in public comments.
  • DRTE does not provide legal advice. Submission creates no relationship or obligation and does not guarantee publication.
  • Confidentiality cannot be promised absolutely, including in response to a court order. Consider legal advice before sending if that risk matters to you. Email privacy depends on the sender, recipient, devices, and delivery method.

Once the channel is confirmed

First ask for the current transfer instructions without attaching documents or identifying private parties. Use the checklist below only after a suitable channel is established.

SECURE CONTACT / PENDING CONFIRMATION

{{SECURE_EMAIL}}

Placeholder only. This is not a working address.

Source intake checklist — for a confirmed private channel

This is a preparation guide, not a form. Do not enter or send personal details on this page.

  1. Your name (for private intake), preferred contact method, permission for follow-up, and role: party, witness, family member, attorney, employee, or observer.
  2. Case number or agency file number, court/county/agency, and dates or date range. We cannot verify an account without a case or file number.
  3. Whether you were physically present or the account is secondhand. Describe what you personally saw or heard separately from what you concluded and why.
  4. Which documents you have and which exist but you do not have. Flag any sealed, protected, or minor-related issues without sending that material.
  5. Permission: background only (never published), publishable with source anonymous, or publishable with source named. Source identity defaults to anonymous unless you affirmatively choose named use; naming still requires review. Anonymous treatment is not a guarantee against identification.
  6. Acknowledge that DRTE may publish nothing, or reach an interpretation different from yours. Confirm that your account is true to the best of your knowledge.

Source: Source Intake and Verification Protocol v1.0, 2026-09-08, §§1–4. The website uses plain instructions in place of a data-collection form.

08 / Corrections Log

The record can change.
So can our account.

Corrections should identify the affected statement, explain what changed and why, cite the supporting record, and carry a dated entry linked to the original publication.

No correction entries are included in this initial website release. This is not a statement about the history of DRTE's other channels.

To propose a correction, prepare the page link, exact statement, proposed correction, and a public source or record identifier. Do not include sensitive documents in an initial message.

Contact and correction instructions →

Editorial policy / website v1.0.0. Future entries: publication link · original statement · correction · source · date · effect on conclusions.

09 / Contact

Bring the source.
Keep the context.

For general questions, corrections, or a right-of-reply request, begin with the public page or record reference and a short, nonsensitive description.

CONTACT CHANNEL / NOT YET CONFIGURED

{{SECURE_EMAIL}}

The address will appear here after confirmation. Until then, the linked DRTE social profiles below can be used for general, nonsensitive inquiries. They are not secure document-intake channels.

Read document-intake safeguards →

10 / Privacy

Read without being tracked by this site.

This website includes no analytics, advertising trackers, cookies, browser storage, third-party embeds, or submission forms. Fonts and the brand mark are served with the site. Reading and navigation work without JavaScript.

The hosting provider may process connection information such as IP addresses and standard access logs to deliver and protect the website. Any external site you choose to visit has its own privacy practices. Email or social messages are handled by those services, outside this website.

Private source records and intake ledgers must remain outside the public website. The site's decorative redaction bars are a visual motif, not a tool for redacting documents.