Platform Services
23 revisions
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- docs(index): add curated 'Where to start' layer to infrastructure, how-to, services (iceberg batch 3/4)
- rename: 6 category display names for plainer, less internal-jargon labels
- Track-B documentation wave: services category — mandatory Test-1 self-contradiction fix (service-fs-data-lake), Test-3 split, structural + mechanical frontmatter fixes across 17 articles
- fix(index): regenerate 505 drifted AUTO-GENERATED MEMBERSHIP bullets across all 15 documentation-wiki categories (EN+ES) against each linked article's current short_description (tool-wiki-core's membership-drift checker, Part 4 item 3) — mostly short lowercase-fragment descriptions replaced with the article's full, current, properly-capitalized short_description; fixed a checker bug in the same pass that would have silently discarded 232 intentional piped-wikilink display texts (e.g. [[slug|Display Text]]) if applied blind
- docs(categories): reconcile 9 documentation-wiki category titles against the ratified 2026-07-02 rev-3 display-name proposal (categories.yaml already carried the new names; _index.md/.es.md and 15 sibling cross-reference links across the corpus had not caught up); also drop governance/_index.md's duplicate H1-restating H2 heading (MOS:HEAD)
- docs(architecture,patterns,substrate,services): ingest 5 PointSav platform-architecture articles migrated from media-knowledge-projects
- editorial(services): sync _index.md membership blurbs to both Track-B batches' findings — service-people/service-search/service-slm-totebox-sysadmin/service-slm-graph-store-migration/yoyo-daily-enrichment-cycle/service-wallet-settlement/service-pointsav-link blurbs were directly contradicting their own just-rewritten articles; EN+ES
- fix(index-group): resolve orphaned articles across 8 categories, add infrastructure's Compute and VM fabric group
- feat(index-topics): migrate remaining 11 categories to structured Index Topic rendering
- 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(compliance): correct SYS-ADR-07/Ring-3 imprecision across 4 articles (EN+ES) — 'no runtime call reaches Ring 3' overstated the real rule; corrected to 'Ring 3 never writes, always via proposal + human approval + Ring 2 write path' per architecture/three-ring-architecture.md's own fuller definition. nightly-datagraph-rebuild.md's 'no AI inference/not model-generated' claims were flatly wrong (verified against service-extraction's real code and service-content's Doorman call) — corrected to describe AI-assisted extraction gated by human approval. service-slm-graph-store-migration.md's stale automated-write description corrected with the 2026-07-18 human-approval-gate fix, plus an unrelated short_description/body metadata mismatch (false LadybugDB-to-SQLite migration claim) fixed. Operator-confirmed resolution after joint investigation — not a real compliance breach, just documentation that predated the approval-gate fix.
- content(services): consolidate service-fs-architecture.md + service-fs-security-compliance.md into one canonical services/service-fs.md — confirmed genuine redundancy (same subject: WORM ledger, Merkle chains, Rekor anchoring, seL4 target, described twice from architecture vs. compliance angles). Archived both old files (.archive/, EN+ES) with mandatory frontmatter; aliases: field + redirects.yaml entries preserve all ~44 existing inbound wikilinks/URLs without hand-editing every referencing file. Updated services/_index.md MOC. service-fs-data-lake.md investigated separately and kept apart — genuinely different subject (GIS landing-zone directory convention, not the WORM ledger service).
- feat(media-knowledge-documentation): add content_type field to all TOPIC + GUIDE files
- docs(2g): rebuild 6 category _index.md landings — complete MOC rewrites
- docs(2g): corpus-wide Doctrine claim vocabulary removal (227 files)
- merge: integrate origin/main (taxonomy ratification + category-balance + schema-scrub commits) before project-knowledge Stage 6 promote
- docs wiki: batch fix 124 frontmatter bugs + 19 gli template markup files
- Phase E: bcsc_class + status sweep — services/, systems/, infrastructure/, reference/, design-system/
- Diffuse Leapfrog 2030 Doctrine and Glossary formatting
- PL.7: Batch normalization — remove legacy topic- prefix from all files and links
- PL.7: Normalize wiki content to category subdirectories and transition to .agent rules
- Merge project-language cluster content into vendor main — sync 30+ TOPIC/bilingual pairs committed by Root and project-language Task
- iteration-1 documentation.pointsav.com — 9 category landing pages bilingual pairs