untouchedin progressdone and verified
Component rollup
| Component | Done | Partial | Open |
|---|---|---|---|
build | 2 | 0 | 0 |
catalog | 1 | 0 | 0 |
docs | 5 | 1 | 1 |
feeds | 4 | 0 | 5 |
globe | 1 | 0 | 1 |
keys | 2 | 0 | 0 |
oauth | 1 | 0 | 0 |
repo | 4 | 0 | 0 |
server | 2 | 0 | 1 |
tests | 1 | 0 | 0 |
textile | 4 | 0 | 2 |
ui | 1 | 0 | 2 |
voice | 1 | 0 | 3 |
How the pieces connect
The source repository holds everything. Build and setup installs and bundles it. The local server reads the provider keys and forwards requests to outside services, so keys never reach the browser. Live feeds (ships, fires, weather) arrive through that server. The textile datasets are static files shipped with the code. Both feed the layer catalog, which the layer panel lists and the 3D globe draws. Voice control calls the same catalog through a short list of allowed actions and signs in through the ChatGPT sign-in. The test suite guards all of it, and the two documents describe it.