Knowledge RAG

Design Knowledge Base

Community-maintained principles reviewed before publication and retrieved as Agent design constraints.

3 published principles / 192 in library

Map POI Icon Attribution Boundaries

POI icon sets such as Maki solve map symbols, not map data, tiles, style, basemap providers, place labels, or interaction attribution.

Map symbols are one layer of visual encoding. Agents must govern icon set, sprite, map style, geodata, tile provider, legend, and accessible labels separately instead of treating icon license as map license.

95%Data Visualizationmaps / geospatial

Map Data Attribution and Alternatives

Map interfaces must separately record runtime library, tiles, styles, glyphs, sprites, geodata, and provider attribution, while providing list/table alternatives and keyboard-reachable paths.

A map is not a background image. It combines complex data visualization, interactive controls, and licensed materials; users must understand location, scope, selected object, data source, update time, and alternate access paths.

95%Resource Licensingattribution / license

Asset Attribution Surface Contract

License metadata should not live only in the catalog. CC BY, custom-licensed maps, photos, illustrations, Lottie files, and similar assets need readable, nearby, traceable attribution, license links, change notes, and commercial-use risk in the UI, export, or source notes.

Attribution is part of interface information architecture, not only an asset-catalog field. Any resource whose license requires credit needs a surface that users can find, reviewers can audit, and agents can trace.

95%