source_scope is separate from review_statusCurrentness warnings stay visibleWebsite acquisition requires admin reviewPrivate scopes are not global by defaultSource automation review is draft-only
Dashboard
Source-library overview
Load admin data to view source counts.
Website sources are usually guidance, procedure, operational context, forms, notices, or contact information unless an admin explicitly classifies otherwise.
Unreviewed feedback, correction artifacts, private preferences, matter uploads, and session captures do not control future answers until reviewed and approved.
User Management
Firm users
Email
Name
Role
Status
Load admin data to view users.
Firms
Firm directory
Load admin data to view firm details.
Login/Auth Audit
Auth events and deterministic checks
Suspicious-pattern summaries will appear here.
Time
Type
Email
Result
Reason
IP
Load admin data to view auth events.
Source Library
Source list and filters
Title
Review
Scope
Type
Authority
Currentness
Acquisition
Load admin data to view sources.
Source Review Queue
Human approval and promotion controls
Only admin/review-authorized users should use these controls. Promotion and currentness approval are scaffolded until dedicated backend workflow steps are added.
Website Acquisition
Controlled website-source intake
Website acquisition status will show submitted URL, canonical URL, final URL, source URL, retrieved_at, detected updated date, content hash, raw HTML storage key/path, rendered HTML storage key/path, cleaned text storage key/path, screenshot/PDF storage key/path, images/assets metadata, local mirror path/manifest, skipped URLs, errors, provenance, manual-download state, and currentness warnings.
Source Currentness
Finality and later-authority review
Currentness warnings load with sources.
Unchecked currentness is not the same as current law. Formal, memo, and partner review should keep currentness warnings visible.
Fields shown here include currentness_status, currentness_check_required, currentness_warning, last_currentness_checked_at, and effective/version date conflict warnings.
Review amendment, repeal, supersession, appeal or later history, preemption/conflict, later authority, later guidance, and effective/version date conflicts before relying on a source.
Section 13I
Source automation review surfaces
Load or attach source-automation planning artifacts to prepare admin review summaries.
13I presents source-area packages, missed-source regression artifacts, source reverification planning, and corrective behavior plans for review only.
No button in this surface activates correction plans, approves sources, marks currentness final, runs crawler/downloader/capture work, ingests chunks, embeds content, or mutates trusted source-library records.
Admin approval, source review, legal review, security/config review, tests, and rollback/versioning gates remain separate and visible.
Review-only integration
Source automation artifacts are displayed as draft review packets until a later explicit admin workflow supplies reviewed decisions.
Source Reviewer App
Candidate review workspace
Review-onlyCandidate records onlyNot Unit JNot source approval or promotionNo currentness overrideNo ingestion, embeddings, or model callsNo source-file mutationExports are authorization inputs only
Load admin data to view Source Reviewer candidate counts.
Source ID
Queue
File name
Relative path
Issue area
Proposed role
Confirmed role
Currentness
Allowed use
Decision
Missing fields
Warnings
Group / badges
Reviewer
Updated / last event
Load admin data to view Source Reviewer candidates.
Answer Reports
Reported answers and review workflow
Pending answer reports remain queued for admin review and do not alter future answers automatically.
Internal Test RAG
Registry-backed retrieval and answer test
Internal test output will appear here.
Audit Logs
Safe structured audit records
Structured audit records are available through the existing safe admin audit API.
Admin Assist
Future LLM suggestions are drafts only. Admin final override controls corrections, source updates, currentness decisions, policy artifacts, and approved answer improvements.
legal_style and legal_readability assistance may improve grammar, clarity, tone, accessibility, and flow, but must preserve legal meaning, citations, caveats, source-sufficiency warnings, currentness warnings, disclaimers, and conclusions unless legal validation approves a change.
Correction/Policy Artifacts
Interpretation corrections
Unreviewed corrections do not control future answers.
Citation/style policies
Style rules cannot alter legal meaning, citations, caveats, or conclusions without validation.
Drafting/readability/validation policies
Approval, rejection, and deprecation controls remain future admin workflow work.
Source correction artifacts
Source corrections require review before any retrieval or answer behavior changes.
Live/Conversation Review
Live-session audit records
Placeholder for assistive live-session review.
Conversation summaries
Future summaries must preserve uncertainty and source limits.
Transcript review
Privacy, consent, retention, and summary generation status remain visible.
Missing-source tasks
Live sessions can later create admin-review tasks without replacing legal validation.