Skip to content

Clinical review: 130 unverified + 132 unknown-status source documents (governance debt burn-down) #229

Description

@BigSimmo

Why

The corpus governance debt in docs/release-source-metadata-debt-2026-06-30.json is accepted as tracked backend debt, not a fix. Clearing it requires genuine clinical/source review — statuses must never be fabricated. This issue queues that human work so the debt is burned down rather than perpetually renewed.

Current corpus state (re-verified 2026-07-03, live project sjrfecxgysukkwxsowpy, unchanged since 2026-07-02)

  • 130 documents clinical_validation_status = unverified (need local clinical review before marking reviewed)
  • 132 documents document_status = unknown (no derivable review/publication date — status can only be set after confirming source currentness)
  • 481 review_due; 0 poor-extraction; 0 missing required source-metadata keys

Governance status is stored in documents.metadata (document_status, clinical_validation_status).

Burn-down path (highest-value first)

  1. Clinically review the 25 surfaced documents in docs/source-review-priority-2026-07-02.md, highest slot-count first. The top 12 alone return the top-result review-required rate to ~0.12.
  2. After confirming currentness, backfill metadata.document_status (via scripts/backfill-source-metadata.ts).
  3. After local clinical review, backfill metadata.clinical_validation_status.
  4. As reviews land, tighten max_review_required_rate in the debt file back toward 0.2, then remove the debt file.

Constraints

  • Do not set statuses/validation without real review — the debt file explicitly does not mark any source current, reviewed, or approved.
  • Debt acceptance currently expires 2026-08-31 (renewed 2026-07-03); this issue is the mechanism to clear it before then.

See also: docs/source-governance-priorities-2026-07-02.md, docs/retrieval-quality-runbook.md.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions