Governance Review Status

Governance Review Status

Definition

Closed enumeration capturing the governance review state of a content item. Distinct from content review (/review per CLAUDE.md) — this is the freshness/ownership review tracked by /api/governance/review. Items move through pending → approved (or reverted / changes_requested); time-based escalation to review_overdue when the cadence elapses.

Synonyms / Acronyms

None.

Baseline values

key	label	provenance
pending	Pending	core
approved	Approved	core
reverted	Reverted	core
changes_requested	Changes Requested	core
review_overdue	Review Overdue	core

Relationships

• record_lifecycle.governance_review_status — text, no DB CHECK on the new home (the pre-M1a content_items_governance_review_status_check did not carry over — see Notes). Re-homed off content_items.governance_review_status at ID-131 M1a (20260628190000_id131_record_lifecycle_facet); content_items itself was DROPPED at ID-131 M6.
• Review/Governance axis spans BOTH owner kinds (D7) — unlike freshness. governance_review_status (with governance_review_due, governance_reviewer_id, verified_at, verified_by, content_owner_id) is on record_lifecycle’s review/governance axis, which applies to owner_kind IN ('source_document', 'q_a_pair') — NOT source-document-only like CV 06/08’s freshness axis. Both source documents and Q&A pairs get a governance review status.
• record_lifecycle.next_review_date, record_lifecycle.review_cadence_days — adjacent administrative metadata, but part of the source-document-only freshness axis (contrast the review-status fields above, which span both kinds).
• verification_history table — per-event review audit trail; not re-verified against the record_lifecycle re-home by this subtask.
• Bound to freshness (CV 08): an expired item may auto-transition to review_overdue (source-document-only, since freshness is source-document-only).

Consumers

• app/api/governance/review/route.ts — governance review endpoint (distinct from /review content-quality flow per CLAUDE.md “Content review vs governance review”).
• lib/mcp/tools/governance.ts, lib/mcp/formatters/governance.ts — MCP governance tooling.
• components/settings/governance-section.tsx — governance config UI.
• lib/dashboard.ts, lib/dashboard-signals.ts, lib/notifications.ts, lib/attention.ts — surfaces review signals on the dashboard.
• Scheduled jobs that escalate items to review_overdue.

Notes

• Distinct workflow from the /review content-quality flow (per CLAUDE.md gotcha).
• CHECK enum did not carry over the re-home. content_items_governance_review_status_check enforced this 5-value set on content_items; record_lifecycle.governance_review_status (ID-131 M1a) has no equivalent CHECK. The vocabulary is still closed by convention/documentation, not by the DB — an ID-131-successor hardening candidate, not raised as a blocking flag here.