Separate post-deploy activity from the post-deploy-created cohort

A post-deploy funnel should report timestamp-bounded activity and a cohort anchored on entities created after deployment separately. Activity shows what the new runtime processed, including older entities; a created-after-deploy cohort shows progression of newly created entities. Do not divide one by the other as a conversion rate unless membership aligns.

Build the cohort from authoritative creation timestamps and stable IDs, join child entities and persisted stages to it, and use observability events for runtime activity. Deduplicate retries by stable identity and separate business outcomes from application exceptions.

Counts remain a moving snapshot, late ingestion can shift logs, and business status is not proof of UI delivery. Without authoritative creation timestamps, label the result event activity only.