In modern manufacturing and energy plants, the most critical data is often trapped. It lives in legacy SQL databases from the 90s, proprietary sensor networks without APIs, and "black-box" PLC systems.
Solving issues in these environments usually requires manual data entry, cross-referencing printed logs, and human operators acting as the only "integration layer." This process is slow, error-prone, and disconnected from the rapid pace of modern decision-making.
AegisCore was built for the Amazon Nova Hackathon to change this. We provide the "Neural Bridge" that finally connects these legacy systems to the world's most advanced reasoning engines.
AegisCore is a mission-critical Agentic AI framework designed to orchestrate industrial automation. By using Amazon Bedrock Nova 2 Lite, we don't just provide a chatbotβwe provide a digital supervisor that can see into your databases, feel your hardware's pulse, and execute complex cross-platform workflows safely.
graph TD
User((Plant Operator)) -->|Natural Language| Frontend[Neural Dashboard]
Frontend -->|WebSocket| Bridge[Python Agent Bridge]
subgraph "The Intelligence Layer (Amazon Bedrock)"
Bridge -->|Stateful Converse API| Nova[Amazon Nova 2 Lite v1:0]
Nova -->|Tool Call Reasoning| Bridge
end
subgraph "The Physical Layer (MCP)"
Bridge -->|Grounding Request| MCPServer[Data Grounding Engine]
MCPServer -->|Query| SQLDB[(Legacy SQL Database)]
MCPServer -->|Telemetry| Sensors[Industrial Hardware]
end
Bridge -->|Final Actionable Report| Frontend
We selected the us.amazon.nova-2-lite-v1:0 model for its exceptional ability to handle Converse API Tool Use. Unlike simpler models that hallucinate, Nova 2 Lite follows a strict "Observe-Orient-Decide-Act" (OODA) loop:
- Observe: Listens to the operator's natural language request.
- Orient: Identifies which legacy system (SQL or Sensor) has the answer.
- Decide: Formulates a structured tool call.
- Act: Interprets the raw hex/data results and translates them back to human terms.
Grounding is everything. Our custom-built MCP Server acts as the translator. It converts legacy SQL rows and raw sensor voltages into "Clean JSON" that Nova can understand.
- Inventory Check: Cross-references browser-extracted data with the master SQL inventory.
- Hardware Telemetry: Simulates real-time polling of temperature and vibration signatures for Industrial Sensors.
In industry, a wrong click can be catastrophic. AegisCore implements a Policy-Driven Gatekeeper. Even if the AI determines a write-action is necessary, the system pauses, presents the reasoning in the "Orchestrator Logs," and requires a physical human signature (Approval) before the bridge executes the command.
To experience the true agentic power of AegisCore, try these prompts in the dashboard:
| Role | Operational Prompt | What the AI does behind the scenes |
|---|---|---|
| Logistics | "Cross-reference the browser data with the legacy database and check if we have enough Control Valve B in stock." | Extracts data, calls cross_reference_inventory, queries SQL, and summarizes the mismatch. |
| Engineer | "Provide a full system health report and specifically check the telemetry for Industrial Sensor A." | Calls get_system_status and get_sensor_telemetry, polls mock hardware, and generates a technical health diagnostic. |
| Safety | "Are there any discrepancies in the sensor vibration levels across the plant?" | Orchestrates multiple sensor checks to identify anomalies in the telemetry stream. |
The Model Context Protocol (MCP) is the "Hands" of our AI. It allows the model to interact with the world through two primary tools defined in supervisor.py and handled by nova_act_mcp_server.py:
-
cross_reference_inventory:- Inputs: List of objects
{name: string, quantity: number}. - Logic: Performs an exact match against the
legacy_inventorySQLite table. - Output: Returns a list of
MISMATCHorNOT_IN_DBfindings.
- Inputs: List of objects
-
get_sensor_telemetry:- Inputs:
{sensor_name: string}. - Logic: Simulates hardware polling via a randomizer to provide realistic Temperature and Vibration flux.
- Output: Returns a simulated hardware state JSON.
- Inputs:
βββ backend/
β βββ agents/
β β βββ agent_api.py # The WebSocket Bridge (The "Spinal Cord")
β β βββ supervisor.py # The Orchestrator (The "Frontal Lobe")
β βββ Dockerfile # Container definition for the Bridge
β βββ requirements.txt # Python dependencies (boto3, websockets)
βββ frontend/
β βββ src/
β β βββ components/ # Reusable Atomic UI Components
β β βββ App.tsx # Dashboard Orchestration & State
β β βββ index.css # Global Industrial Design System
βββ mcp_examples/
β βββ nova_act_mcp_server.py # The Translator between AI and Data
βββ .gitignore # GitHub exclusion rules
βββ README.md # This technical manifestoAegisCore is ready for enterprise container environments. You can launch the backend bridge using:
cd backend
docker build -t aegis-bridge .
docker run -p 8765:8765 -e AWS_ACCESS_KEY_ID=XXX -e AWS_SECRET_ACCESS_KEY=XXX aegis-bridgeThe project includes a comprehensive .gitignore to ensure that:
- β Secrets (CSV files, credentials) are never pushed to the server.
- β Environment folders (
venv,node_modules) are excluded. - β Artifacts (Gemini brain logs) remain local.
- AWS Bedrock Access: Ensure
us.amazon.nova-2-lite-v1:0is enabled in your region. - Python 3.10+ & Node.js 18+.
cd backend/agents
pip install boto3 websockets
python agent_api.pycd frontend
npm install
npm run devOur vision for the next 12 months includes:
- Edge Deployment: Running the Bridge on Greengrass devices.
- Computer Vision: Using Nova's multimodal capabilities to analyze thermal feeds.
- Regulatory Logs: Automated PDF reporting for safety audits.
Developed for the Amazon Nova Hackathon 2026. Empowering the future of industrial intelligence.