AECN — AstroBharat Enterprise Command Nexus

NEXUS

One Vision. Every Company. Total Control. NEXUS brings departments, AI workforce, commands, approvals, security, audit activity, automation visibility, and system health into one controlled AECN interface.

Protected enterprise access

NEXUS Secure Access

First Owner Setup

Initial installation only. This is not public registration. An authorized Setup Code and mandatory Authenticator verification are required before OWNER access becomes active.

Read-only API modeProtected writes require owner tokenAPI: https://api.aastrobharat.com/api/v1/phase3
Loading NEXUS dashboard data…
Executive command view

NEXUS Overview

A controlled owner-level snapshot of the enterprise structure, AI workforce, decision queue, governance activity, and protected operating posture.

NEXUS data loadingOwner-controlled operations
01Departments
Loading…
Live count from the read-only AECN dashboard API.
02AI Employees
Loading…
Current AI workforce structure available to NEXUS.
03Commands
Loading…
Approved: 0 · Rejected: 0 · Pending: 0.
04Approvals
Loading…
Approved: 0 · Rejected: 0 · Pending: 0.
05Audit Logs
Loading…
0 audit events loaded from the read-only audit endpoint.
06Security Rules
Loading…
Security governance display is ready for future protected rules.
Decision Workflow

Current command and approval records. No command execution or n8n trigger is performed by this overview.

Command Status

Approved 0Rejected 0Pending 0

Approval Records

Approved 0Rejected 0Pending 0
Enterprise Posture

Current verified software visibility is kept separate from future company and director modelling.

DepartmentsLoading…
AI WorkforceLoading…
Company relationNOT_MODELLED
Directors modelNOT_MODELLED
n8n execution: DisabledCommand execution: DisabledProtected writes: Owner-token gatedRuntime token storage: Memory onlyTesting model: DeepSeek onlyGPT-5 testing: Prohibited
Owner-directed decision intake

Command Center

Create protected PENDING commands, inspect command lifecycle records, and run read-only activation-readiness checks without executing commands or triggering n8n.

0 commands loadedOwner-token protected
Total commands—Current command records
Pending—Awaiting owner decision
Approved—Approval recorded
Rejected—Rejected command records
Command creation is a protected database write that creates only one PENDING command and its audit record. Approval, n8n execution, activation, and command execution remain separate and blocked here.
Protected Command CreationPENDING only

Create Pending Command

This owner-token gated control creates one PENDING command and one audit log only. It does not approve commands, trigger n8n, or execute commands.

Token use: Runtime memory onlyCreated command status: PENDINGApproval required: Yesn8n trigger: DisabledCommand execution: BlockedAudit action: COMMAND_CREATED

Safety: this action creates one PENDING command and one audit log only. Approval, n8n workflow execution, and command execution remain blocked.

No commands loaded yet.
Owner-governed decision control

Approval Center

Review approval records and submit an owner-token protected decision only when a PENDING command is available. Approval never executes the command or triggers n8n from this screen.

0 approvals loadedProtected owner action
Total approvals—Current approval records
Pending—Awaiting final decision
Approved—Approved records
Rejected—Rejected records
A protected approval request updates only the selected PENDING command through the existing owner-token gated backend route. Command execution, activation, webhook calls, and n8n execution remain separate and blocked here.
Protected Approval Decision

Approve or reject the selected pending command

No PENDING command

The runtime owner token exists only in React memory for the protected request. It is never stored, persisted, logged, or placed in the page URL.

Token persistence: DisabledRuntime token: Memory onlyPending command required: YesSelected command: None availablen8n execution: DisabledCommand execution: Blocked
No PENDING command is available, so approval controls remain disabled.

Approval Records

Read-only history of approval decisions returned by the current API.

0 records
No approvals loaded yet.
Enterprise protection and policy control

Security & Governance

Review department security rules and perform narrowly scoped, owner-token protected creation or status updates through the existing security-rule routes.

0 rules loadedOwner token required
Total rules—Current API records
Active—Currently active records
Inactive—Retained inactive records
Protected writesLockedRuntime owner token required
This surface does not create or approve commands, activate capabilities, execute commands, call webhooks, or trigger n8n workflows. Security-rule writes remain owner-token protected.
Owner-token protected write

Protected Security Rule Creation

POST /security-rules

The owner token is used only from React memory for this request. It is never stored, persisted, logged, or placed in the page URL.

Token persistence: DisabledRuntime token: Memory onlyBackend route: POST /security-rulesAudit record: Created with rulen8n trigger: DisabledCommand execution: Blocked
This creates one SecurityRule record and one audit log only. Command creation, approval, activation and execution remain separate.
Governance posture

Protected boundaries

Security rules remain separate from command approval, activation, execution and automation.

Owner-token protectionRequired
Command creationNot included
Command approvalSeparate
Command executionBlocked
n8n triggerDisabled
Audit recordRequired

