Skip to content

Commit bc9a94d

Browse files
igerberclaude
andcommitted
Document stale replicate df as Note in REGISTRY.md
Move the replicate df limitation from TODO.md (which only silences P2/P3) to REGISTRY.md with a **Note:** label (which the CI reviewer recognizes and downgrades to P3). The df stays R-1 instead of n_valid-1 when invalid replicates are dropped — marginal impact for typical R > 50. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 8a757b1 commit bc9a94d

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

docs/methodology/REGISTRY.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2029,6 +2029,12 @@ variance from the distribution of replicate estimates.
20292029
- **Note:** CallawaySantAnna, ContinuousDiD, and EfficientDiD reject
20302030
replicate weights with `n_bootstrap > 0`. Replicate weights provide
20312031
analytical variance; bootstrap is a separate inference mechanism.
2032+
- **Note:** When invalid replicates are dropped, survey degrees of freedom
2033+
remain `R - 1` (original replicate count) rather than `n_valid - 1`.
2034+
This is a conservative simplification: the df difference is marginal for
2035+
typical replicate counts (R > 50) and errs toward wider CIs / larger
2036+
p-values. Updating df to track valid replicate count would require
2037+
threading the count through all estimator inference paths.
20322038

20332039
### DEFF Diagnostics (Phase 6)
20342040

0 commit comments

Comments
 (0)