PROJECT 02 / AEGISGRID
Spot the threat before it gets close.
We built AegisGrid as a synthetic drone-swarm simulation. It groups nearby threats, scores their risk and helps explain which ones need attention first.
SYNTHETIC SWARM / SCENARIO 04
THREAT GROUPING / RISK REVIEW
C-01
Low4 pointsC-02
Medium3 pointsC-03
High5 pointsAFTER-ACTION
Nearby points are grouped first, then ordered by risk for review.This visual was created for the portfolio to show the project idea clearly.
01 / CONTEXT
What we were trying to solve
A large group of incoming objects can be difficult to review one at a time. The project explores how nearby threats can be grouped and prioritized before presenting the result clearly.
Everything shown here stays inside a synthetic simulation.
02 / TEAM
Team project
We combined clustering, risk scoring, resource allocation and a visual interface during the hackathon.
An optional AI layer helped explain the result in plain language, but it sat outside the core decision loop.
03 / SYSTEM
How it comes together
The decision path stays separate from the explanation shown after it.
- 01Synthetic incoming objects
- 02Movement and distance information
- 03DBSCAN-style grouping
- 04Cluster risk
- 05Priority ranking
- 06Response and allocation context
- 07Optional explanation layer
- 08After-action summary
04 / SIMULATION VIEW
From moving points to a review order.
The supporting views show allocation context and a quieter after-action readout without turning the simulation into a game interface.
PRIORITY / ALLOCATION CONTEXT
SYNTHETIC SCENARIO
REVIEW ORDER
01C-03 / HIGH RISK- 01C-03REVIEW FIRST
- 02C-02NEXT
- 03C-01MONITOR
ALLOCATION CONTEXT
The interface keeps priority and response context adjacent without turning the simulation into a targeting display.SITUATION / AFTER-ACTION SUMMARY
ANALYTICAL REVIEW
Nearby synthetic objects form clusters.
Cluster distance and risk shape priority.
An optional layer describes the result afterward.
Nearby points are grouped first, then ordered by risk for review.
05 / REFLECTION
What I learned
A fast team build still needs a clear line between what makes a decision and what explains it.
- 01
Clustering output becomes more useful when the interface gives it a readable order.
- 02
Technical logic and explanation should remain separate.
- 03
A serious visual tone can communicate urgency without becoming sensational.
WHERE IT STANDS NOW
A hackathon simulation and working project concept.
The case study focuses on the grouping, priority and explanation flow created during the event.