Mineral Rights Retained Evidence Source-Scope Worksheet

Direct answer for mineral owners

Create one blank worksheet for one already-retained artifact and one capture event. Record bounded provenance, an already-available integrity reference, a controlled pointer, source-stated scope and limitations, unresolved fields, and an authorized-human handoff. Copy displayed wording exactly or mark it not stated or unresolved. Do not retrieve, interpret, compare, authenticate, or decide anything.

Key takeaways for mineral owners

• Use one worksheet ID for one already-retained artifact and one capture event.
• Copy source-stated scope and limitations exactly or mark them not stated or unresolved.
• Treat a SHA-256 reference as byte-change evidence only, not proof of authenticity or ownership.
• Keep real artifacts, captured values, and integrity digests in an authorized controlled record.
• Do not search, retrieve, compare a party, or infer a mineral, property, offer, or transaction scope.
• Stop at an authorized-human handoff without generating a proceed or rely-on decision.

Evidence-boundary stop. This blank worksheet describes one already-retained artifact and one capture event. It does not search, retrieve, open, download, authenticate, interpret, compare, submit, purchase, or decide anything. Keep real artifacts, captured values, and integrity digests in an authorized controlled record. MRX provides educational information and resources only and does not buy mineral rights.

Mineral rights retained evidence source scope is a narrow recordkeeping job. It preserves what one retained artifact says about its own scope and limitations, together with a controlled pointer and a limited byte-change reference when one already exists. It does not determine what the artifact proves.

That boundary matters because a filename, storage location, familiar source, or unchanged digest can look more conclusive than it is. The worksheet keeps those observations separate from authenticity, identity, authority, completeness, relevance, ownership, legal effect, valuation, offer quality, and transaction decisions.

Direct answer for mineral owners

Create one worksheet ID for one already-retained artifact and one capture event. Record the source title and URL, capture timestamp and timezone, source type, retained filename and format, already-available integrity reference, controlled evidence pointer, source-stated scope, source-stated limitation, reviewer role, unresolved fields, and authorized-human handoff.

Copy source-stated scope and limitations exactly as displayed. If the artifact does not state one, use not stated. If the wording is unreadable or its boundary needs qualified review, use unresolved. Do not replace a gap with an assumption.

Stop there. Do not retrieve another copy, open an account, search for a related file, compare a sender, infer what a property or mineral interest is, or decide whether anyone should rely on the artifact.

Start with one already-retained artifact

The worksheet begins after retention. An authorized reviewer must already have the artifact and the permitted descriptive information. This public template does not provide a route to fetch, download, order, scrape, or request anything.

Give the record a neutral identifier such as [source-scope worksheet ID]. Tie it to exactly one artifact and one capture event. Start a separate worksheet or version when any of these changes:

• the retained file or physical item;
• the capture timestamp or timezone;
• the source title or URL;
• the retained filename or format;
• the source-stated scope or limitation;
• the controlled evidence pointer; or
• the integrity reference being recorded.

Do not combine several files because they arrived together, have similar names, or appear in the same correspondence. Relationship analysis belongs in a separate authorized review.

Keep every reusable field blank

• Worksheet ID: [source-scope worksheet ID]
• Capture timestamp and timezone: [authorized capture time]
• Source title: [exact displayed title or not stated]
• Source URL: [controlled source URL or not applicable]
• Source type: [exact source-stated type or unresolved]
• Retained filename: [controlled record only]
• Retained format: [exact observed format]
• Integrity reference type: [already-available reference type or none]
• Integrity reference: [controlled record only]
• Controlled evidence pointer: [authorized locator]
• Source-stated scope: [exact displayed wording, not stated, or unresolved]
• Source-stated limitation: [exact displayed wording, not stated, or unresolved]
• Reviewer role: [authorized role, not a personal public identifier]
• Unresolved field: [field and bounded question]
• Authorized-human handoff: [role and neutral handoff state]

The bracketed phrases are labels, not example values. Do not add a real or fictional entity, person, address, instrument, tract, well, mineral interest, owner, buyer, offer, transaction, filename, digest, account, or contact detail to the reusable public worksheet.

Use the federal-records material only as an analogy

The National Archives Records Basics page distinguishes several categories in the federal-government context. It discusses source records, working files, information-system inputs, system content, and outputs. Those distinctions illustrate why a record should identify what kind of retained artifact it describes instead of treating every copy, input, or output as interchangeable.

That page governs federal records-management concepts. This worksheet does not import a federal record definition, preservation duty, disposition schedule, legal status, or agency rule into a private mineral-rights file. The source-type field is descriptive. If the retained artifact does not state a type, record unresolved rather than applying a federal label to it.

