Users are able to classify planet type with real data

SSG-287-1

  1. Python script to pull temp & radius data for parent star
  2. TS script update to grab this info
  3. Terrestrial/Gaseous/Ice world classification
  4. Real formula

  • Perhaps a confirmation popup after?
  • Push new anomalies to cloud Supabase instance ✅ 2025-09-13

Adding more planet data - for research sandbox

Extra data - sandbox

  • Anomalies content to include exofop prefix e.g. KOI ✅ 2025-09-12
  • Allowing for KOI entries to be extracted
  • Research tree to show optional extras, including an explanation on each source and the cosmetic improvements ✅ 2025-09-13
  • Integration into flow for satellite deploy page ✅ 2025-09-12 #SSG-287-2

New research content

We’ll also need an entry point into the Research page/route. I propose that in the event I’m unable to bring the sidebar back in the remaining ~10 hours until this sprint is due, we just have a big section and a reminder for each next scene.

I’ve removed biology section for now:

<ResearchSectionModern title="Biology" infoText="Biological research and findings." backgroundType="planets">
 
<BiologyResearch />
 
</ResearchSectionModern>

SSG-287-4

  • New research blocks ✅ 2025-09-13
  • Allow users to use stardust for those items ✅ 2025-10-20 - probably somewhere around SSG-290
  • Some items are automatically “researched” and don’t incur a Stardust penalty ✅ 2025-09-13

Adding JVH back

  • Allow users to select the project ✅ 2025-09-13
  • New classification route ✅ 2025-09-13

New satellite deploy layout

Building on from SSG-287-2 This is SSG-287-3

CoM: Shapes

  • New research block ✅ 2025-09-13
  • Deploy satellite page reads from research stats for user ✅ 2025-09-13

Sharing posts

  1. Is there a way we can track where posts are shared? Is this only worth building when we have more users?

Fixes

Viewports are responsive

Simple flow - just go through each viewport on mobile & desktop

Single Tasks

  • Update how new exoplanet anomalies are named - the KOI, TIC, or KIC has to be included in the prefix ✅ 2025-09-12

I would suggest the research tasks take priority over milestones/weekly tasks for now - that can be for next week

Awaiting voting section - proposed in SSG-286

Media

Post-sprint

Satellite:

  1. Users can select multiple planets, or at least, cloud types are limited after a planet has its type confirmed.

Telescope:

  1. Research tree items for Sunspots

Definitely need to add rover section now

Go back to previous 2*2 format for sections:

<div className="grid grid-cols-1 md:grid-cols-2 md:grid-rows-2 gap-6 w-full">
 
{/* Set a consistent height for all viewports, matching SolarHealth block */}
 
<div className="w-full h-[420px] md:h-[420px] flex">
 
<TelescopeViewportSection />
 
</div>
 
<div className="w-full h-[420px] md:h-[420px] flex">
 
<SatellitePosition
 
satellites={satelliteData ? [satelliteData] : []}
 
flashingIndicator={satelliteData?.hasUnclassifiedAnomaly}
 
/>
 
</div>
 
<div className="w-full h-[420px] md:h-[420px] flex">
 
<SolarHealth />
 
</div>
 
<div className="w-full h-[420px] md:h-[420px] flex">
 
<RoverViewportSection />
 
</div>
 
</div>

Proper integration of anomalies into viewports, especially the telescope

Bugs - fixed as part of this release/announcement

https://github.com/Signal-K/client/issues/208 https://github.com/Signal-K/client/issues/207

Turns out the post-deployment scene in the telescope is still not mobile friendly…sigh

JVH annotation req, stat.

Propose more clear goals with the epics. “mobile polish” is too generic. Epic 2, story 3 is not relevant, as I said we won’t build any open dashboard or API until we hear from researchers they’re interested in working with us I want to have a go at building some of the visual/narrative mechanics in Godot, so I can take advantage of more