Public Rights Field Guide · web edition

AI, Evidence & Witnesses

AI provenance, later legal process, preservation, privacy, status-first witness and whistleblower routing, and independent recollection.

Edition
v0.7-rc1 companion
Source date
Status
review copy
Maintainer
Brandon N.Gallegos

PUBLICATION INFORMATION

About this reviewer draft

Useful information, careful records, independent decisions.

This companion develops the Public Rights Field Guide’s AI, evidence, and witness workstreams. It accompanies the v0.7-rc1 Core reviewer draft. It is not a replacement for the Core, an official agency form, or a completed catalogue of legal protections.

The guide provides general legal information and organization tools. It does not decide your rights, select a claim or strategy, calculate your deadline, or provide legal representation. A template needs checking against the facts, the current rules, and the receiving process. For a personal legal assessment, consult a qualified lawyer.

EDITION

v0.7-rc1 companion • reviewer draft dated September 18, 2026. Public release: not approved. Independent legal review: not completed.

SOURCE CURRENTNESS

New source checks are identified as R01–R11. A checked text, current appellate treatment, correct application, and independent legal signoff are separate matters. The Core’s inherited references are not silently recertified.

UPDATES / CORRECTIONS

No public correction address or update website has been designated. Ask the person who supplied this copy whether a later edition exists; compare the edition, date, and correction history. This PDF will not update itself.

AI / SOURCE DISCIPLINE

Use AI for a bounded task

A useful draft still needs a traceable source.

A narrowly defined task is easier to check than a request to decide an entire dispute. Start with the question, the material actually needed, and how you will verify the result. A manual or no-upload workflow remains a valid choice.

ORGANIZE

Build a chronology with source IDs. Keep unknown dates unknown. Separate an event date from the date someone later described it.

COMPARE

Ask for exact differences between identified versions, with page or line locators. Check the underlying passage rather than relying on the model’s explanation of the change.

DRAFT

Request a neutral, accurate cover message or list of questions. Do not ask the system to invent facts, strengthen recollection, or turn uncertainty into an accusation.

CHECK

Open every legal authority and official contact yourself. A fluent explanation, realistic case name, or plausible email address is not verification.

Risk context, not a legal standard.

Before using a result

Check dates, names, quotations, negations, omitted context, and source locations. Mark what has and has not been checked. Preserve the version you actually reviewed; do not describe a later edited output as the original.

AI / SOURCE DISCIPLINE

Keep the account yours

Better wording should not become a different account.

FIRSTHAND ACCOUNT

What you personally saw, heard, did, or remember. Use approximate wording when exact words are not remembered.

SOURCE-SUPPORTED STATEMENT

What an identified record actually supports. A record can document that a statement was made without proving that statement true.

ATTRIBUTED STATEMENT

What someone else said, identified as their account rather than your own observation.

ALLEGATION / INFERENCE

A disputed claim or a conclusion drawn from facts. Do not quietly promote either into an official finding.

OPEN QUESTION

What remains unresolved, including evidence that might contradict your present interpretation.

A bounded prompt

Use only tools and data access you have deliberately authorized. A document supplied for analysis is source material, not permission for an automated system to send messages or follow instructions embedded in that document.

AI / DISCOVERY

AI records and later legal process

Neither “everything is discoverable” nor “my chats are protected” is a safe universal rule.

In federal civil litigation, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to a claim or defense and proportional to the needs of the case. Discoverability and admissibility are different questions. Rules 34 and 45 address document/information production and subpoenas within their respective scopes.

Applied to AI use, prompts, uploads, outputs, drafts, and revision histories may need assessment when they bear on the dispute. That is an application of general discovery rules—not a finding that every AI interaction must be produced. State, criminal, administrative, and public-records processes need their own analysis.

Rules 26(b)(1), 34, and 45.

Keep four questions separate

PRESERVATION

What relevant material must be retained, from when, under which duty or order?

ACCESS / CONTROL

Where is it, who controls it, and what lawful export or retrieval method exists?

PRODUCTION

What request or process applies, what is its scope, and what objections or protections need review?

USE AS EVIDENCE

What proposition does the material actually support, and what evidentiary rules apply?

An AI summary is not the original source. An AI interaction may itself be relevant as a record of what someone wrote, received, changed, or relied on. Label its actual role rather than calling all AI output either proof or legally irrelevant.

