Production governance console — admin operations only
not connected
Bircan Migration
Final Locked Production Design v10.0

Enterprise admin control centre.

Govern knowledgebase ingestion, criteria registry build/validation/activation, worker operations and audit integrity without moving legal reasoning into the frontend.

Connection

Use same-origin when this dashboard is served by the backend. Set a backend origin only when hosted separately.

Secret is stored in this browser's local storage only. The dashboard sends it in admin headers and session POST requests.
API
—
/api/health
Knowledgebase
—
Sources / chunks / clauses
Registry
—
Build / validate / active
Worker
—
Queue states

Locked lifecycle map

This console exposes operational controls only; it does not assess law or approve advice.

StageOwnerDashboard controlRule
!
Production guard.Activation occurs only after backend validation passes. If ingestion times out but the existing index is healthy, the operator may continue to registry dry-run with a warning. Invalid registries are never activated silently.

One-click governed lifecycle

Runs the full admin sequence with route diagnostics, resumable status and validation-gated activation.

Lifecycle output

Operator-grade log with route, HTTP status and backend response.

Lifecycle output will appear here.
✓
Knowledgebase is the legal-source repository.Upload, scan, search and maintain source files. This layer does not determine eligibility.
1

Stats

Check live source, chunk and clause counts.

2

Scan / ingest

Index governed legal-source files.

3

Cleanup

Remove known invalid placeholder sources.

Upload legal source files

Uploads are routed to governed backend folders and may trigger ingestion.

Browse and search knowledgebase

Load physical files or search indexed content.

No files loaded.Use Load files or Search.

Knowledgebase operation output

Raw backend responses for audit/debugging.

Knowledgebase output will appear here.
!
Registry activation is the production gate.Only validated active registries may drive deterministic assessment.
1

Dry-run build

Test registry creation without activation.

2

Build registry

Create a draft registry and return an ID.

3

Validate / activate

Validate first, activate only after pass.

Registry browser

Load built/active registry records returned by backend.

No registry records loaded.

Registry output

Route and registry responses.

Registry output will appear here.
✓
Worker operations are asynchronous.Payment finalisation creates durable queue jobs only. This console may monitor and trigger worker controls but does not create advice.

Queues and worker controls

Monitor queue states and run safe operational controls.

No queue data loaded.

Worker output

Worker output will appear here.

Audit and integrity

Every material state transition must be reconstructable.

No audit data loaded.

Integrity output

Integrity result will appear here.

Legal Research Index

Index governed legal files from knowledgebase/MIGRATION into the internal Pinecone retrieval layer. This is research support only; it does not validate the registry or approve advice.

Governance boundary: Legal files must be kept in the Node knowledgebase repository. Pinecone is only a retrieval index. The research assistant cannot assess eligibility, approve advice, or render PDFs.
Legal research indexing output will appear here.

Search indexed legal material

Search the Pinecone legal research index after indexing knowledgebase/MIGRATION.

Search results will appear here.

Ask internal legal research assistant

Strict context-only Q&A. Answers must cite the specific Act section, Regulation, Schedule clause, instrument or policy source found in the retrieved chunks.

Context-only answer will appear here.

Legal research audit

Recent legal research queries recorded by the Node backend.

Route diagnostics

Probe admin routes and see exact HTTP status/body.

Diagnostic output

Diagnostics will appear here.