Build B-07
An image-registration pipeline for lunar imagery needs a console where its results can be viewed and checked against a reference.
| Mode | Depends on | State |
|---|---|---|
| Mock | Nothing external | Implemented |
| Live (V1) | Frontend API; upload cross-matched against a reference | Reads implemented; upload needs new routes |
| Simulated processing (V2) | Not yet specified | Planned |
The console’s three data-source modes and what each depends on.
Not documented yet.
LunarReg is an image-registration pipeline for lunar imagery. The Mission Console is the frontend Hari designed for it: a place to view registration results.
The console has three modes. Mock mode lets the interface work without the pipeline running. Live mode reads results from the frontend API and, in its first version, cross-matches an uploaded image against a reference. A simulated processing mode is planned for later.
Hari implements the backend himself, so the console’s API contract is written down before either side is built. The first implementation surfaced a gap in that contract: every live endpoint is a read, so an upload cannot work until new routes exist.
Source: Implementation notes from the build session.
Screens designed as a design canvas before any code.
React 18 and Vite app with three data-source modes and a single-file build.
Found that the live API is read-only, so live upload needs new backend routes.
No result stated yet.
BUILDING
The console reads a live API; uploads need new backend routes.
Specify and implement upload routes, then build the simulated processing mode.