Likewise, do not relabel source-stated scope as mineral scope, property scope, title scope, ownership scope, valuation scope, offer scope, deal scope, or transaction scope. Preserve the artifact’s wording without expanding it.

Treat an integrity reference as byte-change evidence only

NIST’s FIPS 180-4 Secure Hash Standard specifies hash algorithms that generate message digests. NIST describes those digests as a way to detect whether messages changed after the digests were generated.

That is the permitted boundary here. If an authorized controlled record already contains a SHA-256 digest, the worksheet may identify its type and controlled location. It may support a limited comparison of bytes against that reference in a separate authorized process.

A digest does not prove:

• who created or sent the artifact;
• where it originated;
• whether it is authentic or authoritative;
• whether its contents are accurate or complete;
• whether it concerns a particular person, property, interest, or transaction;
• whether it has legal effect;
• whether it is relevant to a decision; or
• whether anyone owns or may act on anything it describes.

Do not generate a new digest through this public worksheet. Do not publish a real digest. Record only an already-available reference in the authorized controlled record.

Copy stated scope and limitations without interpretation

Preserve exact displayed wording, including qualifiers, dates, page labels, and limiting phrases. Do not normalize a narrow statement into a broader one. Do not use surrounding correspondence, a likely filename, a neighboring page, a search snippet, or memory to fill a missing field.

Use one of three bounded entries:

• exact displayed wording when the source states the field clearly;
• not stated when the artifact does not display it; or
• unresolved when readability or meaning requires an authorized qualified reviewer.

The worksheet may record that a field exists, is not stated, or is unresolved. It may not decide whether the source is sufficient, trustworthy, complete, current, official, relevant, compliant, or suitable for reliance.

Keep this job separate from adjacent records

The valuation evidence-cutoff log organizes a defined valuation evidence set and cutoff date. This worksheet does not create a valuation evidence set or determine inclusion.

The offer version-control and deadline register separates written versions and deadlines. This worksheet covers only one artifact and does not compare versions, track a deadline, or establish which copy controls.

The offer correspondence index organizes communication items. This worksheet does not identify a correspondent, connect messages, or compare a sender, signer, caller, buyer, owner, operator, or transaction party.

Use the document redaction checklist before any separately authorized sharing step. This worksheet itself does not share or transmit an artifact.

Preserve the controlled evidence boundary

The public template contains labels and citations only. Real artifacts and completed values belong in an authorized system with appropriate access controls. The controlled record may retain the worksheet ID, artifact pointer, captured fields, integrity-reference location, unresolved questions, reviewer role, and handoff state.

Do not put credentials, account details, private contact data, title instruments, offers, tax information, legal communications, completed digests, or transaction documents into a public example. Do not create fictional values that could be mistaken for evidence.

Stop at an authorized-human handoff

Close the worksheet with one neutral state: recorded for authorized review, held for source clarification, or not used. Name the unresolved field and the next authorized role. Do not use authentic, verified, complete, owner confirmed, safe to rely on, safe to proceed, or another conclusion.

An authorized human may decide that retrieval, source verification, legal review, title review, identity comparison, valuation work, or transaction review is needed. Each later job requires its own purpose, authority, sources, privacy controls, and evidence. It is outside this worksheet.

This source-scope worksheet records bounded descriptive evidence for one already-retained artifact. It does not provide legal, tax, title, land, records-management, appraisal, valuation, engineering, compliance, investment, offer, or transaction advice.

Frequently asked questions

Does this worksheet retrieve or open the artifact?

No. It begins only after an authorized reviewer already has the retained artifact and the permitted descriptive fields. It does not search, log in, fetch, download, scrape, order, submit, file, purchase, contact anyone, or write to an external system.

Does a matching SHA-256 value prove that an artifact is authentic?

No. A matching digest can support a limited statement that the compared bytes did not change relative to the referenced digest. It does not prove provenance, authorship, authenticity, identity, accuracy, completeness, legal effect, relevance, authority, or ownership.

Can the worksheet combine several related files?

No. Use one worksheet for one already-retained artifact and one capture event. A second file, capture, format, source location, or materially changed displayed scope requires a separate worksheet ID or version.

What if the artifact does not state its scope or limitation?

Record not stated or unresolved. Do not infer a mineral, property, valuation, offer, ownership, legal, or transaction scope from the filename, surrounding correspondence, source location, or expected use.

Does completing the worksheet determine whether anyone should rely on the artifact?

No. The worksheet records bounded descriptive evidence and stops at an authorized-human handoff. It does not generate a trust, rely-on, accept, reject, contact, share, submit, file, purchase, or transaction decision.

Sources reviewed for this article

• National Archives, Records Basics (accessed 2026-08-26)
• NIST, FIPS 180-4 Secure Hash Standard (accessed 2026-08-26)