@tileflow/maps 0.1.0-alpha.0 → 0.1.0-alpha.10

package/README.md

@@ -1,175 +1,334 @@
-# `@tileflow/maps`
+# @tileflow/maps
 
-Official Tileflow maps and the assets they own.
+Official Tileflow maps with their icon, pattern, and font assets. Extend a map with
+`@tileflow/core`; render its prepared output with a framework adapter or MapLibre.
+
+> Related packages and guides: [documentation index](https://raw.githubusercontent.com/tileflow/tileflow-sdk/main/llms.txt).
+
+## Install
+
+```sh
+npm install @tileflow/maps@alpha @tileflow/core@alpha
+```
+
+Core is a peer dependency: it owns the map language and compiler. This package owns map definitions
+and assets. It does not include a tile archive, a browser renderer, or a hosted service subscription.
+
+## Use an official map
+
+Create `tileflow.config.ts`:
+
+<!-- docs:check -->
 
 ```ts
 import {defineMap} from '@tileflow/core';
 import {streets} from '@tileflow/maps';
 
 export default defineMap({
-  id: 'main',
+  id: 'madrid',
+  name: 'Madrid',
   version: 1,
   extends: streets,
   defaultTheme: 'dark',
+  view: {center: [-3.7038, 40.4168], zoom: 12},
 });
 ```
 
-This still inherits both Streets themes; it changes only which concrete theme is selected by
-default.
+This inherits Streets' themes and changes only the default selection and initial view.
+Coordinates are `[longitude, latitude]`. To preview it:
+
+```sh
+npm install --save-dev --save-exact tileflow@alpha
+npx tileflow validate
+npx tileflow preview
+```
+
+Rendering can request remote tiles, glyphs, or terrain. Installing the package does not make those
+resources available offline.
+
+### Develop Streets in an SDK checkout
+
+After installing and building this workspace, run from its root:
+
+```sh
+node packages/cli/dist/index.js preview --config packages/maps/tileflow.config.ts
+```
+
+Open `http://127.0.0.1:3333`. Source edits reload in Map DevTools without publishing.
+Add `--scene nyc` for New York or `--against-theme dark --map streets-workbench` to compare themes.
+The CLI owns the interface; compiler and runtime changes require rebuilding those packages.
+
+## Choose a map
+
+- `streets`: contemporary street cartography with Mapbox-inspired time-of-day and color themes,
+  ranked POIs, generic road-reference shields, and regional hillshade.
+- `baedeker`: warm travel-atlas styling, serif labels, original engraved patterns, and contours.
+- `civica`: illustrated civic-print styling with warm paper, olive parks, blue annotations, and
+  vermilion landmarks.
+- [`map1777` (1777)](docs/map-1777.md): 1777 ink and watercolor on current data, with 3D and four times of day.
+- `siegfried`: a terrain atlas with coordinated light/dark ink palettes, contours, and engraved patterns.
+- `soundings`: bathymetric reference cartography with depth bands, continuous relief, and port context.
+- `blueprint`: a dark architectural drawing style, with a default camera centered on San Francisco.
+
+Every official map is a complete, independent root using the same Core compiler. Official map
+objects are deeply frozen shared instances. Do not mutate them; use `defineMap({extends: ...})`
+to create an application-owned map.
 
-Every export is an ordinary Tileflow map and a complete first-party compiler root. No official map
-imports or extends another official map; each declares its data, modules, effects, themes, and asset
-providers directly. Applications can still use the public `extends` contract to derive their own
-maps from any official root. Streets and Siegfried each contain structurally identical `light` and
-`dark` appearances.
+### Streets appearance
 
-The official map objects are deeply frozen package singletons so one consumer cannot mutate
-the definition seen by another. This does not change Core authoring: `defineMap(...)` still returns
-the application-owned object without freezing it, and an application extends an official map by
-declaring its own modules or other atomic overrides.
+Streets follows the visual direction of [Mapbox Standard](https://docs.mapbox.com/playground/standard-style/)
+(twelve theme/time combinations), calibrated on 2026-10-18. DevTools offers **Default**, **Faded**, and
+**Monochrome** in its Theme control, independently of the Time of day control's `day`, `dawn`,
+`dusk`, and `night` presets. Each of the twelve combinations selects a complete theme, including
+its map colors and artwork. Default retains the configuration key `light` for compatibility:
+`theme="light" timeOfDay="night"` selects `dark`, while `theme="light" timeOfDay="day"`
+selects `light`. The other concrete themes are `dawn`, `dusk`, `faded`, `monochrome`,
+`dawn-faded`, `dawn-monochrome`, `dusk-faded`, `dusk-monochrome`, `dark-faded`, and
+`dark-monochrome`. Dawn and day use light artwork; dusk and night use dark artwork. Time presets
+adjust authored map colors; selecting one does not apply a global lighting tint to the flat map.
+Ground, water, vegetation, roads, zoning, labels and halos use independently evaluated colors
+from Standard's 2026-10-08 style, including each material's theme LUT, lighting, emission and
+transparency. Ground colors are checked against sRGB framebuffer samples from Mapbox GL JS
+3.28.1 across all twelve combinations; footprints and 3D roofs use separate GPU measurements.
+Water retains its own material and zoom 5–7 / 13–14 transitions; it no longer inherits a
+swimming pool's color offset. Background emission changes between zoom 13 and 14. These values
+are baked into theme tokens, so they add no lighting or LUT work per frame.
+Scene-sun lighting preserves unshadowed roof paint while allowing light color to affect walls.
+The underlying tile data and rendering pipeline differ, so these are close palette matches rather
+than a pixel-identical copy. Streets' own semantic design retains slate-blue
+roads, uppercase road names, warm building footprints, green parks, and compact category-colored
+POI discs. Dark mode uses pale discs with dark pictograms. Pictograms adapted from Maki follow
+World's transport mode and POI type: metro, rail, tram, bus, ferry, cable-car, and airport stations
+are distinct, as are bars, cafés, museums, galleries, car dealers, and places of worship by
+religion.
+
+The reference uses DIN Pro Medium for POIs, roads, major settlements, and districts.
+Streets uses hosted Noto Sans Regular for these roles: Noto Sans Bold makes their strokes and
+word widths too heavy at the reference's sizes. Bold is reserved for administrative regions and
+road shields; water labels keep Italic. This is a visual approximation, not a bundled DIN face.
+POI discs use vivid category colors, 20px containers, and fixed native icon scale at every zoom.
+Maki's 15px artwork is composed into a centered 12px box, leaving room inside the 17px colored
+interior. Their 1x and 2x atlases rasterize these SVG compositions separately; the map displays
+each complete icon at native scale instead of rescaling the bitmap as the zoom changes.
+
+The light surface palette is compared with lossless captures of Standard with 3D buildings and
+trees disabled. Parks use a stronger green with lighter lawns and meadows drawn above them;
+flat buildings use a neutral cream. City roads keep the same slate-blue family through the
+z14–z15 transition, with blue borders and translucent tunnels. Road widths retain their hierarchy.
+Road carriageways follow the reference's exponential zoom curves (base 1.5), including
+fractional zooms. Motorways and trunks start at z3, primary roads at z6, secondary and tertiary
+roads at z8, streets and links at z12, and service roads at z15. Surface casings begin at z15
+(z16 for service roads and tracks); they grow from a fine edge independently of the matching
+carriageway gap. This keeps regional views light while preserving detail at street zooms.
+Motorway and trunk links retain their class colors and narrower widths. On the surface and on
+bridges, their fills draw before the receiving carriageways so overlapping round endpoints do
+not leave a contrasting patch over a junction. Tunnels keep their separate treatment.
+Surface and bridge casings are continuous; tunnel casings are dashed. Construction carriageway
+fills and marks draw below roads in service, including motorway ramps.
+Borders use Standard's 2026-10-08 style, theme LUTs and unshadowed ground lighting, without
+carriageway emissive lift. HD-road borders match across classes, bridges, tunnels and roundabouts
+from z15; lower-zoom tunnels retain class colors. Paths keep separate emission. Streets uses the reference border colors without an additional darkening multiplier. These baked
+2D colors exclude fog and Standard's full lighting pipeline.
+Surface caps become round at z14; tunnels retain butt caps and bridges use round fills.
+The road regression checks every quarter zoom from 0 through 24 and both sides of the handoffs.
+Crosswalks and one-way arrows fade in from z16.5 so city-scale roads retain their surface color.
+From z13, pedestrian plazas use an opaque pale surface above commercial zoning and below
+explicit grass, gardens and parks. The `roads.pedestrian.surface` token follows the ground's
+theme and time of day. From z17, mapped sidewalks add a translucent tint and dot pattern through
+`roads.sidewalk.surface`, preserving the underlying ground color.
+Mapped parking polygons use an opaque neutral fill above overlapping vegetation and below
+roads. This requires a `landuse` polygon classified as `parking`; parking POIs and aisle lines
+alone do not provide the boundary needed to fill the surface.
+Hedges (from z15, shaded from z17), fences and walls (from z16) come from `traffic_control`.
+
+Ferry routes fade in from z8, use fine blue dashes from z13, and show uppercase route names
+along the line from z15 when the data includes them. Their labels use a water-colored halo.
+
+Regional hillshade uses [Mapzen Terrain Tiles on AWS](https://registry.opendata.aws/terrain-tiles/)
+from z5 through z13, with source attribution. The 256-pixel Terrarium source is capped at native z12;
+closer views reuse that resolution, avoiding requests for coverage-dependent high-resolution DEM tiles. This is an additional remote data request. To omit
+it, set `terrain: 'none'` in a map extending `streets`. Hillshade does not change road geometry or
+raise the terrain. Buildings appear automatically from zoom 15 with an opacity fade through 15.25;
+the preview's **3D** control can hide them, and its **Trees** control enables vegetation.
+Road shields and exit references use 10 px text. Category text and halos follow the reference's
+emission and palette without a separate contrast recoloring step; marker artwork retains its
+own colors.
+3D lights use Standard's effective theme presets, retrieved on 2026-10-18: southern sun by day,
+southeast at dawn, southwest at dusk and western moonlight at night. Monochrome has distinct
+directions and strengths. Tileflow holds zoom 14+ values; Standard varies intensity below z14.
+Shading differs; `controller.setSun({date, location})` uses the real sun instead of presets.
+The buildings' `threeDimensional.lighting` and `shadows` options control the effect, and each
+theme's `lighting.sun.shadowIntensity` and `lighting.ambient` control its strength.
+Street lights are opt-in: set `roads.streetLights.enabled: true`.
+Core's 3D renderer
+adds a soft ten-percent shade at the foot of the facades, fading within the lowest three metres
+(less on low buildings). Exterior corners have a 0.8 m radius and the roof/wall junction has a narrow
+lighting transition; roofs keep their authored colour. Streets enables soft three-metre contact
+shadows without dark overlaps; `buildings.threeDimensional.occlusion: false` disables them.
+Core replaces the extrusion fallback's blurred bands, styled by `buildings.contactShadow`.
+Streets selects Core's `labels.roadPlacement: 'ground'`: street names follow the road plane below
+buildings; POIs, transit names and shields remain above. Disabling roads omits their names.
+Road rings, ramp and surface ordering use [Core's replaceable defaults](../core/docs/cartographic-defaults.md).
+Streets owns its colors, widths, typography and optional time-of-day themes.
+Browser atmosphere is separately enabled with `atmosphere: true` on a globe map; the base definition
+also remains usable with Mercator and native targets.
+
+Streets enables model trees by default (`mode: '3d'`, `fallback: 'none'`). They stay three-dimensional
+in overhead and tilted interactive browser views. Disabling vegetation removes all trees. Renderers
+without model support omit them. Extensions can opt into the included flat crown artwork with
+`vegetation: refine({mode: 'flat'})`, or switch it with explicit view mode using `mode: 'auto'`.
+Seven original forms cover rounded, spreading and upright broadleaf trees, conifers, columns,
+feather palms and fan palms. Their light/dark crown images come from the same geometry as the
+models. Broadleaf trees have flared trunks, visible forks and separated crown clusters, with
+both compact and open silhouettes. This artwork does not change the map's lighting.
+
+All twelve presets independently style bark and crowns from tilted Standard samples, preserving
+geometry. Mesh and lighting differences prevent identical pixels.
+
+The models have 120–386 triangles nearby and 44–96 at distance. They reuse Core's instanced tree
+renderer; flat crowns use the existing sprite atlas. Tree locations and attributes still come
+from the source tiles. The artwork does not add trees to parks whose data has none. See
+[3D trees](https://github.com/tileflow/tileflow-sdk/blob/main/packages/core/docs/trees-3d.md) for
+browser rendering and platform support. To remove both representations, extend the map:
+
+<!-- docs:check -->
 
 ```ts
-import {
-  cyberpunk,
-  cyberpunkFonts,
-  cyberpunkIcons,
-  ferraris,
-  ferrarisIcons,
-  harad,
-  haradIcons,
-  matrix,
-  matrixFonts,
-  matrixIcons,
-  siegfried,
-  siegfriedFonts,
-  siegfriedIcons,
-  siegfriedThemes,
-  soundings,
-  soundingsIcons,
-  streets,
-  streetsIcons,
-  streetsThemes,
-  verdant,
-  verdantIcons,
-} from '@tileflow/maps';
+import {defineMap, disable} from '@tileflow/core';
+import {streets} from '@tileflow/maps';
+
+export default defineMap({
+  id: 'streets-without-trees',
+  version: 1,
+  extends: streets,
+  modules: {vegetation: disable()},
+});
 ```
 
-`ferraris` is a self-contained printed-atlas design. It uses Core's semantic Streets compiler, but
-it does not import or extend the `streets` map and it does not inherit Streets assets. It declares
-only `[ferrarisIcons]`, which contains nine original seamless SVG patterns for paper, cultivated
-land, vegetation, settlements, sand, wetlands, and water. Applications can import it directly or
-extend it like any other root.
-
-`harad` is a self-contained historical green-map design named “Härad”. It uses Core's semantic
-Streets compiler ABI without importing or extending the `streets` map or reusing any Streets asset.
-It declares only `[haradIcons]`, whose nine original Tileflow SVG patterns describe arable land,
-coniferous and deciduous woodland, orchards, paper grain, sand, settlements, water lines, and
-wetlands. The visual grammar is inspired by Lantmäteriet's CC0 Häradsekonomiska kartan series
-(1859–1934) and official legend. The package redistributes no Lantmäteriet scan, source pixel, legend
-artwork, font, or map data; the shipped style and SVG patterns are original Tileflow work.
-
-`soundings` is a self-contained bathymetric-chart design with ivory land, thirteen-stop
-depth-graded water, labelled band edges, continuous colour relief, multidirectional seabed shading,
-port context, named ferry routes, and restrained technical magenta. Its initial camera faces the
-Strait of Gibraltar, allowing an Iberian GEBCO pilot to exercise both Atlantic and Mediterranean
-relief. It selects the public semantic compiler contract without importing or extending `streets`
-and explicitly composes World with `bathymetry({display: 'hybrid'})` while setting Nautical to
-`false`.
-
-Vector bands come from `tileflow-bathymetry`; continuous colour relief and hillshade come from
-`tileflow-bathymetry-dem`. The stronger DEM treatment is balanced against the vector wash and depth
-labels rather than against experimental navigation symbols. Dashed outlines remain an honest
-fallback traced from broad GEBCO band polygons until native contour geometry is released. Labels
-show the absolute `min_depth` value, not an inferred range or vessel-specific safety contour.
-Harbours and ferries are ordinary World context. Experimental `nautical-v1` tiles, aids, lights,
-soundings, hazards, reefs, and wrecks are deliberately absent from the official map and remain
-available only to explicitly configured laboratory maps. Soundings is reference cartography and is
-not a navigation product.
-
-`siegfried` is a self-contained terrain atlas based on the visual grammar documented for
-swisstopo's nineteenth-century Siegfried Map. It does not import or extend `streets`. The default
-`light` theme preserves black, brown, blue, and an ivory paper substrate; browser-derived contours
-replace modern hillshade and retain the 30-metre Alpine cadence at detailed zooms. Rock and scree
-are re-engraved in key ink after the contour deck, while dedicated SVG motifs distinguish forest,
-glacier, wetland, gravel, orchard, and water. Its coordinated `dark` theme is explicitly a nocturnal
-engraver's proof, not a historical facsimile: it keeps identical geometry and semantic ink roles on
-charcoal paper. `[siegfriedIcons]` owns nine light and nine dark pattern variants,
-`[siegfriedFonts]` owns the locally packaged Cormorant Garamond Regular, SemiBold, and Italic faces,
-and `[siegfriedThemes]` exposes the two complete visual vocabularies for safe derivation.
-
-`verdant` is a self-contained contemporary field-atlas design. It combines a park-map information
-hierarchy with a cool mineral substrate, clean blue hydrography, graphite buildings, and a
-trail-forward accent; its original botanical textures appear only where detailed zooms make them
-useful. It uses the same semantic compiler contract without importing or extending `streets`,
-declares its own Noto Sans glyph provider, and owns its complete icon and pattern set through
-`[verdantIcons]`.
-
-`cyberpunk` is a self-contained dark HUD root. Its road hierarchy, building signals, destination
-beacons, planar effects, semantic theme, World data selection, `[cyberpunkIcons]`, and
-`[cyberpunkFonts]` are all declared directly; it does not import or extend `streets`.
-
-`matrix` is a self-contained monochrome green-screen root. It explicitly owns its sparse HUD
-geometry, reviewed phosphor-green ramp, modules, effects, theme, and Matrix-prefixed layer IDs. It
-omits a bright road centerline and building circuit texture, and uses compact square destination
-nodes through `[matrixIcons]`. A translucent scanline and dot pattern masks the cartographic
-linework so bright strokes break into the phosphor rows of an old CRT without baking that texture
-into the map data; text layers render afterwards and stay crisp. `[matrixFonts]` owns Matrix's
-packaged Oxanium faces for uppercase labels, independently of Cyberpunk's font provider.
-
-`streetsThemes.light` and `streetsThemes.dark` are complete appearance documents consumed by the
-same Streets module recipe. Selecting `dark` changes colors, typography roles, image roles, and
-lighting without changing a source, filter, layer order, zoom gate, collision rule, or module. Both
-sidewalk patterns live in the shared `[streetsIcons]` atlas and the selected theme resolves the
-semantic `roads.sidewalkPattern` image token to the correct asset.
-
-Streets uses one ranked destination hierarchy in both themes. Major transit and cultural anchors
-appear first; lodging, health, education, services, shopping, food, coffee, and parking enter
-progressively as the camera approaches street level. Each visible destination is one collision
-unit made from a colored circular pictogram and an optional neutral name, so the marker remains
-useful when the label cannot fit. Portal-number labels are intentionally disabled. The ten POI
-pictograms are adapted from the pinned CC0 Maki subset documented in
-`THIRD_PARTY_NOTICES.md`; their containers, colors, sizing, and composition are Tileflow-authored.
-
-Road references use a compact Tileflow-owned family of generic rectangular and circular shields.
-The data's normalized `shield_kind` selects neutral, blue, green, red, orange, yellow, or circular
-artwork; `shield_text_color` independently selects the light or dark theme token. Unknown and
-unsupported networks fall back to the neutral rectangle with dark text instead of guessing a
-country from the spelling of `ref`. Both themes retain the same signaling colors.
-
-Streets has separate shield phases for scale, not separate hand-authored network layers. Overview
-uses pre-deduplicated point candidates; detail switches to repeated line placement. Both the fitted
-plate and its complete route reference are viewport-aligned, so shields remain horizontal as the
-map rotates or pitches. The rectangular base plate is 20 by 14 pixels with a one-pixel outline;
-the circular neutral base is 14 by 14. Both use 9-pixel bold text and a small width-only fit
-allowance. Streets limits shields to the motorway-through-tertiary hierarchy; collision padding
-and the overview candidate schedule keep regional views legible while preserving useful repetition
-at street scale.
-
-The two palettes are Tileflow-owned, deterministic snapshots calibrated from rendered Mapbox
-Standard `default/day` and `default/night` references on 2026-08-27. They do not import Mapbox style
-JSON, rules, assets, or runtime dependencies. Public roles such as `surface.background`,
-`landuse.industrial`, `landuse.medical`, `labels.settlement`, `labels.neighborhood`, and
-`labels.road` remain independently wired; `hydro.ocean` also separates Standard Night's deep sea
-from urban and inland water. An agent can alter one cartographic intent without
-knowing or perturbing the physical layer topology. Because Standard is evergreen, later parity work
-must be an explicit dated recalibration rather than an implicit network-dependent change.
-
-At detailed zooms, the road-bearing official maps round-cap ordinary surface-road and bridge
-feature endpoints so adjacent vector segments overlap their antialiasing fringe instead of exposing
-hairline cuts. Tunnel portals retain butt caps; Streets, Cyberpunk, and Matrix also keep butt caps on
-steps and approaches carrying circular-road clearance so those structural ends do not protrude into
-the connected geometry. Streets pairs its blue/slate road decks with a darker casing that grows from
-1 px at z15 to 2 px at z22; tunnel casings use the compact dashed rhythm of the calibrated reference.
-
-A theme is not a loose override cascade. Module styles explicitly reference roles such as
-`roads.motorway`, `labels.road`, and `hydro.water`; the selected complete theme resolves those
-references before MapLibre output is generated. Use `defaultTheme` for a deterministic default and
-`systemThemes` plus the runtime `theme="system"` selection when the browser should follow the OS.
-
-The directory descriptors point into this installed package. A map inherits its parent's icon or
-font list when the property is omitted. Declaring a list replaces the inherited list, a later
-directory wins for an exact duplicate ID, and `[]` selects no directories.
-
-`@tileflow/maps` has a peer dependency on `@tileflow/core`. Core owns the map language and compiler;
-this package owns the official map definitions, icon and pattern sources, Cyberpunk, Matrix, and
-Siegfried fonts, and their notices. Core never depends on this package.
+POI categories use World eligibility and ranks at one density and are placed in one importance
+order, so a category never displaces a more important place of another category. World's two most
+important ranks are placed before street and place names. Each disc needs its name; parking and
+toilets appear as a disc alone, and other unnamed POIs are omitted.
+Ordinary POI and transit names use 13 px lettering, with 18 px for the highest-priority destinations.
+World's size ranks differ from the reference, so a small park with size rank zero does not become
+a large destination label by that value alone. Text padding falls from 6 px to 4 px between z16
+and z17, and collision determines which names fit.
+
+City labels hand over at z15, smaller settlements at z13, and districts at z15. Co-located city
+candidates share one anchor to prevent duplicate names at world scale. Districts retain an overview
+rank gate below z12; from z12 onward, source availability and collisions control their appearance
+because World ranks can change between tile zooms. Street names use 0.15 em letter spacing and
+a 1 px halo; administrative regions use bold lettering and water names use italic lettering.
+House numbers appear from z17 with wide collision padding. Local-language labels remain the default.
+
+The map uses Tileflow data and assets, including hosted Noto Sans Regular, Bold, and Italic. The
+reference's DIN Pro Medium is not part of that glyph provider, so font shapes and stroke weight
+remain an approximation. Available POIs, abbreviated names,
+proprietary landmark models, transit branding, and building detail can differ from the reference.
+See [map design and asset provenance](https://github.com/tileflow/tileflow-sdk/blob/main/packages/maps/docs/design-and-assets.md).
+
+### Blueprint naming
+
+Use `blueprint` and `blueprintIcons` for the architectural drawing map. Its map ID and
+asset directory are `blueprint`, its theme key is `blueprint`, its theme ID is `blueprint-dark`,
+and its grid artwork ID is `blueprint-grid`.
+
+<!-- docs:check -->
+
+```ts
+import {defineMap} from '@tileflow/core';
+import {blueprint} from '@tileflow/maps';
+
+export default defineMap({
+  id: 'city-plan',
+  version: 1,
+  extends: blueprint,
+  view: {center: [-3.7038, 40.4168], zoom: 14},
+});
+```
+
+### Community maps
+
+Cyberpunk, Terminal, and Super Tile World are maintained in
+[Tileflow Community Maps](https://github.com/tileflow/community-maps), with editable source,
+assets, previews, and contribution instructions. They are not part of this package.
+The GitHub-distributed `@tileflow/community-maps` package exports `cyberpunk`, `terminal`, and
+`superTileWorld`, plus each map's font and icon descriptors. Install an exact Git commit using
+the instructions and compatible Core version in that repository.
+
+Soundings is not a navigation product. Its depth-band edges are approximate reference geometry,
+not surveyed isolines or vessel-specific safety contours. Experimental nautical aids and hazards
+are not enabled by that official map.
+
+## Themes and assets
+
+`streetsThemes` and `siegfriedThemes` expose complete `light` and `dark` themes. Import those
+collections when using `defineTheme()` to derive a new appearance. A declared `themes` collection
+replaces the inherited collection, so also declare the intended `defaultTheme` and `systemThemes`
+and optional `timeOfDay` mappings. `system` belongs to browser selection; captures and builds use concrete theme names.
+
+Every map exports an icon-directory descriptor: `streetsIcons`, `baedekerIcons`, `civicaIcons`,
+`map1777Icons`, `siegfriedIcons`, `soundingsIcons`, and `blueprintIcons`. The descriptors point into this installed package; they are not sprite URLs.
+The CLI and build integrations compile the selected directories into runtime assets.
+
+Baedeker, 1777 and Siegfried export `baedekerFonts`, `map1777Fonts` and `siegfriedFonts` for
+their packaged Cormorant Garamond faces.
+Cívica exports `civicaFonts` for DM Serif Text, Barlow Semi Condensed, and Noto Sans fallback.
+Streets, Soundings, and Blueprint declare Noto Sans URL glyph providers
+from one immutable Hosted base-asset set, versioned independently of World data.
+
+Omitting `icons` inherits the parent's directory list. Declaring a list replaces it; `[]` removes
+all icon directories. Compose explicitly when adding application icons:
+
+<!-- docs:check -->
+
+```ts
+import {defineMap} from '@tileflow/core';
+import {streets, streetsIcons} from '@tileflow/maps';
+
+export default defineMap({
+  id: 'store-locator',
+  version: 1,
+  extends: streets,
+  icons: [streetsIcons, './icons'],
+});
+```
+
+Create `icons/` beside the config and add supported image files before building. Later directories
+replace earlier files with the same exact icon ID. Fonts follow the same ordered-directory model;
+`fonts` and `glyphs` are mutually exclusive providers.
+
+## Delivery and attribution
+
+Use the CLI or a build integration to prepare a map's complete asset set. Copying Style JSON alone
+can leave missing sprites, font files, or browser protocols. Keep the generated manifest and its
+referenced files together.
+
+Hosted deployment currently requires Tileflow World and rejects local/package font bundles before
+uploading a style. Maps with packaged fonts therefore need self-hosted delivery or an explicitly
+replaced, compatible public glyph provider. Check with `tileflow validate --target hosted` before
+planning a hosted deployment.
+
+Tileflow-owned designs and artwork use Apache-2.0. Historical inspiration does not mean the package
+redistributes historical scans, source cartography, or data. Third-party fonts and the pinned Maki
+icon subset retain their own terms. Preserve
+[THIRD_PARTY_NOTICES.md](https://github.com/tileflow/tileflow-sdk/blob/main/packages/maps/THIRD_PARTY_NOTICES.md)
+and the notices next to packaged assets. Map data and terrain services have separate attribution
+and usage requirements.
+
+See the [Core guide](https://github.com/tileflow/tileflow-sdk/blob/main/packages/core/README.md)
+for inheritance and styling, or the
+[public exports](https://github.com/tileflow/tileflow-sdk/blob/main/packages/maps/src/index.ts)
+for exact names. The installed package's definitions and README take precedence over a newer `main`.
+
+## Design and asset reference
+
+The [design and asset notes](https://github.com/tileflow/tileflow-sdk/blob/main/packages/maps/docs/design-and-assets.md) describe each map's visual grammar, source references, and third-party asset boundaries. They are also included under
+`docs/` in the installed package.
+
+Streets offers three time-of-day families: `light` (displayed as Default), `faded`, and `monochrome`, each with
+`day`, `dawn`, `dusk`, and `night`. For example, `theme="faded" timeOfDay="night"` resolves to
+`dark-faded`. DevTools shows these as separate Theme and Time of day controls. All twelve
+concrete theme names remain available for existing applications and captures. This catalog
+is inherited when extending Streets without overriding it.
+See the [time-of-day contract](https://github.com/tileflow/tileflow-sdk/blob/main/packages/core/README.md#style-with-themes-and-semantic-modules).