# Stage Retroactive Population Provenance

Separate newly visible calculated history from a newly occurred deal movement.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Stage property enable date,record movement history,export versions and calculated timestamps.

## Workflow
1. Compare movement timestamps with property visibility dates.
2. Use documented retroactive population from existing data.
3. Do not turn first appearance in an export into a new stage transition.
4. Return history versus export timing without altering records.

## Output contract
record | stage | movement_time | property_enable | first_export_seen | new_event_unproved

## Fictional acceptance test
Fictional stage calculations are enabledOct 15 and show anOct 1 entry. TheOct 15 export did not prove the deal entered the stageOct 15. Missing original history remains unverified.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://knowledge.hubspot.com/properties/stage-calculated-properties

Checked October 15, 2026. Oct15 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude45, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia115, cashflowforecasting13. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.