Skip to main content

mapv10 captures index

This document is the captures index for the mapv10 viewer. It enumerates every scripted scenario in tools/llm-bundles/captures/mapv10.scenarios.json, groups them by panel, and lists the surfaces that currently have no capture coverage at the bottom. The scenario index is generated from the JSON by sbundle gen captures-md mapv10; the Coverage Gaps section beneath the marker line is hand-written.

How to run captures​

mapv10 captures are dispatched via the viewer-side hook window.__mapv10RunScenario(id), not via DOM selectors in the bundle adapter. The sbundle driver loads the viewer at the configured run URL, waits for loaded: true, then invokes the scenario hook for each entry in the scenarios manifest and writes one PNG per files[] entry.

Drive captures through sbundle:

# Refresh the three mapv10 profiles together.
tools/llm-bundles/target/release/sbundle build mapv10 mapv10-ui mapv10-full-ui

# Refresh a single mapv10 profile.
tools/llm-bundles/target/release/sbundle build mapv10

Re-shoot a single scenario through sbundle capture <profile> <scenario-id> when only one PNG needs to be regenerated.

Continent overview​

  • mapv10_continent_geography_topdown — 01-mapv10_continent_geography_topdown.png — terrain / top-down — Continent zoom in terrain mode with the camera straight overhead. Shows the continent-scale terrain mesh, biome coloring, and global terrain features without political overlays.
  • mapv10_continent_geography_oblique — 02-mapv10_continent_geography_oblique.png — terrain / oblique — Continent zoom in terrain mode with a standard oblique camera. Demonstrates how silhouettes and elevation read once the 3D terrain mesh is viewed off-axis.
  • mapv10_continent_geography_oblique_low — 03-mapv10_continent_geography_oblique_low.png — terrain / low oblique — Low-altitude oblique foothill shot that exposes whether mountains and terrain displacement are real. This is the continent-scale relief proof rather than a map-mode overview.

Continent modes​

  • mapv10_continent_political_topdown — 04-mapv10_continent_political_topdown.png — political / top-down — Continent zoom in political mode with the camera straight overhead. This is the standard strategic ownership view at the largest scale.
  • mapv10_continent_political_oblique — 05-mapv10_continent_political_oblique.png — political / oblique — Continent zoom in political mode with an oblique camera. Shows realm color fills draped over the generated 3D terrain surface.
  • mapv10_continent_routes_topdown — 06-mapv10_continent_routes_topdown.png — routes / top-down — Continent zoom in routes mode from overhead. The base terrain is muted so route-network evidence can be reviewed without losing the continent context.
  • mapv10_continent_height_topdown — 07-mapv10_continent_height_topdown.png — elevation / top-down — Continent zoom rendered through the elevation mode. Validates that the elevation product is sampled coherently across the full run.
  • mapv10_continent_slope_topdown — 08-mapv10_continent_slope_topdown.png — slope / top-down — Continent zoom rendered through the slope mode. Exposes derivative continuity, ridge gradients, and any tile-aligned slope artifacts.
  • mapv10_continent_normals_topdown — 09-mapv10_continent_normals_topdown.png — normals / top-down — Continent zoom rendering encoded normals. Useful for spotting surface-normal discontinuities, quantization, and tile seams in the LOD products.

