Yo-Yo daily enrichment cycle
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- 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
- editorial(services): rewrite yoyo-daily-enrichment-cycle around the already-verified 2-phase pipeline (Track-B) — reused ai/elastic-compute-lora-training-pipeline.md's verified findings rather than re-deriving: real script is 2 phases not 8, ~4 hour budget not 45 minutes (cost figures were downstream-wrong by ~6x), and critically the training phase is confirmed NOT YET ACTIVE (marker-only mode pending a VM image rebuild) — dropped the fabricated 'Verified test results' table showing DPO-pair deltas from training runs that don't actually execute yet; register-clean EN+ES, no repo-path citations
- fix(index-group): resolve orphaned articles across 8 categories, add infrastructure's Compute and VM fabric group
- correct(services): flag wrong 8-phase/45min structure vs real 2-phase nightly-run.sh (yoyo-daily-enrichment-cycle)
- editorial(titles): sentence-case re-casing across 43 documentation titles
- Metadata heal (documentation): 25 short_descriptions (EN+ES) + drop leading article/sentence-case 39 titles (EN+ES); title/frontmatter-only, slugs unchanged
- Linking heal (documentation): first-mention wikilinks on 48 under-linked articles (171 links, index-validated, no red links); EN only, ES pairs follow-up
- feat(media-knowledge-documentation): add content_type field to all TOPIC + GUIDE files
- docs(architecture,services): add yoyo and spot-vm topics (EN+ES) — kill-switch pattern, 8-phase enrichment cycle, DPO format, verified test results; from project-software dispatch