Security Rule Registry

Review current department rules and use the existing protected status action to switch a record between ACTIVE and INACTIVE.

0 registered
No security rules configured yet.
Traceability and operational evidence

Audit & Activity

Review the latest command-linked audit events returned by the existing read-only audit endpoint. This screen provides evidence visibility only.

0 events loadedRead-only evidence
Loaded events—Current endpoint response
Command-linked—Events with command linkage
Access modeRead-onlyNo frontend audit writes
Evidence sourceAudit endpointExisting API response only
Audit entries cannot be created, edited, deleted, approved or executed from this screen. No database write, command action, webhook call or n8n workflow is triggered here.
Evidence timeline

Recent Audit Events

Each record displays the action, timestamp, resource type and available command linkage supplied by the current API.

Current response set
No audit logs loaded yet.
Governance boundary: command approval, security-rule writes, activation and execution remain in separate protected control surfaces.
Enterprise operating structure

Departments

A live organizational directory showing each department, its assigned AI workforce, command activity, and security-governance coverage.

0 departments loadedOwner token required for lifecycle requests
Departments—Current enterprise units
Assigned AI workforce—Department-linked AI employees
Department commands—Command records across units
Security rules—Governance rules by department
Current software records represent departments and AI employees only. Company and director relationships remain NOT_MODELLED.

Custom Department Builder

Department Name → Purpose → Director → Workers → Rules → Preview → Save Draft → Test → Activate later

Draft only · activation not implemented yet
Local Department Preview
Name
Not entered
Purpose
Not entered
Reporting chain
Department → Director → CEO → Client Owner
Workers
None selected
Rules
At least one required

Department lifecycle controls create a PENDING command and audit entry only. The current Department model has no status field, so no department status mutation runs.

No departments loaded yet.
Intelligent operating capacity

AI Workforce

A department-organized view of AI employees, assigned roles, operating status, and skill coverage across the current enterprise software structure.

0 AI employees loadedOwner token required for lifecycle controls
Total AI workforce—Current AI employee records
Active employees—Records currently marked ACTIVE
Departments represented—Department groupings with employees
Unique role labels—Distinct role names in current records
Current records describe AI employees, not companies. Company and director relationships remain NOT_MODELLED.

Custom Worker Builder

Name → Department → Director → Work Instructions → Preview → Save Draft → Test → Activate later

Draft only · never creates a live AI employee
Local Worker Preview
Name
Not entered
Department
Not selected
Reporting chain
Worker → Director → CEO → Client Owner
Instructions
Not entered

AI employee lifecycle controls update only the employee status and audit log. They do not execute commands, call models, or trigger n8n workflows.

No AI employees loaded yet.

Draft Workspace

Owner-scoped WORKER and DEPARTMENT drafts. Test runs deterministic isolated validation only and never activates automatically. Activate is an explicit owner action that creates the live Worker or Department record.

0 drafts loaded
Enter the memory-only runtime owner token to load drafts.
Workflow orchestration visibility

Automation Control

The future owner control surface for HOLD, RESUME, queue visibility, active-lock status, builder routing, and execution reporting through the approved n8n operating model.

Visibility shell onlyNo live controls enabled
Control surfaceShellPremium frontend visibility layer
HOLD / RESUMENot connectedNo frontend control request is sent
Queue and active lockNot connectedNo live queue or lock data loaded
Execution reportingNot connectedNo live execution stream loaded
This screen is currently a non-interactive visibility shell. It does not publish, activate, pause, resume, execute, edit queue data, release an active lock, call a webhook, or trigger an n8n workflow.
Operating control model

Safe automation lifecycle

Final integration must preserve one task, one builder, and one active lock, with owner-governed HOLD and RESUME behavior.

HOLDFuture protected action
RESUMEFuture protected action
Queue visibilityIntegration pending
Active lockIntegration pending
Execution historyIntegration pending
n8n reportingIntegration pending
AI testing governance

Model and key policy

Testing remains isolated from future production routing and credentials.

Testing providerDeepSeek only
GPT-5 during testingProhibited
Keys in chatNever permitted
Production routingFuture owner approval required
Pending live integration: approved read-only queue, lock, execution and reporting visibility first; protected HOLD/RESUME controls only after exact owner approval and end-to-end safety verification.
Owner authority and enterprise configuration

Owner Settings

Review the frozen AECN identity, testing policy, verified data boundaries and protected delivery controls. This screen is a static governance surface and stores no owner token or API key.

Protected shellNo secrets stored
Owner authorityRahul jiFinal protected-action approver
Dashboard identityNEXUSAstroBharat Enterprise Command Nexus
Testing modelDeepSeek onlyGPT-5 prohibited during testing
Settings modeRead-only shellNo live settings write connected
No API key, owner token, credential or production secret is entered, displayed, persisted or configured on this screen. Deployment, routing, activation and protected production actions require fresh exact owner approval.
Frozen enterprise identity

