01Architecture
COMPLETEGitHub Verified
The interactive Control Tower is a labeled synthetic demonstration of a Control Tower operational view mapped to the 7-stage NARI Intelligence Lifecycle. Demonstration telemetry is generated from synthetic simulation unless explicitly labelled as physical-test data. It is read-only and does not control physical robots. It does not expose private GitHub files, source code, credentials, physical actuator controls or live production telemetry.
Physical AI product assurance
Architecture → Code → Simulation → Robot Test → Evidence → Control Tower → Release. Public status is GitHub-backed. Simulation never authorizes physical movement.
Last verified: 2026-09-10T20:20:00Z UTC
01Architecture
COMPLETEGitHub Verified
02Code
SOFTWARE V0GitHub Verified
03Simulation
BASELINE PASSEDSimulation Baseline Passed
04Robot Test
NOT AUTHORIZEDNot Authorized
05Evidence
STALEEvidence Pending
06Control Tower
ACTIVEGitHub Verified
07Release
NOT READYNot Ready
Hardware interface
SOFTWARE BOUNDARY PASSEDSoftware boundary passed: execution terminates at a mock/stub hardware boundary. Software-level result only; no physical robot validation is implied.
GitHub Verified
Navigation
SOFTWARE BASELINE PASSEDSoftware baseline passed: Navigation V0 produces MotionRequest / motion-intent only and stops before any hardware. Software-level result; no physical robot validation is implied.
GitHub Verified
Simulation V0
BASELINE PASSEDDeterministic, fail-closed Simulation V0 with mock/stub-only actuator execution.
Simulation Baseline Passed
Navigation V0
SOFTWARE BASELINE PASSEDSoftware baseline passed. Navigation generates MotionRequest / motion intent only and stops before any hardware or actuator; no physical robot validation is implied.
GitHub Verified
Hardware Authority
NOT AUTHORIZEDSoftware boundary passed: execution terminates at a mock/stub hardware boundary. This is a software-level result only; it does not authorize physical hardware activation and implies no physical robot validation.
Not Authorized
Physical Robot Test
NOT AUTHORIZEDPhysical robot testing requires explicit human authorization, approved robot/configuration identification, readiness evidence, and applicable safety clearance.
Not Authorized
MAHAA CHANDI-18 follows a human-authorized deployment model. Software and simulation validation do not independently authorize physical movement. Human authorization remains the final gate between digital validation and physical action.
Evidence / Engineering Control Tower
This view reports public engineering provenance only. It does not dispatch robots, expose credentials, or treat synthetic demonstration telemetry as physical-world evidence.
Evidence stale
Live evidence retrieval unavailable: showing last recorded snapshot
Software simulation · mock/stub actuators only
CI and safety-gate success is GitHub-recorded software evidence. It is not physical safety certification and is not live CI polling.
Software boundary passed · execution ends at a mock/stub boundary
Artifact presence is not physical-world evidence
A human authorization gate remains in force
Not ready for physical deployment
Software-only V0
GitHub Verified
Architecture
COMPLETEEngineering evidence recorded internally
Code
SOFTWARE V0Engineering evidence recorded internally
Simulation
BASELINE PASSEDEngineering evidence recorded internally
Robot Test
NOT AUTHORIZEDEngineering evidence recorded internally
Evidence
STALEEngineering evidence recorded internally
Control Tower
ACTIVEEngineering evidence recorded internally
MAHAA CHANDI-18 follows a human-authorized deployment model. Software and simulation validation do not independently authorize physical movement. Human authorization remains the final gate between digital validation and physical action.
Synthetic demonstration
The console below is a labeled synthetic simulation. It is not physical-world evidence and cannot move a robot.

MahaaAi · Robot Control Tower
Physical Intelligence Live Lab
Explore the NARI Intelligence Lifecycle — Sense → Understand → Twin → Reason → Govern → Act → Learn — with Somavati visible at the Govern gate. This is a Control Tower operational view, not a second architecture.
Somavati Govern
Enabled
Safety Bypasses: 0 in this synthetic scenario
Physical control unavailable
Fleet profiles
6
Simulated plant twins
5,000
Active scenario
Dry Soil
Somavati
APPROVE
Data source
Synthetic V1
Interactive simulation
—
Soil moisture
22%
NARI proposal
IRRIGATE
Somavati govern
APPROVE
Verification
PASS
Demonstration telemetry is generated from synthetic simulation unless explicitly labelled as physical-test data. Only soil moisture drives the V0 irrigation policy. Temperature, humidity and EC are contextual synthetic telemetry.
Control Tower operational view
demo-initializing
Sense → Understand → Twin → Reason → Govern → Act → Learn
Sense
Sensor intake · Synthetic soil-moisture observation received
Understand
IoT / Edge qualify · Freshness and quality checked
Twin
Digital Twin update · Plant Digital Twin state updated
ReasonNARI
NARI proposal · NARI proposes bounded irrigation
GovernSomavati
Somavati safety gate · Somavati independent checks complete
Act
ROS 2 simulation · Irrigation simulated
Learn
Verification / evidence · PASS
Robotics Lab Fleet 1
Simulation profiles — not physical fleet claims
MRL-01
Plant care & ground operations
MRL-02
Vision, inspection & perception
MRL-03
Irrigation & water intelligence
MRL-04
Field mission & mobility research
MRL-05
Safety, patrol & system inspection
MRL-06
Plant growth & Digital Twin research
5,000 Digital Plant Twins — Synthetic Simulation
Last 12 synthetic cycles

Twin-00041
Water-stressed
Irrigation required
Evidence trace
Sanitized
{
"scenario": "dry_soil",
"trace_id": "demo-initializing",
"plant_twin": "TWIN-00041",
"execution_mode": "simulation",
"synthetic_data": true,
"nari_proposal": "IRRIGATE",
"safety_gate": "APPROVE",
"verification": "PASS",
"safety_bypass": false,
"physical_control": false,
"data_classification": "synthetic_v1"
}Every cycle carries explicit source, execution and safety labels. This envelope is synthetic and does not include private files, credentials or actuator commands.