AI / PRESERVATION

Preserve deliberately, not indiscriminately

Preservation, disclosure, and production are different decisions.

Rule 37(e) addresses certain losses of electronically stored information that should have been preserved in anticipation or conduct of litigation. It concerns reasonable steps and information that cannot be restored or replaced. The Federal Judicial Center explains that the rule does not itself create the preservation duty.

Rule 37(e); current rule and historical official explanation.

IDENTIFY

List potentially relevant systems and record types: messages, attachments, native media, exports, drafts, AI interactions, and delivery records. Include information that complicates the account.

RETAIN LAWFULLY

Keep relevant material you lawfully possess or control. Do not defeat access controls, take unrelated workplace files, or upload private records to make a more impressive packet.

NOTICE AUTO-DELETION

Record known expiry, overwrite, account-closure, and disappearing-message risks. When a duty or order may apply, obtain prompt, scope-specific guidance rather than improvising a destructive change.

VERIFY THE COPY

Keep native originals when available. Check that exports open and contain the expected attachments, timestamps, and context. A screenshot or flattened summary may omit information.

RECORD LIMITATIONS

Note missing material, unsuccessful exports, incomplete histories, and transformations. Do not recreate absent data as though it were an original.

AI / PRIVACY

Privacy settings are not legal status

A handling choice is not a privilege determination.

Do not assume that a “private,” “temporary,” “local,” “enterprise,” or “no training” label answers who can access a record, how long it is retained, or whether it is legally protected. Check the actual service, account configuration, sharing, integrations, administrator access, retention, export, and legal-process terms before a consequential upload.

This draft does not certify any product’s privacy behavior. A no-upload workflow avoids that upload; it does not make existing records immune from applicable legal process.

Privilege and work product

Attorney-client privilege and work-product protection are distinct. Rule 26(b)(3) addresses qualifying material prepared in anticipation of litigation or for trial by or for a party or its representative; it is not limited to papers personally written by a lawyer. Whether particular AI material qualifies or a disclosure affects protection requires separate analysis.

Rule 26(b)(3); Rules of Evidence 501–502. No case-specific conclusion.

BEFORE UPLOADING

Ask whether the material includes private third-party information, possible privileged communications, restricted records, or information beyond the task.

BEFORE SHARING

Check recipient, need, authority, appropriate channel, attachments, filenames, hidden information, and applicable disclosure requirements.

AFTER A POSSIBLE MISTAKE

Preserve an accurate incident record and seek prompt, qualified guidance. Do not assume deleting a message cures disclosure or that every accidental disclosure necessarily waives protection.

WITNESS / STATUS ROUTING

Start with the person’s actual role

One person can occupy several roles at once.

Record the role at the time of the activity and at the time of the alleged response. Use “unknown” when employment, contracting, institutional control, or authority is unclear. The following are research branches, not coverage determinations.

FEDERAL EMPLOYEE / APPLICANT

Identify the employing agency, position, personnel action, disclosure or other activity, and the relevant OSC/MSPB route. Do not assume every federal position or every subsection uses the same process.

NM STATE / LOCAL PUBLIC EMPLOYEE

Identify the actual public employer and employee relationship. Examine the New Mexico Whistleblower Protection Act and other potentially relevant frameworks separately.

PRIVATE-SECTOR EMPLOYEE

Identify what was reported: discrimination, safety, fraud, wages, or another subject. Do not infer a single all-purpose protection for every report of workplace wrongdoing.

CONTRACTOR / AGENT

Distinguish the contracting entity, a contractor’s employee, and an agent. Identify the contract, funding source, and conduct before selecting candidate statutes.

HEALTHCARE EMPLOYEE / PROFESSIONAL

Separate patient-care, emergency-care, safety, billing, licensure, employment, and reporting-duty questions. Role and subject matter matter.

PUBLIC-UNIVERSITY EMPLOYEE

Identify the actual employer, duties, speech or testimony, and employee/student dual status. Public employment is not a complete First Amendment analysis.

WITNESS / STATUS ROUTING

Reporting is not one legal status

A complaint, a witness account, and a protected activity are different questions.

STUDENT

Record institution, program, activity, and any employee role. Examine the relevant education and other statutory frameworks; do not substitute an employment test.

PATIENT

