| 1c02ec1 | Peter Woodfine | 2026-06-16T18:48:42+00:00 | fix(editorial): strip leaked claim-comment markers (22 files); tier-nomenclature lede rewrite (§16.C Mode 2) | |
| 3f1e0da | Jennifer Woodfine | 2026-06-14T06:23:35+00:00 | docs(wiki): add 5 bilingual TOPIC pairs — crypto/license/PPN/console/distribution architecture (10 files) | |
| 5d6b8b2 | Peter Woodfine | 2026-05-18T03:35:13+00:00 | docs: CITATION.cff — CFF 1.2.0 citation metadata for content-wiki-documentation (CC-BY-4.0 dataset) | |
| cd269e0 | Jennifer Woodfine | 2026-05-16T19:36:15+00:00 | content: correct design-system license citations (Apache 2.0, not MIT) | Two articles cited the design-system as MIT-licensed; the canonical
licensing matrix in factory-release-engineering assigns Apache 2.0
to pointsav-design-system (matching IBM Carbon / Adobe Spectrum).
Files:
- governance/contributor-model.md — "MIT design-system" → "Apache 2.0 design-system"
- substrate/knowledge-commons.md — license table row corrected to Apache 2.0
- substrate/knowledge-commons.es.md — matched Spanish-language correction |
| 197b92a | Peter Woodfine | 2026-05-15T18:04:10+00:00 | docs(governance): update category landing to reference architecture-decisions | - governance/_index.md: lede updated to reference consolidated architecture-decisions
article; article list updated (removed ADR stubs; added architecture-decisions,
bcsc-disclosure-posture, compliance-and-continuous-disclosure); retired
/company/ link removed from See also; last_edited updated
- governance/_index.es.md: full Spanish rewrite matching EN structure; same
article list and See also updates; 'convenciones de cumplimiento' → 'requisitos
de cumplimiento' (removes internal vocabulary) |
| fd0d647 | Jennifer Woodfine | 2026-05-15T17:52:23+00:00 | docs(2g): readability pass — featured pool batch 2 (3 articles) | - customer-hostability.es: 'Doctrine §IV.b' → plain text (mirrors EN fix)
- knowledge-commons: quality published→complete; 'conventions' in lede and table
replaced with 'published specifications'; 'See also' normalized
- knowledge-commons.es: quality published→complete |
| 4e3426d | Jennifer Woodfine | 2026-05-12T16:35:56+00:00 | YAML reorganization: move structured-record files from root into category subdirectories — architecture/ governance/ reference/ services/ | |
| c4d1fb1 | Peter Woodfine | 2026-05-09T04:25:09+00:00 | home-page YAML refresh + title scrub — institutional banker register | featured-topic.yaml: rotation pool of 12 banker-relevant articles
(disclosure-substrate, economic-model, compounding-substrate,
sovereign-ai-commons, customer-hostability, three-ring-architecture,
llm-substrate-decision, doorman-protocol, worm-ledger-design,
knowledge-commons, substrate-native-compatibility,
leapfrog-2030-architecture); operator advances pin weekly. First pin:
economic-model. Replaces stale pin at architecture/topic-leapfrog-2030-
architecture (pre-migration path).
leapfrog-facts.yaml: refresh from 'leapfrog inventions' framing to
seven Structural Facts in banker register. Workspace-internal
governance vocabulary scrubbed. Each fact opens with structural
defensibility ('runs on commodity hardware', 'fully operational with
zero AI inference', 'customer data never leaves customer infrastructure',
'OLMo 3 Level 3 openness', 'disclosure compliance built into commit
layer', 'every inference call logged', 'commercial threshold is
architectural not feature-tier').
Title scrub — 3 articles whose titles contained workspace-internal
governance vocabulary (Doctrine, Convention) per operator constraint
that public-facing wiki content reads in institutional prose, not
internal naming for governance machinery:
- governance/sovereign-airlock-doctrine.md + .es.md: 'The Sovereign
Airlock Doctrine' → 'The Sovereign Airlock' / 'La Exclusa Soberana'
- reference/bim-aec-muscle-memory.md + .es.md: 'AEC Muscle Memory and
Interface Conventions' → 'AEC Muscle Memory and Interface Patterns'
/ 'Memoria Muscular AEC y Patrones de Interfaz'
- architecture/foundry-doctrine-architecture.md + .es.md: 'Foundry
Doctrine — Architectural Overview' → 'Foundry — Architectural
Overview' / 'Foundry — Visión Arquitectónica'
Slugs retained per content-contract.md §3 immortality rule; URLs
unaffected.
OS title casing normalised — 3 systems/ articles whose title fields
used PascalCase (OrchestrationOS, NetworkAdminOS, PrivateGitOS) while
sibling articles used Title Case + space (Console OS, Infrastructure
OS, MediaKit OS). Same category, three formats, visible to readers on
home-page article lists. Normalised to Title Case + space:
- systems/os-orchestration.md + .es.md: 'OrchestrationOS' →
'Orchestration OS' (title + short_description)
- systems/os-network-admin.md + .es.md: 'NetworkAdminOS' → 'Network
Admin OS' (title + body lede)
- systems/os-privategit.md + .es.md: 'PrivateGitOS' → 'Private Git
OS' (title + body lede)
cleanup-log.md: new Open entry — body-level Doctrine (72 EN files) +
Convention (49 EN files) scrub surfaced as tracked work, phased over
multiple sessions (first sweep: 12 banker-relevant Featured-rotation
articles; second: substrate/+architecture/; third: remaining
categories). Per-file editorial decision required; not a mechanical
find-replace. |
| ef58b39 | Peter Woodfine | 2026-05-06T23:50:26+00:00 | fix: quote colon-containing YAML title fields per content-contract §4 — 4 Phase-E files | |
| 91889cf | Jennifer Woodfine | 2026-05-09T01:02:36+00:00 | cleanup-log: close 2026-05-09 category-balance audit (taxonomy ratified) | Audit complete across 5 commits (729c39b + d0b5b58 + 333a59d + eaac482 + 2e843fb). All 4 original imbalances resolved:
- architecture oversized (75) → split into 35 + substrate 30 + patterns 10
- reference oversized (55) → trimmed to 44 by moving design-system articles
- applications/infrastructure undersized → infrastructure populated to 9, applications stable at 4
- company/help empty → retired from §4 taxonomy
Final state: 10 active categories, no empties, no oversized. naming-convention.md ratification log updated with decisions #5 (split) and #6 (retirement). |
| af66e62 | Peter Woodfine | 2026-05-06T22:19:48+00:00 | Hygiene: archive closed entries from cleanup-log | cleanup-log.md: 295 lines → 282 active (open items); 24 lines → cleanup-log-archive.md
Active file is still over 150-line limit; content is open items for Root review.
Root session needed to triage 2026-04-23 items for completion or carry-forward. |
| 2e843fb | Peter Woodfine | 2026-05-09T01:01:54+00:00 | Taxonomy ratification 2026-05-09: split architecture/ into substrate/+patterns/+architecture/; retire company/+help/ | Operator-confirmed structural change to content-wiki-documentation taxonomy. Closes the category-balance audit.
**architecture/ split (75 → 35) into 3 categories:**
- substrate/ (30 articles, NEW category): foundational mechanism concepts — X-substrate articles plus the disciplines and primitives that compose them (apprenticeship-substrate, brief-queue-substrate, citation-substrate, code-for-machines-first, compounding-doorman, compounding-substrate, customer-owned-graph-ip, design-system-substrate, disclosure-substrate, four-tier-slm-substrate, knowledge-commons, knowledge-graph-grounded-apprenticeship, language-protocol-substrate, llm-substrate-decision, location-intelligence-substrate, mcp-substrate-protocol, merkle-proofs-as-substrate-primitive, reverse-flow-substrate, seed-taxonomy-as-smb-bootstrap, single-boundary-compute-discipline, sovereign-ai-commons, substrate-native-compatibility, substrate-without-inference-base-case, system-substrate-doctrine, tier-zero-customer-side-sovereign-specialist, trajectory-substrate, tui-corpus-producer, yoyo-compute-substrate, adapter-composition, meta-repo-pattern). Plus _index.md + .es.md MOC landings authored.
- patterns/ (10 articles, NEW category): named design patterns recurring at the editorial/interface/coordination layer (article-shell-leapfrog, collab-via-passthrough-relay, knowledge-wiki-home-page-design, knowledge-wiki-leapfrog-architecture, location-intelligence-ux, pairing-as-permission, reverse-funnel-editorial-pattern, source-of-truth-inversion, wikipedia-leapfrog-design, zero-execution-routing). Plus _index.md + .es.md MOC landings authored.
- architecture/ retained (~35 articles): cross-cutting platform architecture, doctrine articles, concrete systems composition (3-layer-stack, three-ring-architecture, foundry-doctrine-*, doorman-protocol, totebox-orchestration-development, totebox-session, leapfrog-2030-architecture, BIM articles, crypto/identity articles, etc.).
**Empty categories retired:**
- company/ (was 0 articles): retired. Originally ratified §13 decision #2 (2026-05-07) as investor-facing. No articles authored. Per operator: re-add when first TOPIC is written.
- help/ (was 0 articles): retired. Originally for contributor-onboarding. No articles authored. Same re-add policy.
**naming-convention.md updates:**
- §4 category-set table: replaced 9-category proposal with the new 10-category active set (architecture, substrate, patterns, systems, services, applications, governance, infrastructure, reference, design-system). Removed company + help rows. Added substrate + patterns rows with example articles.
- §13 ratification log: appended decisions #5 (split) and #6 (retirement) with rationale (~3× mean was too big; empty categories carry no editorial value).
**Final distribution (no oversized, no empties):**
- architecture: 35 (was 75)
- substrate: 30 (new)
- patterns: 10 (new)
- design-system: 36
- reference: 44
- governance: 20
- services: 19
- systems: 10
- infrastructure: 9
- applications: 4
Mean ~22, range 4-44, 10 active categories. No category 4× mean.
**File operations:** 30 articles × 2 = 60 git mv to substrate/; 10 articles × 2 = 20 git mv to patterns/; 4 _index files (substrate + patterns × EN+ES) created; 4 _index files (company + help × EN+ES) git rm'd; 80 moved files had category frontmatter field updated via sed.
Closes the category-balance audit started 2026-05-09. The wiki is render-ready and well-balanced. |
| 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 |