| a9b4059 | Jennifer Woodfine | 2026-05-15T20:11:26+00:00 | fix(systems): remove cluster-totebox-jennifer deployment reference from totebox-archive | |
| 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 |
| d0b5b58 | Jennifer Woodfine | 2026-05-09T00:43:04+00:00 | Resolve 5 slug collisions: globally-unique-slug invariant restored | content-contract.md §3 requires globally unique slugs across the wiki (the wikilink resolver is flat, not per-category). Audit found 5 slug collisions where the same slug existed in two categories. Resolved by keeping the more comprehensive/recent version and rm'ing the duplicate.
**Resolutions (10 files git rm'd):**
1. citation-substrate — kept architecture/ (134 lines, full substrate framing); rm'd reference/ (54 lines, shorter overview).
2. design-system-substrate — kept architecture/ (134 lines); rm'd reference/ (54 lines).
3. reverse-funnel-editorial-pattern — kept architecture/ (113 lines); rm'd reference/ (61 lines).
4. favicon-matrix — kept governance/ (44 lines, full foundry-doc-v1 frontmatter from session #4 commit 1868a20); rm'd reference/ (44 lines, older frontmatter style).
5. location-intelligence-platform — kept applications/ (refined this 2026-05-08 sweep at commit dc9acec, consequence-first lead naming the 2 component apps); rm'd architecture/ (older + duplicate platform overview).
Each rm'd EN paired with its .es.md. Total: 10 files removed.
Verified: `find . -name '*.md' | basename | sort | uniq -d` returns 0 results across the wiki content. Slug invariant clean.
Net category counts after this commit:
- architecture: 83 → 82 (location-intelligence-platform removed)
- reference: 59 → 55 (citation-substrate, design-system-substrate, reverse-funnel-editorial-pattern, favicon-matrix removed)
- Other categories unchanged.
Closes the slug-uniqueness audit started during the category-balance analysis. |
| 8d047fc | Jennifer Woodfine | 2026-05-06T18:09:03+00:00 | content-wiki-documentation: ES pairs Véase también batch + contributor-model frontmatter fix (107 files) | - Added ## Véase también to 106 Spanish strategic-adaptation files that
were missing it; links mirror the EN pair's ## See Also slugs
- contributor-model.es.md: rebuilt full foundry-doc-v1 frontmatter
(schema, title, slug, language, paired_with, type, quality, status,
last_edited, editor, cites); fixed Véase también from raw (topic-*.md)
links to [[slug]] wikilinks per content-contract §5.1
- design-system/_index.es.md skipped (category landing, EN has no See Also) |
| 729c39b | Peter Woodfine | 2026-05-09T00:29:28+00:00 | Wiki content frontmatter normalisation: schema upgrade to foundry-doc-v1 across 24 files + slug-collision cleanup | Operator dispatch 2026-05-09: complete coverage of all TOPICs and GUIDEs so the live wikis can be updated. Audit of content-wiki-documentation revealed:
- 16 files at old schema 'foundry-topic-v1' (need upgrade)
- 17 files with no schema field — 7 are repo-meta (legitimately no foundry-doc-v1), 10 are wiki content needing full frontmatter
- 2 slug-collision files (architecture/service-slm-totebox-sysadmin EN+ES) duplicating the canonical services/service-slm-totebox-sysadmin (last_edited 2026-05-08 from the services-batch-2 commit) — content-contract.md §3 requires globally unique slugs
This commit closes all three:
**Schema upgrade foundry-topic-v1 → foundry-doc-v1 (16 files):**
- architecture/architecture (EN+ES)
- architecture/collab-via-passthrough-relay (EN+ES)
- architecture/source-of-truth-inversion (EN+ES)
- architecture/substrate-native-compatibility (EN+ES)
- infrastructure/edge-deployment (EN+ES)
- infrastructure/storage (EN+ES)
- infrastructure/telemetry-architecture (EN+ES)
- reference/wiki-provider-landscape (EN+ES)
Plus normalisation: status 'published' → 'active'; added type: topic + quality: complete; replaced 'language: es' / 'companion: <stale-path>' with the current paired_with field; bumped last_edited to 2026-05-09.
**Full frontmatter added (8 files):**
- architecture/customer-hostability.es.md (was just 4 fields; full frontmatter added)
- architecture/decode-time-constraints.es.md (added schema + type + paired_with)
- architecture/foundry-doctrine-architecture (EN+ES) (added schema + type + paired_with)
- architecture/location-intelligence-substrate (EN+ES) (added schema + type + paired_with)
- architecture/service-wallet-settlement (EN+ES) (added schema + type + paired_with)
**Slug-collision rm (2 files):**
- architecture/service-slm-totebox-sysadmin.md + .es.md git rm'd. The canonical version lives at services/service-slm-totebox-sysadmin.md (foundry-doc-v1, last_edited 2026-05-08, refined in commit 11d617a Step 5 priority 4b services batch 2). The services category is correct per the Nomenclature Matrix (service-* prefix → services/).
After this commit, content-wiki-documentation has zero foundry-topic-v1 files and zero no-schema wiki-content files. All 424+ wiki articles carry foundry-doc-v1 schema. The repo is render-ready for the next live-wiki update. |
| 6ae8599 | Peter Woodfine | 2026-05-06T18:05:43+00:00 | content-wiki-documentation: terminal section order + See Also batch (32 files) | - Fixed section order (See Also after References) in 2 articles:
architecture/collab-via-passthrough-relay.md,
design-system/design-primitive-vocabulary.md
- Added ## See Also section to 30 EN articles that were missing it:
7 architecture, 2 applications, 1 governance, 14 reference,
3 services, 1 design-system; 3-5 [[slug]] wikilinks per article
- See Also placed immediately before ## References (if present)
or before copyright footer; follows Wikipedia terminal section order |
| 38aa424 | Peter Woodfine | 2026-05-08T19:47:52+00:00 | Phase A close-outs: zero-container-inference competitor-name fix + cleanup-log items closed | architecture/zero-container-inference.md: "What this rules out" section replaces named competitors (Cloud Run, Kubernetes, SkyPilot, cargo-chef) with generic categories (managed container orchestration platforms, container runtime systems, multi-cloud abstraction frameworks, OCI image registries, layered Docker build caching, container build pipelines). Workspace §6 violation — "no competitive comparisons by name" — now resolved.
.agent/rules/cleanup-log.md: closes two Open items per the verified state — (1) competitor-name violation (just fixed at this commit); (2) category migration verification (find produces no root-level legacy topic-*.md files; migration completed in earlier sessions). Staging-mirror state line removed (covered by outbox addenda). |
| 1ef6cba | Jennifer Woodfine | 2026-05-06T18:03:06+00:00 | content-wiki-documentation: body H1 batch remediation (106 files) | - Removed duplicate body # H1 from 103 category-subdirectory articles with
foundry-doc-v1 frontmatter (content-contract §5.2: renderer supplies H1
from title: field; no body H1 permitted)
- Added foundry-doc-v1 frontmatter + removed H1 from 3 bare articles:
architecture/leapfrog-2030-architecture.md + .es.md,
reference/style-guide-guide.es.md
- Cleanup-log updated: guide-telemetry.md and user-guide-2026-03-30-v2.md
deferred (classification decisions required before H1 removal)
- Script respected code blocks: style-guide-changelog # Changelog (line 92
inside markdown code block) correctly left unchanged |
| e06100b | Jennifer Woodfine | 2026-05-08T19:39:17+00:00 | cleanup-log: 2026-05-08 Open entry updated — Step 5 priority 4c closed, canonical promote landed | Removes the now-stale "Open — applications category (Phase 4c paused)" line. Updates the commit list to reflect the full session sweep including Stage 6 reconciliation merge (dcec4f6), cleanup-log archive split (5880bd0), 4c remainder reclassification (dc9acec), and frontmatter+lead pass on moved articles (0a5b96f).
Documents the canonical promote at 2026-05-08T20:55Z (5880bd0) and notes the 2 staging-only commits (dc9acec, 0a5b96f) queued for the next promote.
Editorial Reference Plan Step 5 status: priorities 1, 2, 3, 4a, 4b, 4c all complete; only priority 5 (~72 GUIDEs) and category migration verification remain. Step 4 still blocked. |
| d046f96 | Peter Woodfine | 2026-05-06T17:00:20+00:00 | content-wiki-documentation: commit cleanup-log entries for Phase D/E batch and bim-leapfrog sweep | |
| 0a5b96f | Peter Woodfine | 2026-05-08T19:29:59+00:00 | Step 5 priority 4c remainder (frontmatter+lead): 4 moved articles in architecture/ | Follow-up to the previous rename commit. The renames landed at 100% similarity because the post-mv frontmatter and lead edits were not staged before the commit. Staging them now.
Per article (EN + ES pair):
- article-shell-leapfrog: schema foundry-topic-v1 → foundry-doc-v1; added title/slug/type/quality/short_description/editor/paired_with; category applications → architecture; lead consequence-first.
- knowledge-wiki-home-page-design: same schema upgrade; lead opens with the two-reader claim and Wikipedia Main Page inheritance.
- wikipedia-leapfrog-design: same; lead consolidates the 95%/5% muscle-memory framing.
- location-intelligence-ux: schema already foundry-doc-v1; body H1 removed (content-contract.md §5.2); category applications → architecture; lead opens with Conclusion-First philosophy.
last_edited bumped to 2026-05-08 across all 8 files. Stage 6 to canonical pending. |
| 9c805a1 | Jennifer Woodfine | 2026-05-06T16:50:53+00:00 | content-wiki-documentation: update flat-file-bim-leapfrog topic with richer draft content | - Expanded standards-stack maturity section (IFC 4.3/ISO 16739-1:2024, IDS 1.0, BCF 3.0, CityJSON 2.0)
- Extended format table (COBie, hash-addressed object store, SVG, CityJSONSeq)
- Added government regulatory acceptance section (US federal, EU, UK, Singapore, Dubai)
- Added trade-offs section (real-time collaboration, city-scale federation, generative AI)
- §6 applied: all named competitors genericized (structural positioning only)
- Body H1 removed per content-contract §5.2
- ES strategic-adaptation refreshed with regulatory posture and trade-offs
- Source: project-bim draft (Doctrine claim #40 — Flat-File BIM Substrate) |
| dc9acec | Jennifer Woodfine | 2026-05-08T19:29:33+00:00 | Step 5 priority 4c remainder: 4 design-intent articles → architecture/, location-intelligence-platform refined, launch announcement retired | Reclassification + cleanup pass on the 6 remaining applications/ articles.
**Moved to architecture/** (4 EN+ES pairs, 8 files):
- article-shell-leapfrog (cross-cutting design pattern: 5 article-shell primitives beyond Wikipedia)
- knowledge-wiki-home-page-design (design intent for documentation.pointsav.com home page)
- wikipedia-leapfrog-design (95%/5% muscle-memory contract for the wiki chrome)
- location-intelligence-ux (Conclusion-First design philosophy for the GIS interface)
Schema upgrade foundry-topic-v1 → foundry-doc-v1 on all 4 (3 needed it; location-intelligence-ux was already foundry-doc-v1). Body H1 removed where present (location-intelligence-ux). Lead consequence-first per draft 2 of 10. last_edited 2026-05-08.
**Refined in place** (1 EN+ES pair, 2 files):
- applications/location-intelligence-platform — body H1 removed; lead now names the two component apps explicitly (app-orchestration-gis + pointsav-gis-engine) and points to co-location-methodology.
**Retired** (1 EN+ES pair git rm'd):
- applications/documentation-pointsav-com-launch-2026-04-27 — historical launch event from 2026-04-27 16:25 UTC (workspace v0.1.29). CHANGELOG.md captures the event; the live URL is the canonical record. The slug's date suffix marked it as a one-off, not a standing topic. Inbound wikilinks scrubbed (app-mediakit-knowledge See Also EN+ES — replaced with article-shell-leapfrog reference).
After this commit:
- applications/ retains 4 canonical app-* topics (app-mediakit-knowledge, app-mediakit-marketing, app-orchestration-gis) + location-intelligence-platform.
- architecture/ gains 4 design-intent siblings to compounding-substrate, doorman-protocol, etc.
Closes Step 5 priority 4c. Stage 6 to canonical pending. |