Identify the care setting, record or grievance process, and relevant rights. Patient status should not be substituted for a hospital-personnel protection.

ORDINARY / LIKELY WITNESS

What was observed? What proceeding exists or may be anticipated? Who knew what, and what response or attempted interference occurred?

COMPLAINANT

Identify the underlying complaint and process. The word “complaint” alone does not establish the protected-activity element of every law.

VICTIM

Separate ordinary usage, any statute-defined status, assistance services, procedural rights, and potential remedies.

PERSON ASSISTING ANOTHER

Record the assistance and any consent or authority. Helping with information is not the same as authority to represent another person or release their records.

REPORTING POSSIBLE FEDERAL CRIME

Identify the information, recipient, possible offense, and any required federal connection. A report is not an adjudication or a promise of prosecution.

TESTIFYING IN A COURT / ADMINISTRATIVE PROCEEDING

Record the tribunal, whether testimony was required or voluntary, its subject, the person’s duties, and applicable orders. Do not treat all testimony rules as interchangeable.

WITNESS / PROTECTION CARDS

What a protection card must answer

The name of a law is only the start.

WHO IS PROTECTED

Person, employment or other relationship, institution, jurisdiction, dates, and exclusions.

PROTECTED ACTIVITY

The actual disclosure, opposition, participation, assistance, refusal, or testimony—not just a label.

REQUIRED BELIEF / NEXUS

Any reasonable-belief, good-faith, subject-matter, recipient, funding, proceeding, or federal-offense requirement.

PROHIBITED RESPONSE

The framework’s actual action, threat, interference, or other prohibited conduct.

CAUSATION / KNOWLEDGE

Who knew of the activity, the relevant causal standard, burdens, defenses, and competing explanations.

FORUM

Agency, tribunal, court, or government enforcement route; correct respondent and legal vehicle.

DEADLINE / PREREQUISITE

Independent clock, trigger, notice, exhaustion, election, filing, and service questions. Do not borrow a period from a neighboring claim.

REMEDY

What relief the route authorizes, who can obtain it, and what limits or defenses apply.

SOURCE

Current operative text, pinpoint support, controlling treatment, and scoped review dates.

LIMITS

What is not established, excluded, uncertain, contested, or not researched.

WITNESS / PILOT CARD

Federal personnel: a bounded pilot

5 U.S.C. § 2302(b)(8) and (b)(9) are distinct starting points—not a universal employee remedy.

WHO / ACTIVITY

First check OSC’s coverage page. Its overview describes § 2302(b)(8) disclosures involving a reasonable belief in specified wrongdoing categories, and separately describes § 2302(b)(9) complaint, assistance, cooperation, and refusal activity.

BELIEF / RESPONSE

For the disclosure route, the overview identifies violation of law/rule/regulation, gross mismanagement, gross waste, abuse of authority, or substantial and specific danger to public health or safety. It discusses taking, failing to take, or threatening personnel action.

KNOWLEDGE / CAUSATION

The overview’s whistleblowing discussion identifies official knowledge and contribution to personnel action. Do not copy that description across all subsection (b)(9) activities, forum routes, or procedural postures.

Agency-guidance-level pilot. Full statute and controlling treatment remain open.

FORUM

OSC’s wrongdoing-disclosure function and its prohibited-personnel-practice complaint process are different. The official complaint page is the filing starting point—not proof that an individual matter has been filed or accepted.

Official routes inspected; no submission performed.

DEADLINE / PREREQUISITE

Open review: OSC process, MSPB jurisdiction, direct appeal versus individual-right-of-action route, exhaustion, election, mixed matters, and all applicable clocks.

REMEDY

Open review: the route’s corrective or other relief, burdens, defenses, and limits. No individual entitlement is stated.

WITNESS / NM RESEARCH BOUNDARY

New Mexico: do not combine the routes

Public employment, civil rights, workplace safety, and witness law need separate source sets.

PUBLIC-EMPLOYMENT RESEARCH BRANCH

NMSA 1978 §§ 10-16C-1 through -6: verify current official codification, definitions, protected activities, belief standards, response, causation, forum, prerequisites, remedies, and controlling appellate treatment.

This draft does not reproduce an old bill as current Whistleblower Protection Act text or carry forward an unverified personal-grievance/public-benefit test. The federal-rights dataset is a research lead, not authority that closes these gaps.

