This is a submission for the GitHub Finish-Up-A-Thon Challenge
This is my submission for the GitHub Finish-Up-A-Thon Challenge.
The idea behind this challenge really hit home for me: finally finish what you started.
HELIX started as a satellite tracking and conjunction detection project. It already had a working backend, orbital propagation, a 3D globe, and basic AI summaries. But it still felt like a technical prototype.
For this challenge, I brought it much closer to a finished product.
I turned HELIX into an AI-powered space operations intelligence platform that can investigate orbital risk, correlate multiple space data sources, and generate explainable operational assessments.
GitHub Copilot helped me push the project from “cool prototype” to something that feels like a real mission operations console.
Github Repository :
HELIX is an AI-powered Space Operations Intelligence Platform that transforms fragmented orbital, launch, and space weather data into actionable mission intelligence.
Built on top of Coral's federated SQL runtime, HELIX enables operators, researchers, and analysts to investigate conjunction risks, correlate launch activity, monitor orbital congestion, and generate explainable operational assessments through multi-step AI investigations.
Unlike traditional satellite trackers, HELIX focuses on answering:
What is happening in orbit?
Why is it happening?
What should operators pay attention to next?
Earth's orbit is becoming increasingly congested.
Thousands of active satellites, frequent launches, and growing debris populations create a complex operational environment where understanding risk requires data from multiple disconnected systems.
Most tools can visualize orbital activity.
HELIX investigates it.
Using Coral as a unified intelligence layer, HELIX correlates:
…
HELIX is a local-first space situational awareness and mission intelligence platform.
It helps answer questions like:
Instead of only showing satellite positions, HELIX performs structured investigations over operational data.
HELIX includes a real-time globe interface for viewing satellites and conjunction events.
The frontend uses:
The backend uses:
System Architecture:
HELIX connects multiple operational data sources:
These sources are exposed through Coral as SQL-queryable tables.
That means HELIX can run cross-source intelligence queries like:
conjunction risk + NOAA space weather
launch activity + current solar conditions
closest conjunctions + Space-Track object metadata
Starlink launch activity + local conjunction pressure
The biggest finish-up improvement was moving from:
prompt → query → summary
to:
prompt → investigation plan → query chain → findings → assessment → recommendations
The investigation engine is deterministic and safe.
It does not generate arbitrary SQL.
Instead, it chooses from approved Coral SQL templates and runs a bounded sequence of investigation steps.
Example investigation:
`User: Why are conjunction risks elevated today?
[1] Querying conjunction risk distribution
[2] Analyzing closest high-risk events
[3] Detecting repeated satellite involvement
[4] Comparing risk density by day
[5] Checking upcoming launch activity
[6] Checking NOAA space weather
[7] Correlating findings
[8] Generating operational recommendations`
Before the Finish-Up-A-Thon, HELIX was a project with a lot of potential but it was stuck in the place where many ambitious side projects end up.
The foundation was already there.
It had a FastAPI backend, satellite data ingestion, orbital propagation, conjunction detection, a SQLite database, and a 3D globe interface. It could track satellites, visualize orbital activity, and identify close approaches between objects in space.
Technically, it worked.
But it didn't feel finished.
HELIX could tell users what was happening, but it struggled to explain why it was happening. The AI layer was limited to basic summaries, many features felt disconnected, and the overall experience resembled a collection of powerful components rather than a unified intelligence platform.
In short, HELIX felt more like a satellite-tracking prototype than a true mission operations system.
That was the state of the project when I began the finish-up process.
Instead of starting over, I focused on understanding what already existed.
Using GitHub Copilot and advanced GPT-5.5 style assistance, I began by inspecting the codebase, mapping the architecture, and identifying the areas that would create the biggest impact if improved.
The process became highly iterative:
Rather than rewriting everything, I concentrated on strengthening what was already there.
The first step was cleaning up and stabilizing the architecture while preserving the satellite tracking and conjunction detection capabilities that already worked.
From there, I introduced Coral as the data orchestration layer and connected multiple operational datasets into a unified queryable system.
Suddenly, HELIX was no longer looking at isolated pieces of information.
It could correlate data across:
The project started evolving from a visualization tool into an intelligence platform.
The most significant change was the intelligence workflow itself.
Before, the AI interaction looked something like this:
Ask a question
→ Run a query
→ Summarize the results
It worked, but it was shallow.
The system answered questions without actually investigating them.
I wanted HELIX to think more like an analyst.
So I built a deterministic investigation engine that transformed the workflow into:
Ask a question
→ Build an investigation plan
→ Execute approved Coral queries
→ Correlate findings
→ Generate an assessment
→ Recommend next actions
With the help of Copilot, I implemented:
The system stopped behaving like a chatbot and started behaving like an operations analyst.
Consider a question like:
Why are conjunction risks elevated today?
Previously, HELIX would have returned a simple summary of conjunction data.
Now it performs a full investigation.
It can:
Only then does it generate an assessment and suggest possible operational actions.
That fundamentally changed how the platform feels.
The transformation wasn't about adding flashy features.
It was about connecting everything together.
GitHub Copilot helped accelerate the parts that often cause projects to stall:
Feature by feature, HELIX became more cohesive, more intelligent, and more useful.
Before the Finish-Up-A-Thon, HELIX was a promising demonstration of satellite tracking technology.
Today, it feels like a genuine AI-powered space operations console.
It can investigate, correlate, explain, and recommend not just visualize.
The project didn't need a complete rewrite.
It needed someone to finish what had already been started.
GitHub Copilot helped make that possible.
And in many ways, HELIX's biggest achievement wasn't the technology itself—it was finally crossing the line from almost finished to fully realized.
I used GitHub Copilot heavily throughout the finish-up process, specifically with advanced ChatGPT/GPT-5.5 style coding assistance.
Copilot helped with:
The most valuable part was not just code generation. It was the ability to work iteratively:
That workflow made it possible to finish a project that otherwise could have stayed half-done.