Location intelligence substrate
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- docs(documentation): rename fabricated osc-sn-51-721 citation ID to np-51-201 workspace-wide -- following Command's citations.yaml fix (commit c6be400, real workspace-wide OSC SN 51-721 sweep), this wiki's citation ID and ~59 prose/frontmatter references to the fabricated Ontario-specific staff notice were left dangling; renamed to the real CSA National Policy 51-201 entry Command's fix established, matching the same instrument corporate wiki's dad5b0a fix now cites. Mechanical ID rename + prose phrase swap only, no new claims (EN+ES, 61 files).
- editorial(substrate): resolve location-intelligence-substrate's standing 2026-08-02 flag (Track-B) — confirmed service-parking has zero trace anywhere; confirmed service-business/service-places are real only as project-gis Python data-pipeline directory conventions, not Rust Ring 1 services; reframed the record shape as an internal pipeline schema rather than a public service contract per public-repo-safety-review.md precedent (same treatment as service-business-clustering/service-places-filtering); fixed the See-also line's false Ring-1-services claim; register-clean EN+ES
- fix(index-group): backfill index_group across 11 categories migrated to Index Topic (330 files)
- docs(substrate): fidelity sweep — 21 of 40 articles defective, verified against canonical origin/main; fabricated service-disclosure/service-parking/slm-cli, wrong Tier A model + DPO/SFT + KV-cache-federation claims, understated moonshot-sel4-vmm progress, retired-engine route surface, stale versions
- 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) — substrate/
- fix(frontmatter): correct references: YAML indentation across 72 documentation articles
- feat(media-knowledge-documentation): add content_type field to all TOPIC + GUIDE files
- enrich wikilinks: documentation substrate body (EN+ES) batch 3 of 4
- 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)
- 2j: substrate EN + missed patterns/applications Bloomberg sweep (batch 6)
- docs(2g): corpus-wide Doctrine claim vocabulary removal (227 files)
- docs(2g): corpus-wide mechanical quality pass
- merge: integrate origin/main (taxonomy ratification + category-balance + schema-scrub commits) before project-knowledge Stage 6 promote
- Taxonomy ratification 2026-05-09: split architecture/ into substrate/+patterns/+architecture/; retire company/+help/