WHO / ACTIVITY / NEXUS

For an eventual NM card, establish the public employer and employee relationship, the actual activity, and the applicable statutory branch. All are open until source-linked review is complete.

RESPONSE / CAUSATION / FORUM

Identify the alleged action, knowledge, governing causal test, defendant, and cause of action. An institution’s name or public funding alone does not finish the analysis.

CLOCK / REMEDY / LIMITS

Do not publish a deadline or damages promise copied from an older summary. Check the operative rule, its trigger, prerequisites, defenses, and relevant cases.

One separately checked safety-route warning

New Mexico Environment Department’s employee page distinguishes workplace-safety complaints from discrimination complaints and states that discrimination complaints must be filed within 30 days of the discriminatory action. That statement concerns its safety-and-health route—not every NM retaliation claim.

Official agency page checked; no individual deadline calculated.

WITNESS / RESEARCH MAP

Candidate frameworks to investigate

A research map, not an assertion that a listed protection applies.

PUBLIC-EMPLOYEE SPEECH

Pickering / Garcetti / Lane and controlling Tenth Circuit cases: actual duties, citizen speech, public concern, balancing, causation, testimony, academic speech, and remedies.

FALSE CLAIMS ACT

31 U.S.C. § 3730(h): employee/contractor/agent scope, protected efforts, knowledge and causation, defendants, forum, limitation, and relief. Keep retaliation distinct from qui tam filing and seal questions.

EMTALA

42 U.S.C. § 1395dd(i): specified hospital personnel, activity, hospital relationship, remedy interactions, forum, and clocks. Do not assume a patient has the same personnel protection.

DISABILITY / CIVIL RIGHTS

42 U.S.C. § 12203; applicable Title VI, Title IX, § 504, and employment frameworks: coverage, opposition versus participation, assistance, retaliation versus interference, remedies, and separate procedures.

OSHA-ADMINISTERED STATUTES

Identify the specific statute, industry, employer, activity, federal/state-plan allocation, and short filing clock. “OSHA whistleblower” is not one universal claim.

FEDERAL WITNESS / INFORMANT

18 U.S.C. §§ 1512–1513: subsection-specific conduct, intent, official-proceeding or federal-offense connection, knowledge, and enforcement. Do not infer a personal civil action from a criminal provision.

OTHER STATE / CONTRACTOR / PROFESSIONAL ROUTES

Applicable NM witness, public-record/evidence, Human Rights Act, labor, healthcare, and professional-reporting protections; 41 U.S.C. § 4712 and 10 U.S.C. § 4701 where facts warrant research.

WITNESS / RECOLLECTION

Protect independent recollection

One master account for your reporting effort does not mean one account for every witness.

When contact is lawful and appropriate, begin with an open invitation to describe what the person independently remembers. Avoid feeding details, demanding agreement, rehearsing a preferred answer, or offering a benefit for a particular account. A person should be able to say “I do not know” or “I did not see that.”

Keep the original account and later corrections distinct. Record when and how the account was obtained, who was present, and what documents, other accounts, or AI-generated material had been shown. Do not call a later reconstruction contemporaneous.

Rule 612. Application to a particular preparation document requires legal review.

A no-contact or other order, representation, the person’s role, safety, and the forum’s procedures may require a different approach. This page is not permission to conduct an interview or share testimony in disregard of those limits.

Official publication description checked; no prevalence or causal claim made.

WITNESS / DISCLOSURE

A consistent account; deliberate disclosure

Tailor the cover message—not the underlying facts.

For a reporting effort, keep one versioned master account and a stable evidence index. Derive shorter cover messages for different recipients. Keep uncertainties and material corrections consistent across versions; preserve the exact statement and attachments actually sent.

PUBLIC

Material deliberately prepared for unrestricted circulation. Review third-party identification and context before publication.

PUBLIC WITH REDACTIONS

A clearly marked derivative. Keep the lawful original separately and a record of what was removed and why.

RECIPIENT-LIMITED

Material limited to a defined, verified recipient and purpose. Confirm the process and whether the recipient may share it further.

ATTORNEY / REGULATOR-ONLY HANDLING

A working disclosure tier, not a legal privilege or assurance of confidentiality. Verify authority, need, accepted channel, and legal obligations.

An auditable send record

