NyayaOS Ultra
AI Legal Platform
Command Center Preview

The public preview of routing, approvals, pricing, and release control.

This page is intentionally public-facing and read-only. It previews how NyayaOS Ultra is governed. The actual protected admin workspace opens only after an authorized admin session.

Testing Preview

All non-admin workspaces are free from April 12, 2026 to July 12, 2026.

The public site should make the testing preview rule obvious: free testing for all non-admin roles, but no casual access to grants, revokes, pricing governance, routing writes, or system secrets.

  • Public visitors can review the website, architecture, pricing logic, and access rules before signing in.
  • Approved testers can be upgraded from normal user to advocate, senior reviewer, judge-style reviewer, or super user at zero cost during the preview.
  • Admin access stays restricted to operators responsible for grants, revokes, pricing, routing, audit, and system controls.
Admin

Primary responsibility lane

Global operating policy, pricing rules, grants, revokes, and integrations.

Super User

Primary responsibility lane

Protected non-admin collaboration, elevated review, and sensitive workflow visibility.

Senior Advocate

Primary responsibility lane

Strategic review, premium routing override, and final approval.

Reviewer

Primary responsibility lane

Corrections, citation verification, and release readiness.

Normal User

Primary responsibility lane

Dashboard, uploads, and assigned matter participation without admin controls.

Visibility Matrix

Each role should see only the workspace meant for that responsibility.

Public preview pages remain visible without login, but actual workspaces and controls are gated by signed-in identity and role.

RoleVisible AreasRestricted Areas
Public VisitorWebsite, architecture, access page, pricing page, contact, demo, and sign-in.Dashboard data, uploads, drafting desks, team management, admin cockpit, or protected matter records.
Normal UserOwn dashboard, uploads, guided assistant, basic matter flows, and approvals explicitly shared with that account.Other users, role grants, pricing controls, routing overrides, or admin operations.
AdvocateDrafting, research, chronology, issue spotting, case review, and advocate workspace tools.Global user administration, secret keys, routing policy writes, or protected admin controls.
Senior Advocate / Judge-Style ReviewerHigher-trust review lanes, release readiness review, and premium legal quality checks.Admin-only grants, revoke controls, secret management, or tenant-wide config writes.
Super UserCross-workspace legal operations, elevated review, sensitive workflow visibility, and protected non-admin collaboration.Admin cockpit, user-grant controls, pricing governance, secrets, and global system settings unless admin is also granted.
AdminUser administration, grants, revokes, pricing, routing, integrations, audit, release control, and platform operations.Only the actions blocked by explicit policy, payment holds, or manual compliance pause.
Live Queues

Every workflow stage should have operator visibility.

The protected command center is meant to make progress and bottlenecks visible across intake, drafting, review, payment, release, and submission assist.

  • Intake queue
  • Draft queue
  • Review queue
  • Approval queue
  • Payment queue
  • Release queue
Override Actions

Operators can intervene without breaking the system model.

Override actions exist so the team can respond when a matter is high-risk, under-specified, urgent, or commercially unusual.

  • Manual hold
  • Approve release
  • Retry failed job
  • Rerun chronology
Coverage

31 operating modes

Client intake, drafting, review, billing, release, and submission support sit inside one operating model.

Graph Control

27 LangGraph nodes

The orchestration graph stays explicit from intake through audit save and command-center override.

Advanced Engines

30 advanced features

Verification, research, reasoning, pricing, memory, and filing adaptation are exposed as callable Nyaya services.

Missing Items

0 unresolved gaps

The command center audit can surface coverage gaps instead of hiding them behind marketing copy.

Primary Controls

The dashboard is built for action, not passive reporting.

These are the kinds of actions a firm should be able to trigger from one protected control plane.

  • force premium routing
  • hold release
  • mark payment received
  • rerun extraction
  • compare versions
  • view audit logs
Approval States

Release and submission move through named workflow states.

These states keep NyayaOS Ultra honest about whether the matter is still processing, needs review, is payment-gated, or is actually ready for release.

  • PROCESSING
  • UNDER_REVIEW
  • PENDING_APPROVAL
  • PAYMENT_PENDING
  • READY_FOR_RELEASE
  • RELEASED
Nyaya Engine Grid

The command center can now inspect concrete engine endpoints.

These are the advanced NyayaOS Ultra capabilities now wired into the backend instead of only being described in architecture copy.

  • citation verification engine -> /api/nyaya/citation/verify
  • court rules engine -> /api/nyaya/court-rules/resolve
  • multi-agent reasoning system -> /api/nyaya/multi-agent/reason
  • risk scoring engine -> /api/nyaya/risk-score
  • legal research agent -> /api/nyaya/research/preview
  • filing format auto-adapter -> /api/nyaya/filing/auto-adapt
Existing Platform Lanes

Core platform layers still stay visible next to the new engines.

This keeps routing, RAG, approval, pricing, and command-center operations inside the same operating dashboard.

  • RAG architecture -> /api/features/catalog
  • LangGraph nodes -> /api/nyaya/architecture
  • pricing engine + negotiation -> /api/nyaya/pricing/preview
Governance

Command-center power stays inside legal and operational boundaries.

These rules are what stop a powerful autonomous system from becoming an unsafe one.

  • Final legal responsibility remains with authorized humans.
  • Submission assist must pause for credentials or declarations.
  • Audit logs track routing, approvals, payment-linked release, and overrides.
  • Dynamic intake, connected filing preparation, and authoritative-source linking are already part of the internal architecture.
  • Final submission can still pause for actual court credentials, DSC, captcha, human declaration, registry-side checks, or connector/runtime setup.
  • The product should say clearly when it is in preparation mode, submission-assist mode, or manual-submit-only mode instead of pretending the filing is complete.