[Atlas/feat] open_question artifact_type — schema, populate, per-field views done

← Open Questions as Ranked Artifacts
Quest: Open Questions as Ranked Artifacts (b307ad54-a95). Acceptance: - artifact_type='open_question' with metadata schema: {question_text, field_tag, sub_field, importance_elo, tractability_score, potential_impact_score, evidence_summary, status (open|partially_answered|resolved), source_kind (wiki|gap|hypothesis|debate|manual), source_id}. - Auto-populate pass: parse 18,447 wiki pages for 'Open Questions' / 'Unanswered' / 'Future directions' sections (markdown header search) → emit open_question artifacts with source_kind=wiki and provenance link back to wiki_page artifact_id. Idempotent on (source_kind, source_id, question_hash). - Auto-populate from gaps: any gap with status='proposed' and quality_score>=7 → emit open_question. - Per-field route: /questions/ ranked by importance_elo desc; /api/questions?field=...&sort=...&limit=... - Initial Elo: 1500 baseline; tournament path comes in sibling task. - Spec: docs/planning/specs/open_question_artifact.md. Why now: ranked open questions per field is the single most operator-requested view. Wiki pages already have the raw material.

Completion Notes

Auto-completed by supervisor after successful deploy to main

Git Commits (2)

[Atlas] Add open_question artifact type, wiki backfill, and API routes [task:b2d85e76-51f3-4edf-959b-3b3bde8529de]2026-04-25
[Atlas] Work log: update spec with completed work log [task:b2d85e76-51f3-4edf-959b-3b3bde8529de]2026-04-25

Sibling Tasks in Quest (Open Questions as Ranked Artifacts) ↗

Task Dependencies

↓ Referenced by (downstream)