Keep the exact submitted version, attachment list, recipient, official route, date/time/time zone, receipt or reference number, delivery result, bounce/error, and correction history. A sent message, automated acknowledgment, accepted filing, and accepted representation are different events.

These are practical organization suggestions. They do not authorize withholding required material, ignoring a subpoena, copying restricted files, or treating a voluntary public-sharing checklist as a discovery response.

WORKING TOOLS

AI work and source record

Working tool • complete only what you know; check the applicable process.

An AI-assisted transformation or draft matters enough to keep a traceable record.

ai-provenance-record-template · working template

ai-provenance-record-template

/header>
Record ID: [ ]
Task and scope: [ ]
Date/time/time zone: [ ]
Tool/model/version as displayed, if known: [ ]
Input source IDs and lawful working-copy locations: [ ]
What was uploaded or connected: [ ]
Prompt/output or available export location: [ ]
Human edits and checked source locations: [ ]
Unverified statements or known omissions: [ ]
Final reviewed/sent version ID: [ ]
Preservation instruction, if any, and who confirmed scope: [ ]

BEFORE SHARING

This is usually a private working record. Do not paste sensitive source content merely to complete the index. Check any applicable preservation or disclosure requirements.

KEEP

Relevant available originals and actual exports. Do not invent a missing history or overwrite the reviewed version.

WORKING TOOLS

Protection and independent-route record

Working tool • complete only what you know; check the applicable process.

You need to organize the questions for a specific possible protection.

protection-routing-record-template · working template

protection-routing-record-template

/header>
Person’s role(s), institution, jurisdiction, dates: [ ]
Candidate protection / exact provision: [ ]
Who is protected and exclusions: [ ]
Actual activity and required belief/nexus: [ ]
Alleged prohibited response: [ ]
Knowledge, causation, competing explanations: [ ]
Forum / respondent / legal vehicle: [ ]
Independent deadline, trigger, prerequisite: [unverified / source]
Potential remedy and limitations: [ ]
Primary authority, pinpoint, version, date checked: [ ]
Controlling-case review and unresolved questions: [ ]

BEFORE SHARING

Use a separate record for each framework. Mark unknown and not researched honestly. Obtain qualified help for an urgent clock.

KEEP

The source and version underlying each statement; corrections without erasing earlier versions.

WORKING TOOLS

Disclosure and exact-delivery record

Working tool • complete only what you know; check the applicable process.

Preparing or documenting a consequential voluntary submission.

disclosure-delivery-record-template · working template

disclosure-delivery-record-template

/header>
Purpose / requested action: [ ]
Master statement ID / version: [ ]
Recipient / role / official route checked on: [ ]
Required form or submission instructions: [ ]
Disclosure tier and authority/consent questions: [ ]
Attachment IDs, redactions, context checks: [ ]
Exact submitted version and sent attachment list: [ ]
Sent date/time/time zone: [ ]
Receipt / reference / acknowledgment: [ ]
Bounce / error / failed upload / alternative used: [ ]
Correction version and recipient notice, if any: [ ]
Separate deadlines still needing confirmation: [ ]

BEFORE SHARING

Check recipient, content, sensitive data, authority, required process, and independent clocks. Do not send merely because the record is filled in.

KEEP

The actual sent version, native delivery information, receipts, errors, and material corrections.

WORKING TOOLS

Independent-account source record

Working tool • complete only what you know; check the applicable process.

Documenting provenance of an account obtained lawfully and appropriately.

independent-account-provenance-template · working template

independent-account-provenance-template

/header>
Account/source ID: [ ]
Date/time/time zone and method: [ ]
Who initiated the exchange; who was present: [ ]
Person’s role and firsthand/secondhand basis: [ ]
Original account location; exact or approximate wording: [ ]
Questions asked, if recorded: [ ]
Materials/accounts/AI output shown beforehand: [ ]
Uncertainty, things not observed, missing context: [ ]
Later correction: date, source, and separate version: [ ]
Contact, consent, safety, representation/order concerns: [ ]

BEFORE SHARING

Do not populate this from guesses. Keep identifying/contact details outside public or AI-uploaded copies when not needed and authorized.

KEEP

The independent original, how it was obtained, disclosed transformations, and later corrections separately.

SOURCE LEDGER

Source checks for this draft

Checked September 18, 2026 • scope matters as much as the date.

