Original inquiry sources

An inquiry’s source label is editable CRM information. Its retained source is an immutable record of the material that created the inquiry, or evidence deliberately attached later. Editing a contact, renaming a form, or changing the source label does not rewrite that evidence.

Open a lead’s Original inquiry source section, then Review retained form, Radar and forwarded-email provenance. The source library shows 20 records at a time; follow Next 20 for older records. Sources remain private to the business. Current full workspace members can read them; contractors, shared-wedding participants and anonymous links cannot. Reads and Radar conversion recheck current named membership after waiting for domain locks.

What is retained

• Public inquiry form: the exact submission and publication identifiers, original title, publication revision, accepted-answer checksum and publication verification state. Open the source to read the original questions and answers. A personal questionnaire does not create acquisition provenance.
• Radar: the original captured adapter, normalized public URL, title, author, snippet and supplied publication date, plus the operator who converted it into an inquiry. The public page may later change. A captured signal does not verify the author’s identity, contact details or consent.
• Reviewed forwarded email: the original encrypted capture and immutable accepted review, including corrected fields, asserted marketplace, duplicate decision and named operator. Manual originals remain labeled operator supplied. Provider-retrieved originals additionally retain their exact verified receipt, receiving-address generation and provider authentication observations, separately from the unverified marketplace assertion. The provider routing check compares signed and retrieved destination fields; it is not independent proof of the SMTP envelope. Quoted headers and passing authentication do not establish customer identity or consent. Neither path activates selected-version routing or marketplace APIs.

Accepted provider sources remain valid after their receiving address is renamed, rotated or disabled, or new receiving is paused. Current named access is still required to read them. Their original operator approval, provider observations and hashes are preserved; an address change does not rewrite old source evidence.

Every source has a SHA-256 verification record and an explicit relationship. Original acquisition identifies the source of one actual new inquiry. Additional evidence links a later reviewed capture without changing the original inquiry or claiming that evidence created it. An inquiry can have only one original acquisition source.

Example: renamed form, unchanged answers

Inez submits “Portraits in the garden,” selecting an outdoor meeting point. Later, the business changes its public title and travel question. The retained source still links to Inez’s original publication and accepted answers. An exact browser retry returns that accepted submission; it does not create another inquiry, source or automation event.

New public submissions create provenance in the same transaction as their lead. New Radar conversions create one lead, original source and established lead-created event. Clicking convert again returns the existing inquiry. Existing form/Radar automation behavior is preserved; source creation itself introduces no new enrollment, messages or consent.

Historical records, merges and recovery

Older accepted submissions and already-converted Radar signals keep their original behavior. Replaying them does not backfill an inferred source. An old publication without a saved publication checksum is labeled Legacy publication without a retained publication hash; new source capture additionally retains the observed definition checksum, without presenting that as historic publisher verification.

Merging or archiving a lead keeps evidence on its original record. Open the linked original to inspect it. The retained source is never silently moved to the continuing record. Referenced original evidence and source records cannot be hard-deleted or edited through this feature. If evidence fails verification, the reader stops and asks for support review; it does not substitute a current draft or reconstructed source. Retain backups and original records while investigating.

Project attribution is a separate explicit choice. Another project for the same client does not automatically inherit a source. Use the project’s attribution review to connect retained evidence with invoice principal reporting. Source history alone is not collected cash, verified advertising attribution or recognized accounting revenue.

This development increment retains accepted provenance and its originals. It does not offer a purge or erasure workflow for referenced records. A coordinated retention, deletion and support policy remains an activation requirement before operating live external email capture.