Regression discontinuity for platform policies (information systems)
A fork of the empirical template for thresholds set by platforms, such as rating cut-offs or eligibility rules: it adds a manipulation test at the cut-off and a bandwidth sensitivity check.
Where it sits
left: what it builds on · right: what builds on it · pale: exampleBy Noor Haddad (example)
How studies reach it
- Platform fee changes and app develope… → Regression discontinuity for platform…Example
- Rating cut-offs and seller entry on a… → Regression discontinuity for platform…Example
- Close elections, mayor turnover and a… → Regression discontinuity for platform…Example
- Fee cuts for small developers and pro… → Regression discontinuity for platform…Example
- Ranking rule changes and complementor… → Regression discontinuity for platform…Example
Disciplines it reaches
Solid: published studies. Light: examples.
Computed from the records on this site: what each study, template and specialist names as used, which study extends which, and who authored what. 5 studies in total.
- Input
- A research question, user- or item-level data with the running variable, and your literature
- Output
- A draft paper with RD plots, a replication package and a dossier
- At the end
- When any run ends, e2er builds the PDF, writes the audit trail and the structured export, and pushes to GitHub if you set that up.
Steps
Greyed steps do not run in the selected mode.
- 1 specialistsDesign, data, estimation and draftPlans the paper and dispatches specialists for the literature, data, identification strategy, econometric specification, analysis and drafting.
- 2 specialistsImprove until it stops getting betterFurther rounds of the strategist, revisiting design and analysis.
- 3 checkEstimation checkChecks the estimation against the specification declared before it ran. Halts the run on failure.
- 4 checkManipulation testTests for bunching of the running variable at the cut-off. Halts the run when the density jumps at the threshold.
- 5 checkBandwidth sensitivityRe-estimates at half and double the chosen bandwidth and records how far the estimate moves.
- 6 specialists
- 7 specialists, parallelPolishFive specialists polish formulas, numbers, institutional detail, equilibria and the bibliography.
- 8 reviewers, parallelReview panelNumbers and citations are checked first. Six reviewers (mechanism, technical, literature, data, identification, writing) then score the draft.
- 9 specialistsRevisionRevises the draft in response to the reviews, as a full revision and as targeted edits.
- 10 specialists
Technical details
Template id rd-platform-policy.
| Step | Id in the template file | Specialists |
|---|---|---|
| 1. Design, data, estimation and draft | initial | idea_developer, literature_scanner, data_architect, identification_strategist, econometrics_specialist, data_analyst, paper_drafter |
| 2. Improve until it stops getting better | iterative | |
| 3. Estimation check | estimation_gate | |
| 4. Manipulation test | manipulation_test | |
| 5. Bandwidth sensitivity | bandwidth_sensitivity | |
| 6. Self-critique | self_attack | self_attacker |
| 7. Polish | polish | polish_formula, polish_numerics, polish_institutions, polish_equilibria, polish_bibliography |
| 8. Review panel | review | mechanism_reviewer, technical_reviewer, literature_reviewer, data_reviewer, identification_reviewer, writing_reviewer |
| 9. Revision | revision | revisor, patch_revisor |
| 10. Replication package | replication | replication_packager |
At the end (finalize): compile, audit_export, github_push, structured_export. Modes: single_pass, iterative.
More
A fork of the empirical study template. It keeps every step and check of the original and adds the design-specific checks marked below. Skills it loads: Regression Discontinuity Design.
Description
Data model- Discipline
- Information systems
- Method family
- Empirical (quantitative)
- Design
- Regression discontinuity
- Research stage
- Research designData analysisDraftingReview
- Authors
- Noor Haddad (Methodology, Software)
- Usage
- not used in published research yet · Examples: 5 example studies
- Source
- Example
- Record
- template:rd-platform-policy · JSON
Solid tags are declared by the source or mapped from its terms; dashed tags are inferred by a published rule. Hover a tag for its provenance.
Versions and evaluations
PlannedNo versions yet.
Connectors this template can use
What a run of this template can reach outside your machine, and what each sends out.
Checks on this template
- ✓Output contracts · Every step produced the artifact it declared, in the declared form
Required of every template. - ✓Execution reliability · Analysis code ran and wrote a parseable, non-empty result
Required of every template. - ○Numbers · Every number in tables and text matches the output of executed code
Proposed. Proposed for the floor; runs log it but may not block on it. - ○Citations · Every reference resolves to an existing publication via OpenAlex, Semantic Scholar or Crossref
Proposed. Proposed for the floor; runs log it but may not block on it. - ○Verbatim passages · Every claim about a source points to a passage found word for word in that source
Proposed. Proposed for the floor; runs log it but may not block on it.
Runs of this template
No runs yet.
On e2er.org
Loading…
Discussion
Loading…