Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Use one lifecycle-complete contract for completion funnels
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
A multi-step completion funnel needs one canonical lifecycle contract. Define the eligible denominator, durable opened and started milestones, per-step reached, attempted, completed, and failed outcomes, and one true user-task-completed milestone. Do not use an intermediate submission event or a parent entity’s terminal status as a proxy unless the product contract makes them equivalent. Keep fraud or verification outcome separate from whether the user finished the requested work. This applies to flows with optional or configured steps, retries, security gates, and post-submit work. It is a contract method, not a claim about current production rates.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review