R01 · source

Federal Rules of Civil Procedure

Version
Official rules, December 1, 2025 pamphlet
Scope
Rules 26(b)(1), 26(b)(3), 26(b)(5), 26(c), 34, 37(e), and 45; scoped text review.
Limits
Federal civil procedure only. No individual discovery, privilege, preservation, or deadline determination.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R02 · source

Federal Rules of Evidence

Version
Official rules pamphlet
Scope
Rules 501–502 and 612; scoped text review.
Limits
Rule 612 has conditions, a court role, and a criminal-case qualification. No universal AI-disclosure rule.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R03 · source

Failure to preserve electronically stored information

Version
Federal Judicial Center, December 1, 2015
Scope
Official educational explanation of the 2015 Rule 37(e) amendment.
Limits
Historical explanatory material, checked against the current rule; not a new source of preservation duty.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R04 · source

Generative Artificial Intelligence Profile

Version
NIST AI 600-1, July 2024
Scope
Confabulation, data privacy, and information-integrity risk descriptions, especially § 2.2.
Limits
Voluntary risk-management context. Not a current product benchmark or legal rule.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R05 · source

Prohibited Personnel Practices: Overview

Version
U.S. Office of Special Counsel, official guidance
Scope
Whistleblower retaliation and other retaliation sections.
Limits
Guidance, not a complete statutory or controlling-case treatment review.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R06 · source

Who can file a prohibited personnel practices complaint?

Version
U.S. Office of Special Counsel, official guidance
Scope
Coverage and jurisdiction cautions.
Limits
Position, employing agency, and exclusions require their own check.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

SOURCE LEDGER

Source checks for this draft

Checked September 18, 2026 • scope matters as much as the date.

R07 · source

How to file a prohibited personnel practices complaint

Version
U.S. Office of Special Counsel, official instructions
Scope
Official filing starting point, not tested submission.
Limits
No form was submitted. Delivery, acceptance, and timeliness were not established.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R08 · source

Disclosure of Wrongdoing: Overview

Version
U.S. Office of Special Counsel, official guidance
Scope
Wrongdoing-disclosure function, distinct from a retaliation complaint.
Limits
No assumption that use of one OSC channel completes every other process.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R09 · source

Resources for Employees

Version
New Mexico Environment Department, official guidance
Scope
Safety complaints distinguished from discrimination complaints; published 30-day discrimination-complaint statement.
Limits
This is not the NM Whistleblower Protection Act. Statutory scope, trigger, procedure, and exceptions need separate verification.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R10 · source

Eyewitness Evidence: A Guide for Law Enforcement

Version
National Institute of Justice, October 1999; NCJ 178240
Scope
Official publication description: collecting, recording, and preserving eyewitness evidence.
Limits
Law-enforcement practice context, not an experiment or a universal mandate for private persons.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

R11 · source

Current Rules of Practice & Procedure

Version
Administrative Office of the U.S. Courts
Scope
Official starting point for federal national rules.
Limits
A national-rules page does not replace local rules, standing orders, or case-specific orders.
Checked
2026-09-18
Review state
scoped-source-check; not publication approval

Open source

RELEASE REVIEW

What remains before public release

A usable reviewer copy is not an approved public edition.

LEGAL COVERAGE

Complete current official codification, controlling-case treatment, defendants, vehicles, prerequisites, remedies, and independent clocks for every active legal proposition and template instruction.

CONTACTS / UPDATES

Designate a stable correction/update route. Reverify official contacts and submission instructions; do not imply delivery or acceptance from a successful webpage fetch.

DOCUMENT QA

Inspect the final native Core, tools, and supplement at full resolution, in grayscale, with text selection, links/bookmarks, actual viewers, and assistive technology. A tagged-PDF indicator is not accessibility certification.

PRIVACY / PACKAGE

Check author metadata, local paths, hidden information, attachments, and public build inputs. Exclude private case, contact, student, medical, and correspondence datasets.

INDEPENDENT REVIEW

Obtain appropriately scoped independent legal/editorial review before presenting high-consequence explanations as publication-ready. Record what the reviewer did and did not assess.

The source ledger and working tools are part of the draft, not proof of legal compliance. Readers retain their own decisions. The project’s job is to make sources, options, uncertainties, and limits easier to see.

Back to the Public Rights Field Guide library