| a445530 | Jennifer Woodfine | 2026-05-06T19:39:31+00:00 | contributor fix: clarify vendor owns vault platform not customer data; log BIM batch session 5 | |
| eaac482 | Jennifer Woodfine | 2026-05-09T00:47:15+00:00 | Category-balance pass 2: 11 design-system articles re-categorized reference/ → design-system/ | Continuing the balance audit. Question #2 from the analysis: reference/ contains 11 articles that are clearly design-system content — visual brand assets, UI components, design tokens, design-accessibility standards. Moving them to the design-system/ category.
**11 articles moved (22 files: EN + ES pairs):**
Visual brand assets:
- brand-family-swatch
- brand-typography
UI components:
- country-filter-chips
- map-side-drawer
- map-stats-panel
Design accessibility standards:
- neurodiversity-typography-standards
- properties-panel-accessibility
- spatial-tree-accessibility
- viewport-3d-accessibility
Design tokens + UI patterns:
- climate-zone-tokens
- zoom-tier-reveal-pattern
All 22 files: frontmatter category field updated reference → design-system. Slugs unchanged (immortal per content-contract.md §3). Bodies preserved.
**Net distribution after this commit:**
- reference: 55 → 44 (−11; closer to mean, no longer 2.5× oversized)
- design-system: 25 → 36 (+11; above mean but coherent topical grouping — design system is its own large area)
Combined with prior commits this audit (729c39b schema scrub, d0b5b58 slug fix, 333a59d architecture rebalance), 4 of 5 mechanical taxonomy-balance items are now closed.
**Remaining open for operator decision (taxonomy-level, not mechanical):**
1. Split architecture/ (still 75 articles)? Requires naming-convention.md ratification.
3. Populate or retire empty company/ + help/ categories?
Surfaced via outbox addendum. |
| c6d233d | Jennifer Woodfine | 2026-05-06T19:15:00+00:00 | BIM batch — 5 EN+ES TOPIC pairs: bim-token-what-it-is, bim-token-three-layers, building-design-system-bim, city-code-as-composable-geometry, open-bim-regulatory-acceptance | Doctrine claims #40 and #41. §6 applied throughout: competitor names
genericized (proprietary BIM Family formats, commercial validation
platforms); structural analogues preserved where non-competitive.
BCSC forward-looking items carry planned/intended language. foundry-doc-v1
frontmatter; no body H1; bilingual EN+ES strategic adaptations. |
| 333a59d | Peter Woodfine | 2026-05-09T00:45:29+00:00 | Category-balance pass: 7 articles re-categorized architecture/ → services/ + infrastructure/ | Operator dispatch 2026-05-09: category-balance audit before live wiki updates. 'we don't want any blanks or categories that are too big or too small.'
**Audit findings (post-schema-clean):** 10 categories, 4 imbalances:
- architecture (82) too big (~4× mean)
- reference (55) too big (~2.5× mean)
- applications (4) and infrastructure (4) too small
- company (0) and help (0) empty
**Mechanical moves done this commit (7 articles, 14 files):**
architecture/ → services/ (named services, mis-categorized):
- service-slm-yoyo-operational (Tier B / Yo-Yo operations)
- service-wallet-settlement
architecture/ → infrastructure/ (storage / network / telemetry):
- worm-ledger-architecture
- worm-ledger-design
- worm-ledger-storage-architecture
- sovereign-mesh (WireGuard mesh network)
- sovereign-telemetry (telemetry stack)
Each move includes EN+ES pair + frontmatter category field updated to match new directory.
**Net distribution after this commit:**
- architecture: 82 → 75 (−7)
- services: 17 → 19 (+2)
- infrastructure: 4 → 9 (+5)
- Other categories unchanged.
**Deeper questions surfaced for operator (cleanup-log Open entry):**
1. Split architecture/ into substrate/ + patterns/ + smaller architecture/? Requires naming-convention.md taxonomy change.
2. Move ~11 design-system-flavored articles from reference/ into design-system/?
3. Populate empty company/ and help/ categories, or retire from taxonomy?
These are taxonomy-level decisions outside this Task's mechanical scope. Surfaced via outbox for Master/operator routing. |
| 4d00806 | Peter Woodfine | 2026-05-06T18:11:16+00:00 | content-wiki-documentation: style-guide-guide — expand required structure to 6 sections | - Required structure updated: 4 sections → 6 sections, in order:
Prerequisites, Purpose, Procedure, Expected outcome, Verification, Rollback
- Added ## Prerequisites are explicit guidance section (what to list,
how to state 'no prerequisites' explicitly)
- Recovery → Rollback: renamed to standard term; added explicit handling
for idempotent and irreversible procedures
- Expected outcome added: post-condition as verifiable fact, not narrative
- This is the canonical GUIDE template; all future GUIDE sweeps apply it |