God’s Eye View: a globe, AI interaction and honest data boundaries
A first God’s Eye View exercise: inspect an environmental layer without confusing display and data
Start keyless, use a bounded environmental view and record source state before drawing conclusions from the globe.
What you will learn
- Start with the smallest useful view
- Check behavior rather than attractive output
- Keep the first exercise keyless and reversible
Before you start
- Basic JavaScript and JSON
- Understanding of coordinates and source timestamps
Explain how source records, validation, layer presentation and optional AI interaction differ, using synthetic examples.
Key takeaways
- One layer makes source behavior easier to inspect.
- Label visibility and record presence are different.
- The displayed earthquake subset has a magnitude filter.
Start with the smallest useful view
The terminal quickstart installs locked dependencies, runs the setup doctor and starts the local app. Choose Environmental or Explore Manually in the first-run panel. Begin with one layer and normal styling so decorative overlays do not obscure the source and its state.
Record the selected layer, source attribution and observation time where supplied. For a synthetic worksheet, include one accepted event and one unknown field. Do not turn a missing timestamp into the current time or substitute a screen position for the original geographic coordinates.
Check behavior rather than attractive output
Toggle the environmental layer and inspect its source explanation. A rendered marker and an ambient label are different presentation elements; label budgets may suppress text even when a record exists. Absence of a label alone therefore does not establish absence of a source event.
The earthquake adapter uses a daily USGS feed and the inspected normalizer keeps magnitudes at or above 2.5. The incoming feed and the displayed subset are not the same population. Describe the filter whenever comparing what the map shows with a provider’s complete list.
Keep the first exercise keyless and reversible
Return to the full globe and normal style when finished. Voice can be evaluated later with a deliberate provider and microphone choice; it is not required to understand the rendering path. Saving a camera view also does not freeze future live source data.
We did not run this interactive exercise. Its acceptance sheet intentionally leaves display and source checks unresolved. The executed evidence is the isolated parsing fixture in the source chapter, not a browser session or validation of current earthquake activity.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Start the documented local keyless path.
- 2
Choose one environmental layer and normal styling.
- 3
Record source, filter and unknown fields.
- 4
Verify display behavior and reset the view.
Copy-ready example
{
"exercise": true,
"layer": "earthquakes",
"sourceWindow": "daily",
"minimumMagnitude": 2.5,
"sourceTimeMs": null,
"visibleLabels": null,
"browserExerciseExecuted": false
}Frequently asked questions
Does a missing label mean the source has no event?
Not necessarily. Presentation budgets can suppress labels.
Must I configure voice before exploring?
No. The README documents a keyless non-voice starting path.
Sources
- God’s Eye View / README.mdSource checked 2026-09-14
- God’s Eye View / src/layers/earthquakes/model.jsSource checked 2026-09-14
- God’s Eye View / src/layers/earthquakes/source.jsSource checked 2026-09-14