Skip to content

Open Questions Register

Auto-generated from feature docs. Run ./docs/scripts/generate-open-questions.sh to update.

Note: Most existing feature docs do not yet use the standardised OQ-N format for open questions. As feature specs are updated, their open questions should use the format - [ ] **OQ-N**: Question text → Context to be captured by the generator.

Summary: 0 open | 0 resolved | 0 features with standardised questions

Known Open Questions (Manual Inventory)

The following open questions exist in feature specs but haven't yet been converted to the standardised OQ format. This section will be replaced by auto-generated content as specs are updated.

Annotation Domain

  • FEAT-001: What happens to in-flight annotations during a question version transition?
  • FEAT-001: Should question set versions support cross-project sharing?
  • FEAT-002: Virtual scroll implementation — CDK vs custom for 100+ questions?
  • FEAT-004: How are field mapping conflicts resolved during annotation import?

Screening Domain

  • FEAT-007: Should screening profiles support versioning, or only clone-to-revise?
  • FEAT-007: What happens to in-progress decisions when a stage's profile is changed?
  • FEAT-008: How does stage filtering handle studies added mid-review?
  • FEAT-010: Should stage settings support templates for common configurations?

Reconciliation Domain

  • FEAT-005: What granularity for permission groups — per-stage or per-project?
  • FEAT-006: Should reconcilers see annotator identifiers or only "Annotator A/B"?
  • FEAT-006: How is reconciliation handled for stages with 3+ annotators?

Export & Reporting Domain

  • FEAT-011: How should the PRISMA dual-column layout handle custom source types?
  • FEAT-013: What agreement metrics to include in enhanced export (beyond Cohen's Kappa)?

This register will auto-populate as feature specs adopt the standardised - [ ] **OQ-N**: ... format.