Semantic zoom bands​

  • mapv10_realm_political_topdown — 10-mapv10_realm_political_topdown.png — realm / political — Realm-tier political view showing how the strategic map partitions below continent scale. Captures political readability and LOD continuity at mid zoom.
  • mapv10_province_political_oblique — 11-mapv10_province_political_oblique.png — province / political oblique — Province-tier oblique political view. Stresses streaming, terrain displacement, and political coloring at the province band.
  • mapv10_location_political_topdown — 12-mapv10_location_political_topdown.png — location / political — Location-tier political view with the camera close enough for individual strategic cells to dominate the viewport. Useful for detail-LOD and LUT regressions.
  • mapv10_scale_ruler_continent — 13-mapv10_scale_ruler_continent.png — scale ruler / continent — Continent-altitude scale-ruler proof. The ruler should report a coarse km value and remain monotonic relative to realm and location ruler shots.
  • mapv10_scale_ruler_realm — 14-mapv10_scale_ruler_realm.png — scale ruler / realm — Realm-altitude scale-ruler proof. The ruler should show a mid-scale km value finer than the continent shot and coarser than the location shot.
  • mapv10_scale_ruler_location — 15-mapv10_scale_ruler_location.png — scale ruler / location — Location-altitude scale-ruler proof. The ruler should show the finest value in the three-shot monotonic sequence while close-detail tiles settle.
  • mapv10_zoom_continent_to_location_clean_lowland — 16-mapv10_zoom_continent_to_location_clean_lowland.png — zoom trace / clean lowland — Scripted zoom trace from continent scale to a clean close-band lowland target. Captures the final frame while the scenario records semantic bands, LOD, scheduler, and cache evidence.
  • mapv10_continent_to_location_slow_network — 17-mapv10_continent_to_location_slow_network.png — zoom trace / delayed products — Scripted continent-to-location zoom with delayed terrain and runtime product requests. Retained as stress evidence for fallback duration and final settled close-detail residency.
  • mapv10_zoom_realm_to_location_overlays_z5 — 18-mapv10_zoom_realm_to_location_overlays_z5.png — zoom trace / overlays — Scripted realm-to-close zoom with borders, routes, and labels enabled. Captures the final close overlay state and preserves trace telemetry for route and label rebuild pressure.

Influence products​

  • mapv10_location_influence_corruption_oblique_z5 — 19-mapv10_location_influence_corruption_oblique_z5.png — influence / close oblique — Close influence-mode view over the deterministic corruption fixture. Proves corruption renders from generated influence truth and runtime sidecars instead of a decorative screen overlay.
  • mapv10_location_geography_corruption_overlay_off_z5 — 20-mapv10_location_geography_corruption_overlay_off_z5.png — terrain / influence hidden — Close terrain view over the corruption fixture with the influence layer disabled. Shows that base terrain remains readable while generated influence truth stays load-required and inspectable.

Hover and inspector​

  • mapv10_hover_selection_location_influence_z5 — 21-mapv10_hover_selection_location_influence_z5.png — interaction / location — Close interaction proof for a Location in influence mode. Hover and selection must emit typed payloads, update selection state, and expose terrain plus influence inspector fields.
  • mapv10_hover_selection_routes_water_features — 22-mapv10_hover_selection_routes_water_features.png — interaction / vector entities — Interaction proof for route, water, and feature entities near the western lake and river network. Confirms that generated vector/raster products drive payloads and emphasis.
  • mapv10_hover_selection_terrain_cell_z6 — 23-mapv10_hover_selection_terrain_cell_z6.png — interaction / terrain cell — Close terrain-cell hover and selection proof. The inspector must expose generated tile/cell, base/effective material, forest/wetland, water, and influence fields.
  • mapv10_empty_click_escape_clear — 24-mapv10_empty_click_escape_clear.png — interaction / clear — Selection and hover clear-behavior proof. Empty click, Escape, and pointer leave must clear through renderer-owned payload state rather than shell-only DOM state.

