Skip to content

Create a source-passage locator receipt

Create a source-passage locator receipt: A locator receipt identifies the passage and surrounding unit precisely.

Guides

What should a source-passage locator receipt make inspectable?

Consider a long discussion supporting a narrow tray-carrying claim where reviewers repeatedly land on the wrong reply. A locator receipt identifies the passage and surrounding unit precisely. It reduces friction without inventing source identifiers, reconstructing unavailable language or treating a convenient summary as an independently verified replacement for original public evidence and the context needed to interpret its reported task.

Artifact schema and decision check
Output columns: draft_claim; original_url; source_unit; available_locator; exact_phrase; context_boundary; inspection_state.
Decision check: Ask another reviewer to try the reference and record actual inspection state. A plausible URL is not successful review.
01 / Guides

Identify the concrete review task

Name the claim and source unit needed. Distinguish parent post from the relevant reply. A discussion title alone is insufficient when support depends on one exchange with its own conditions, attribution or unresolved reference to a product component that the writer elsewhere describes with ambiguous wording rather than an explicit name.

02 / Guides

Inspect admissible supporting material

Include original URL, available reference and an exact locator phrase. Exclude guessed timestamps or identifiers. Montage results may provide usable locations, but use only available references and mark missing precision rather than fabricate a deep link or claim the product supplies a field the reviewer never actually received or verified.

03 / Guides

Assemble the decision artifact

Record surrounding language distinguishing the passage from quotations elsewhere. Preserve whether it reports the writer's experience or another account. A snippet may guide navigation without establishing full context or independently verifying the event; keeping those roles separate prevents an easily located fragment from appearing more evidentially complete than the underlying exchange actually is.

04 / Guides

Check the inference and action boundary

Ask another reviewer to try the reference and record actual inspection state. A plausible URL is not successful review. Automated repetition of the phrase cannot show the original was inspected under necessary conditions or resolve missing context simply because it sounds like the desired passage and the response includes an attractive citation marker.

05 / Guides

Deliver the bounded review state

Deliver locator, boundary and access state together. Keep reuse permission separate from reference utility. The receipt makes support easier to check, not certified true, permanently accessible or representative of all sources in the larger file. One successful location check does not establish independent verification of every other claim or all its downstream uses.

Keep the boundaries clear.

  • One successful location check does not establish independent verification of every other claim or all its downstream uses.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage