Leapfrog 2030 architecture
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- short_description trim (documentation): 52 over-long descriptions → ~135-179 chars, keyword-first (EN+ES); field-only, key distinguishing point preserved
- Metadata heal (documentation): 25 short_descriptions (EN+ES) + drop leading article/sentence-case 39 titles (EN+ES); title/frontmatter-only, slugs unchanged
- fix(frontmatter): correct references: YAML indentation across 72 documentation articles
- brand(trademark): MCorp™ + Capability Geometry™ — TOPIC footer notices and body text across documentation wiki
- feat(media-knowledge-documentation): add content_type field to all TOPIC + GUIDE files
- enrich wikilinks: documentation architecture body (EN+ES)
- 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(2g): corpus-wide Doctrine claim vocabulary removal (227 files)
- topic(architecture): leapfrog-2030-architecture — five shifts table, thesis clarification, Doctrine-claim scrub, Foundry→PointSav
- chore(architecture): convert bare concept references to wikilinks
- merge: integrate origin/main (taxonomy ratification + category-balance + schema-scrub commits) before project-knowledge Stage 6 promote
- docs wiki Step 5: register-correct rewrites — 4 high-urgency EN+ES architecture/governance pairs
- wikipedia-parity: remove inline copyright, trademark, and Provenance blocks from article bodies
- content-wiki-documentation: terminal section order + See Also batch (32 files)
- content-wiki-documentation: body H1 batch remediation (106 files)
- IP footer sweep — re-apply five-mark trademarks workspace-wide
- PL.7: Batch normalization — remove legacy topic- prefix from all files and links