Visual foundation​

  • mapv10_location_geography_overlays_oblique_z4 — 25-mapv10_location_geography_overlays_oblique_z4.png — terrain / overlays z4 — Close terrain view with borders, routes, and labels enabled at the z4 navigation case. Captures dense overlay readability against terrain relief.
  • mapv10_location_geography_overlays_oblique_z5 — 26-mapv10_location_geography_overlays_oblique_z5.png — terrain / overlays z5 — Very close terrain view with overlays enabled. This is the close-band shot for route width, label density, terrain relief, and seam visibility together.
  • mapv10_location_geography_clean_oblique_z5 — 27-mapv10_location_geography_clean_oblique_z5.png — terrain / clean z5 — Very close terrain-only view with overlays disabled. Isolates terrain material, relief lighting, sidecar residency, and tile seams from route and label clutter.
  • mapv10_location_geography_clean_lowland_oblique_z5 — 28-mapv10_location_geography_clean_lowland_oblique_z5.png — terrain / lowland clean — Close terrain-only view over a lower-elevation lowland target. Proves ordinary close terrain readability without relying on snow, peak tint, or overlay context.
  • mapv10_lod_transition_z4_z5_seam — 29-mapv10_lod_transition_z4_z5_seam.png — terrain / LOD transition — Mid-altitude close-detail transition shot. Captures whether primary tiles, immediate ancestors, and close-detail sidecars remain coherent across LOD boundaries.
  • mapv10_visual_foundation_coast_edge_oblique_z6 — 30-mapv10_visual_foundation_coast_edge_oblique_z6.png — terrain / coast edge — Close oblique coast-edge proof over the western sea mouth. Shows terrain, generated sea water, water-mask sidecars, and water selection ownership in the same frame.
  • mapv10_visual_foundation_lake_edge_oblique_z6 — 31-mapv10_visual_foundation_lake_edge_oblique_z6.png — terrain / lake edge — Close oblique lake-edge proof over the western basin lake. Verifies generated freshwater geometry, terrain shoreline ownership, routes, and inspector payloads.
  • mapv10_visual_foundation_underlay_wireframe_z6 — 32-mapv10_visual_foundation_underlay_wireframe_z6.png — terrain / wireframe underlay — Close wireframe proof focused on resolver ownership. Exposes whether the scene is rendering real close-detail triangulation rather than broad underlay slabs.
  • mapv10_location_geography_wireframe_z5 — 33-mapv10_location_geography_wireframe_z5.png — terrain / wireframe — Close terrain shot with the wireframe layer enabled. Reveals the actual displaced triangulation and whether wireframe is hiding missing primary meshes.
  • mapv10_location_height_z5 — 34-mapv10_location_height_z5.png — elevation / close — Close elevation-mode view with the same residency gates as terrain. Useful for seeing elevation continuity and coarse-underlay plateaus without biome color.

Routes and labels​

  • mapv10_location_routes_oblique_z5 — 35-mapv10_location_routes_oblique_z5.png — routes / close — Very close routes-mode view with borders and labels enabled. Validates local-route density and route emphasis at the same distance as the close terrain audit.
  • mapv10_location_label_uniqueness_z5 — 36-mapv10_location_label_uniqueness_z5.png — labels / close — Close terrain view with labels isolated from route and border clutter. Proves label uniqueness and visible text density in the close semantic band.

M11x coast geometry​

  • shoreline_transition_close_band_lod_policy — 37-shoreline_transition_close_band_lod_policy.png — geography / continent + coast oblique — M11x Wave 9 / Wave 1 — Policy C close-semantic-band shoreline emission proof. Two camera presets verify the LOD policy: (a) continent top-down at ~5000 km altitude exposes the political/geography surface dominated by terrain-land + terrain-seafloor, with no shoreline-transition ribbon geometry visible because every shoreline-transition mesh is on a close-band tile (z6/z7); (b) coast oblique at ~70 km altitude over a mixed-coast tile lands the camera at a close-band primary where the shoreline-transition ribbon is the only mesh that crosses the mean-sea-level isoline along a coast. The boundaryIdsCrossReference gate cross-checks the per-LOD coast BoundaryId ownership invariant — every coast BoundaryId is owned by exactly one terrain-land asset (total) and exactly one shoreline-transition asset per emitting close-band z.

Coverage gaps​

The following viewer surfaces are not exercised by any scenario in mapv10.scenarios.json today. They are intentionally listed here so future waves can decide whether to add scripted coverage or accept the gap.

  • Loading Panel — no captures. The run-load progress, error, and retry states are never exercised in isolation.
  • Stream Panel — no captures. The tile-streaming HUD is never exercised in isolation.
  • Debug Drawer (Products button) — no captures. The generated-products inspector drawer is never opened by a scenario.
  • Performance HUD (F3) — no captures. The F3 telemetry HUD is never exercised.
  • Markers layer dedicated scenario — currently only exercised as a side effect of mapv10_hover_selection_routes_water_features. No dedicated marker-only capture exists.
  • Right-click drag-to-pan (OrbitControls default) — no scenario verifies that right-button drag pans the camera. The native browser context menu is suppressed on the canvas so the right-button gesture is unambiguous, but the affordance is unproved end-to-end.
  • State-field overlay (Overlay slider) — no captures. The state-field overlay producer is currently unwired, so the Overlay slider always renders empty; a capture wave is deferred until the producer ships.