Brand-family swatch
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- fix(brand-family-swatch): correct article to stop implying GIS-specific taxonomy — component defaults are baseline placeholders, GIS supplies its own real taxonomy as one reference deployment
- brand-family-swatch: redact 2 R1 exact-threshold exposures (zoom level, cluster density); category-placement decision made — stays in design-system (best fit, no move)
- editorial(design-system): resolve brand-family-swatch's standing 2026-08-02 flag (Track-B) — confirmed against dtcg-vault/components/brand-family-swatch/recipe.json: dot size is hardcoded inline CSS (10px default, 24px marker), no ps.swatch.dot.size token exists; real token references are semantic.ink-primary/ink-secondary + primitive.space.05/radius.sm; the 3 brand-family color values were already accurate; dropped the Correction-narration wrapper, stated facts directly per register-documentation.yaml; fixed the same 12px claim in the ES pair, which hadn't been flagged at all; register-clean EN+ES
- fix(index-group): backfill index_group across 11 categories migrated to Index Topic (330 files)
- fix(design-system): add dated Correction callouts to 12 of 15 design-system/ articles — fabricated --ps-* CSS variable family across 3 articles, stale token counts across 3 more, a shipped-then-removed MCP endpoint, and a WCAG AAA overclaim already corrected once in the real source; 3 verified clean
- content(gis): GIS/location-intelligence cluster consolidation (final of 5 flagged clusters) — merged the one genuine duplicate (pointsav-gis-engine.md into location-intelligence-substrate.md; its own body said its core logic lives in app-orchestration-gis). More significant: found and fixed a corpus-wide wikilink collision — 7 articles cited [[co-location-methodology]] as the retail-cluster tier-scoring methodology, but that slug resolves to a real, unrelated article about data-center FACILITY co-location siting. No article for the real retail methodology existed under any slug, and the one place a scoring mechanism WAS described in detail (app-orchestration-gis.md) described a Haversine formula the real SCORING-METHODOLOGY.md V3 confirms was replaced by a 4-tier gate system — with 2 more articles describing the mechanism differently again, none matching each other or reality. Created substrate/retail-co-location-tier-methodology.md as the single source of truth (facts from the verified real methodology doc) and repointed all 7 citing articles (14 files EN+ES) to it. Fixed architecture/_index.md's MOC description, which had also mischaracterized the real co-location-methodology.md article. All content-matrix clusters now resolved.
- fix(frontmatter): short_description band-fit to house style (120-180 chars) — ai/, applications/, design-system/, governance/
- feat(media-knowledge-documentation): add content_type field to all TOPIC + GUIDE files
- enrich wikilinks: documentation design-system body (EN+ES) batch 3
- content(quality-pass): institution POV elevation — 97 articles updated, 32 new from drafts-outbound
- editorial(lint): banned-vocab sweep + tier-a-verified claim fix
- fix(design-system): E3 — add status: active to brand-family-swatch + brand-typography pairs (old schema missing field)
- docs(content-wiki-documentation): D-items sprint — short_description added to all 162 EN+ES wiki articles
- editorial: Phase A2+A3 — title normalisation (169 files) + wikilink backslash fix (20 files)
- docs(design-system): delink 22 stale wikilinks to moved design-system articles
- sweep 2j batch 4: design-system/ EN+ES vocab scrub — Foundry/Doctrine removed
- docs(2g): corpus-wide mechanical quality pass
- merge: integrate origin/main (taxonomy ratification + category-balance + schema-scrub commits) before project-knowledge Stage 6 promote
- Category-balance pass 2: 11 design-system articles re-categorized reference/ → design-system/