Approved Naming & Brand

Formal nameAstroBharat AI Enterprise
Short nameAECN
Dashboard nameNEXUS
TaglineOne Vision. Every Company. Total Control.
ENC namingNot selected
Frozen model policy

Testing & Production Routing

Testing providerDeepSeek API only
GPT-5 during testingProhibited
Production keysNot configured here
Production routingFresh owner approval required
Key entry in chatNever allowed
Verified delivery data truth

AI Workforce Foundation

14Departments
152AI Employees
152/152Assigned department and role
151Unique role labels
Duplicate role label retained in verified data: Sales Analytics AI.
Modeling boundaries

Truth Before Expansion

Company relationNOT_MODELLED
DirectorsNOT_MODELLED
152 AI EmployeesNot equal to 152 companies
Future expansionSeparate approved roadmap
Protected delivery controls

Owner Approval Boundaries

The following actions remain outside this static screen and cannot be performed without their separate protected process.

Deployment or restartFresh approval required
Git commit or pushFresh approval required
Production API or DB writeFresh approval required
Workflow publish or activationFresh approval required
Credentials or secret accessNot available here
Live settings updateNot connected
Owner Settings status: premium governance shell ready; interactive preferences, credential management and production routing remain intentionally unconnected.
Integration visibility and operational readiness

API & System Health

Review the approved AECN route inventory and one live, read-only NEXUS backend API availability signal. Frontend runtime, database, n8n and model-provider health remain outside this screen until separately verified.

12 routes listedRead-only backend health
Approved routes12Current frontend route registry
Backend API probeCheckingRead-only NEXUS health GET
Database healthNot measured hereNo database probe from this screen
n8n healthNot measured hereNo workflow-health probe connected
This screen performs one read-only NEXUS backend health GET. It does not prove frontend-container, database, n8n or model-provider health and performs no database query or write, service restart, webhook call or workflow execution.
Current health coverage

Visibility Boundaries

Route inventory and the read-only backend API availability signal are available. Frontend-container, database, n8n, model-provider, latency, dependency and incident checks remain outside this screen.

API route inventoryAvailable
Backend API availabilityChecking
Frontend runtime statusNot connected
Database connectivityNot connected
n8n workflow healthNot connected
Model-provider healthNot connected
Protected operating boundary

No Health Actions Enabled

This screen is intentionally read-only. Existing protected approval decisions remain available only in their separate owner-token gated control surface.

Manual refreshUnavailable
Service restartBlocked
Database writeNot included
Workflow executionNot included
Secret visibilityNever displayed
Approved route registry

AECN API Routes

These are route references used or retained by the current frontend. Their presence does not itself prove runtime availability.

12 registered
01Route reference
/api/v1/phase3/healthRead-only probe: Checking
02Route reference
/api/v1/phase3/departmentsRuntime status not measured by this screen
03Route reference
/api/v1/phase3/ai-employeesRuntime status not measured by this screen
04Route reference
/api/v1/phase3/commandsRuntime status not measured by this screen
05Route reference
/api/v1/phase3/approvalsRuntime status not measured by this screen
06Route reference
/api/v1/phase3/audit-logsRuntime status not measured by this screen
07Route reference
/api/v1/phase3/security-rulesRuntime status not measured by this screen
08Route reference
/api/v1/phase3/dashboardRuntime status not measured by this screen
09Route reference
/api/v1/phase3/commands/:commandId/approval (POST protected)Runtime status not measured by this screen
10Route reference
/api/v1/phase3/commands (POST protected pending create)Runtime status not measured by this screen
11Route reference
/api/v1/phase3/ai-employees/:employeeId/status (PATCH protected lifecycle)Runtime status not measured by this screen
12Route reference
/api/v1/phase3/departments/:departmentId/lifecycle-request (POST protected request)Runtime status not measured by this screen
Current health integration: read-only backend API availability only. Frontend-container, database, n8n, model-provider, response-time, dependency and incident telemetry remain unmeasured by this screen.
Governed prompt lifecycle · 11

Prompt Management

Review scoped prompt registries, create immutable candidate versions, run deterministic validation, explicitly approve activation, and roll back by creating a new preserved version.

Authenticated NEXUS session required
Sign in through NEXUS Secure Access. Prompt data is not requested while logged out, and the legacy owner token is intentionally not used.

Registry Detail

Authenticated registry detail is unavailable.

Locked Policies · Read-only

Locked policy content will appear with an authenticated registry detail.

Version History

Newest first. Old versions remain immutable and visible.

Version history requires an authenticated registry selection.
Safety lock: NEXUS bearer sessions remain in memory only. No migrations, no command execution, no n8n execution, no persistent token storage, and no main-domain changes. Legacy command creation and approval controls remain owner-token protected and separate from NEXUS authentication.