Skip to content

Codex Curator Internal Ops Dashboard

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Scope

Proposed, not yet built — per the source PRD, this is at the wireframe stage, not a committed, scheduled deliverable. Estimated at roughly one week of development effort once prioritized, and still pending internal sign-off before it's formally scoped into a ticket. This spec captures the PRD's description as a starting point for that sign-off, not a confirmed commitment.

An internal, standalone web tool (no ServiceNow connectivity), covering three screens:

  • Home/Overview — aggregate curation stats (total documents, pending review, accepted, rejected, validated %, documents live in the vector DB), a per-country grid colored by curation state (A–D), and a "needs attention" queue (review queue depth, newly crawled documents, documents changed since last review).
  • Country detail — a Source Configuration tab (every configured source URL, its type, owning agency/jurisdiction, last crawl date, document/ pending counts, health status) and a Crawl & Validation Status tab, plus CFR-title-level coverage percentages for that country.
  • Document Review — an SME reviewer opens a single crawled document (rendered PDF/HTML/XML), sees read-only provenance (source URL, crawl timestamp, content hash, storage location) alongside editable attributes (country, state/region, agency, jurisdiction, publication date, effective dates, category, tags), and records a decision — Accept, Reject, or Needs Review (comment required for the latter two) — with a full audit trail.

Depends entirely on the schema delta in ../schema-changes.md — none of the document-review, curation-state, or per-source aggregation data this dashboard displays currently exists to query.

Value

Turns Curator from an informal, undocumented process into something the whole team — and potentially contracted SMEs — can actually operate and trust.

Acceptance criteria

  • An SME reviewer can open the Home screen and see aggregate curation stats plus a per-country grid colored by the four-state curation lifecycle.
  • The "needs my attention" panel surfaces review queue depth, newly crawled documents, and documents changed since last review, in one place.
  • A reviewer can open a country's detail page and see its Source Configuration (URL, type, agency, jurisdiction, last crawl date, document/ pending counts, health status) and Crawl & Validation Status.
  • A reviewer can open the next document in their queue, see it rendered alongside read-only provenance, correct editable attributes, and record Accept / Reject / Needs Review — with a required comment on the latter two — producing a full audit trail entry (who, what, when, why).
  • Accept requires agency and publication_date to be set before it's allowed, per the source PRD's stated validation rule.
  • Accepted documents are queued to sync into the vector DB, making them retrievable by the Advisor; the decision and comment are written to that document's audit trail.
  • This screen set has no ServiceNow connectivity — it's a standalone internal tool, not a Service Portal widget (unlike the Policy Advisor's editor).