Projects · 01

Sightline

A lunar landing-site planner. It shows when the Sun and Earth are in view from a landing site at the Moon's south pole, every hour from 2026 to 2049, and whether a landing date fits a mission's limits.

Open the live site Read the code

Right now

Checking…

Read from /api/status after the page loads. How it works

My part
I led the six-person team behind it (NASA Space Apps 2026) and owned the architecture decisions. AI coding agents wrote most of the code, under my direction and review.
Result
Sun and Earth positions match JPL Horizons within 0.0071° over 5,469,984 hourly checks. Deploys go out as a canary and roll back automatically. 2,020 tests run in CI.
Stack
  • Python
  • TypeScript and React
  • Google Cloud Run
  • Terraform
  • Firestore
  • Redis
  • Pub/Sub and BigQuery
  • GitHub Actions
Sightline's front page. The Moon seen from above its south pole, half lit, with marked landing sites, a time bar set to 27 November 2026 and the Scout co-pilot open on the right.
lunarsightline.com on 18 November 2026, after closing the welcome card. Taken with headless Chrome at 1440 by 900, at twice the pixel density.

What it does

A lander at the Moon’s south pole needs the Sun for power and Earth for a direct radio link, and there both only skim the horizon, so the hills decide when each is in view. Sightline computes that from NASA’s terrain and ephemeris data for 13 sites, every hour from 2026 to 2049.

You pick a site, a landing date and a mission: how long it lasts, how much darkness and radio silence it can take. Sightline answers in words. It fits, it fits with little margin, or it does not and why, with the next landing that does.

How it is built

A Python pipeline reads NASA’s LOLA terrain models and SPICE kernels and computes the horizon and the Sun’s and Earth’s positions for each site. The front end is React and TypeScript.

It runs on Google Cloud as four Cloud Run services, each with its own image, identity and deploy: the web server, saved plans, the co-pilot, and a private worker that counts questions. A global load balancer with a CDN and an edge firewall sends each path to its service. Every piece of it is declared in Terraform and applied from GitHub Actions, which signs in to Google Cloud with no stored keys.

Merging to main deploys one service at a time. Each new version starts with no visitors, is tested, then takes a share of traffic, and rolls back by itself if its checks fail.

Who wrote the code

AI coding agents wrote most of it: nearly all the code, tests, Terraform and docs. I set the direction, reviewed the work and made the calls, and I led the six people on the team. The repository says the same in its AI_USAGE.md.

The architecture decisions were mine to make. Three of them: one server split into four services with separate identities, the rule that the co-pilot never types a number (the server fills in every figure from computed data), and deploys that prove themselves before visitors reach them.

Architecture · scroll sideways for all of it →

How Sightline is hosted A visitor reaches an edge firewall (Cloud Armor), then a load balancer with a CDN. The load balancer sends plan paths to the plans service, which uses Firestore; chat paths to the co-pilot service, which calls the Anthropic API and publishes to Pub/Sub, which feeds BigQuery and a private events worker; and everything else to the web service, which reads Cloud Storage and Text-to-Speech. All four services are Cloud Run. Redis holds rate limits and kept answers. Everything is declared in Terraform and applied from GitHub Actions with no stored keys. visitor edge firewall Cloud Armor load balancer CDN · HTTPS /api/plans plans Cloud Run /api/chat · /api/ask co-pilot Cloud Run events worker Cloud Run, private everything else web Cloud Run Firestore Anthropic API Pub/Sub BigQuery Cloud Storage Text-to-Speech Redis rate limits, kept answers, circuit breaker All of it in Terraform applied from GitHub Actions, with no stored keys
Four Cloud Run services behind one load balancer. No service calls another to answer a visitor; the load balancer sends each path to the service that owns it. Drawn from docs/SYSTEM_DESIGN.md in the repository.

Where these claims come from