CONTENT GOVERNANCE

Reviewer workspace

View guidance library
HUMAN REVIEW REQUIRED

Build the evidence chain first.

Capture the governing source, inspect the extraction evidence, then draft the narrow operational interpretation it supports. This workflow cannot publish a compliance conclusion.

  1. 1 Register authoritative source
  2. 2 Process and index evidence
  3. 3 Route for SME, Legal, and MA review
01
SOURCE RECORD

Register a governing source

Use an official link and capture the effective source version. Commentary can be recorded for discovery, but it cannot support a published conclusion.

Creates a versioned source record and audit event.

02
EVIDENCE EXTRACTION + NVIDIA INDEXING

Process every page, then create review candidates

Native extraction and OCR preserve page evidence. NVIDIA is used only to tag jurisdiction, topic, and candidate questions with citations; it cannot publish a rule.

Register a source first.

Evidence processing is always tied to a versioned source record.

03
LLM-INDEXED CANDIDATES

Evidence-backed candidates awaiting review

These are discovery records, not answers. A reviewer must confirm the source evidence and draft any operational interpretation.

No indexed candidates yet. Configure NVIDIA_API_KEY, then process a source PDF.

04
COUNTRY RULE · DRAFT ONLY

Draft a cited operational interpretation

A source locator is mandatory. The draft’s citation, conditions, and history are stored together and cannot be silently published.

Register a source first.

Rule drafts need a current authoritative source version.

RECENT DRAFTS

Governance review and controlled release

No draft rules yet. Saved drafts will appear here for routing.

Three distinct approval roles are required. The Worker verifies the release key and D1 release gates before publishing.