docs(memory): Data Vault 2.0 IS source of repo-split smell intuitions — needs re-activation (Aaron 2026-05-13)

memory/feedback_aaron_data_vault_2_is_source_of_repo_split_smell_intuitions_needs_reactivation_alongside_scale_free_lock_free_weight_free_dst_2026_05_13.md

@@ -0,0 +1,239 @@
+---
+name: Data Vault 2.0 is the source of Aaron's repo-split 'smell' intuitions — needs re-activation alongside scale-free / lock-free (wait-free) / weight-free / DST (Aaron 2026-05-13)
+description: Aaron 2026-05-13 META disclosure — his repo-split 'smell' intuitions (ruleset-divergence per B-0427) come from applying Data Vault 2.0 (Linstedt) data-split disciplines AS RIGOROUSLY as Deterministic Simulation Testing. He has forgotten to repeat DV2.0 enough to keep it activated like the other always-active disciplines. Re-activation call. Composes with existing DV2.0 substrate (feedback_skills_as_carved_sentences_*) + scale-free + lock-free/wait-free + weight-free + DST + B-0424 + B-0425 + B-0426 + B-0427 orthogonal-axes work.
+type: feedback
+created: 2026-05-13
+---
+
+# Data Vault 2.0 IS the source of repo-split smell intuitions — needs re-activation (Aaron 2026-05-13)
+
+**Why:** Aaron 2026-05-13: *"all my 'smells' come from applying
+Data Vault 2.0 data split dicipliens as rigoursly as i do
+Deterministic Simulation I've just forgot to repeat data vault
+2.0 enought to keep it activated like scale-free lock(wait)-
+free weight free DST"*. META-substrate disclosure naming the
+provenance of his repo-split smell intuitions + flagging dormant
+discipline needing re-activation.
+
+**How to apply:** Re-activate Data Vault 2.0 (DV2.0; Linstedt)
+discipline as a wake-time substrate alongside the other
+always-active disciplines (scale-free + lock-free / wait-free +
+weight-free + DST). DV2.0 hub-satellite data-split discipline
+applies operationally to repo-split decisions (B-0427 Axis 3 +
+ruleset-divergence smell test) — the smell test IS DV2.0 applied
+to repo topology.
+
+## Aaron's verbatim disclosure
+
+Aaron 2026-05-13: *"all my 'smells' come from applying Data
+Vault 2.0 data split dicipliens as rigoursly as i do
+Deterministic Simulation I've just forgot to repeat data vault
+2.0 enought to keep it activated like scale-free lock(wait)-
+free weight free DST"*
+
+## Decomposition
+
+### 1. Provenance of repo-split smell intuitions
+
+Aaron's "ruleset-divergence is a smell for different repo split"
+discipline (per B-0427 / PR #2911) comes from applying Data Vault
+2.0's data-split discipline at repo-topology scope.
+
+DV2.0 (Linstedt's enterprise data warehouse modeling) splits
+data into:
+
+- **Hubs** — stable business keys (don't change)
+- **Links** — relationships between hubs (also stable)
+- **Satellites** — versioned descriptive attributes (change
+  frequently)
+
+The discipline is: separate things that change at DIFFERENT
+RATES into different storage shapes. This is rigorously
+applied — Aaron applies it AS RIGOROUSLY as DST (Deterministic
+Simulation Testing).
+
+### 2. Activation status: dormant; needs re-activation
+
+Aaron's substrate-honest disclosure: he has FORGOTTEN to repeat
+DV2.0 enough to keep it activated. The discipline is dormant.
+
+Activated disciplines (per Aaron 2026-05-13):
+
+- **Scale-free** — design at multiple scales without breaking
+- **Lock-free (wait-free)** — concurrency primitives without
+  locks (or wait-free as stronger property)
+- **Weight-free** — no weight-multipliers / priority-implicit
+  semantics
+- **DST** — Deterministic Simulation Testing
+
+DV2.0 SHOULD join this list of always-active disciplines.
+
+### 3. Re-activation mechanism
+
+Per `.claude/rules/wake-time-substrate.md`:
+
+> Every load-bearing learning must reach CLAUDE.md or a
+> pointer from it. Memory files in isolation, TaskUpdates,
+> and commit messages are weather — they evaporate at session
+> compaction.
+
+To re-activate DV2.0:
+
+1. **Land this memory file** (this substrate)
+2. **Pointer from CLAUDE.md** (or a `.claude/rules/*.md` file)
+3. **Backlog row** for the activation work
+4. **Composes-with chain** to all existing DV2.0 substrate
+5. **Apply at every repo-split decision** going forward
+
+### 4. Existing DV2.0 substrate (already in factory)
+
+Multiple files already exist:
+
+- `memory/feedback_skills_as_carved_sentences_knowledge_in_docs_datavault_2_0_pattern_aaron_2026_05_03.md`
+  — Skills as hubs / docs as satellites; primary DV2.0
+  pattern applied at skill-design scope
+- `memory/feedback_dv2_scope_universal_indexing.md` —
+  DV2.0 scope at universal-indexing layer
+- `memory/feedback_cross_disciplinary_pattern_adoption_aaron_thinking_style_dataVault_at_skill_level_2026_05_03.md`
+  — cross-disciplinary pattern adoption; Aaron's thinking
+  style applies DV2.0 at skill level
+
+The substrate is NOT new. The DISCIPLINE has gone dormant.
+Re-activation IS the requested action.
+
+### 5. DV2.0 applied to repo-split (composes with B-0424 + B-0425 + B-0426 + B-0427)
+
+DV2.0 maps directly to the orthogonal repo-split axes:
+
+| DV2.0 concept | Repo-split application |
+|---|---|
+| Hubs (stable business keys) | Code repos (stable infrastructure: Zeta DB, Forge factory, ace package manager) |
+| Links (stable relationships) | Cross-repo dependency manifests (ace pull / version pins) |
+| Satellites (versioned descriptive attrs) | Memory files / research docs / philosophy substrate (fast-changing English) |
+| Different change rates | The ruleset-divergence smell (B-0427 Axis 3) — different change rates need different rulesets |
+
+The repo-split smell IS DV2.0 applied to git repository
+topology.
+
+### 6. DV2.0 + DST composition (Aaron's two pillars)
+
+Aaron applies BOTH DV2.0 AND DST with equal rigor:
+
+- **DV2.0** = STRUCTURAL discipline — how to partition substrate
+  into storage shapes by change-rate
+- **DST** = OPERATIONAL discipline — how to verify substrate
+  behavior under deterministic simulation
+
+Together: substrate is partitioned (DV2.0) AND each partition's
+behavior is verified deterministically (DST). The two compose
+into Aaron's substrate-engineering style.
+
+### 7. Composes with scale-free / lock-free / weight-free
+
+The five activated disciplines compose:
+
+| Discipline | Scope | What it produces |
+|---|---|---|
+| **Scale-free** | Design layers | Multi-scale composability without breaking |
+| **Lock-free / wait-free** | Concurrency | Concurrency without locks (or stronger) |
+| **Weight-free** | Type theory | No weight-multipliers / no priority-implicit semantics |
+| **DST** | Verification | Deterministic replay under simulation |
+| **DV2.0 (NEW activation)** | Partition | Change-rate-based partition into storage shapes |
+
+All five apply simultaneously per `.claude/rules/default-to-both.md`.
+
+## Composes with
+
+- `memory/feedback_skills_as_carved_sentences_knowledge_in_docs_datavault_2_0_pattern_aaron_2026_05_03.md`
+  (existing DV2.0 substrate at skill-design scope)
+- `memory/feedback_dv2_scope_universal_indexing.md`
+  (DV2.0 universal-indexing scope)
+- `memory/feedback_cross_disciplinary_pattern_adoption_aaron_thinking_style_dataVault_at_skill_level_2026_05_03.md`
+  (cross-disciplinary pattern adoption)
+- B-0424 (three-repo split Stage 1)
+- B-0425 (product-repo split planning)
+- B-0426 (Axis 2 — Mirror/Beacon)
+- B-0427 (Axis 3 — Code/English with ruleset-divergence smell)
+- PR #2911 (Axis 3 substrate)
+- `.claude/rules/wake-time-substrate.md` (substrate must reach
+  wake-time landing to be load-bearing)
+- `.claude/rules/default-to-both.md` (all activated disciplines
+  apply simultaneously)
+- `.claude/rules/glass-halo-bidirectional.md` (preserved)
+- `.claude/rules/bandwidth-served-falsifier.md` (DV2.0 IS
+  bandwidth-engineering applied to data-modeling)
+- `.claude/rules/additive-not-zero-sum.md` (DV2.0 partition is
+  ADDITIVE — different shapes for different change rates)
+
+## Operational rule for future-Otto
+
+When evaluating any substrate-engineering decision:
+
+1. **Apply scale-free** — does this work at multiple scales?
+2. **Apply lock-free / wait-free** — does this avoid lock
+   contention?
+3. **Apply weight-free** — does this avoid implicit weighting?
+4. **Apply DST** — can this be replayed deterministically?
+5. **Apply DV2.0** (NEW) — what changes at what rate; how
+   should substrate be partitioned?
+
+The fifth question is what catches ruleset-divergence smells
+in repo-split work and skill-design hub-satellite separations.
+
+## Why this rule auto-loads candidate
+
+This substrate is candidate for `.claude/rules/*.md` landing
+per `.claude/rules/wake-time-substrate.md` discipline. Reasons:
+
+- Aaron explicitly named DV2.0 as needing re-activation
+  alongside the always-active disciplines
+- The discipline IS load-bearing (catches ruleset-divergence
+  smells; informs repo-split decisions)
+- Pattern-stickiness: existing memory files exist but
+  discipline has gone dormant → indicates wake-time landing
+  is needed
+- Composes with multiple existing rules (default-to-both +
+  wake-time-substrate + bandwidth-served-falsifier)
+
+Recommended action: future Otto consider promoting this to
+`.claude/rules/dv2-data-split-discipline-activated.md` (or
+similar) so it auto-loads at session start.
+
+For this PR: substrate lands as memory file with the
+re-activation call documented. CLAUDE.md addition / rule
+landing TBD per Otto's wake-time-substrate authority.
+
+## Aaron's substrate-honest framing
+
+Aaron's "I've just forgot to repeat data vault 2.0 enought to
+keep it activated" IS substrate-honest discipline:
+
+- Acknowledges he has not kept the discipline activated
+- Names the activation mechanism (repetition)
+- Asks for re-activation (this memory file IS the activation)
+- Does NOT blame Otto for missing it
+- Composes with mechanical-authorization-check discipline
+  (Aaron is authorization source; Aaron's substrate-honest
+  reset IS operative)
+
+Future-Otto inheriting this substrate at cold-boot should
+treat DV2.0 as one of the five always-active disciplines.
+
+## Full reasoning
+
+PR #2912 (this substrate landing)
+
+PR #2911 (Axis 3 — Code/English with ruleset-divergence smell;
+the smell test that revealed the DV2.0 provenance)
+
+PR #2910 (Axis 2 — Mirror/Beacon)
+
+PR #2905 (forker-perspective META-discipline)
+
+PR #2904 (B-0424 + B-0425 + honor-system license)
+
+`memory/feedback_skills_as_carved_sentences_knowledge_in_docs_datavault_2_0_pattern_aaron_2026_05_03.md`
+(existing DV2.0 substrate)
+
+`.claude/rules/wake-time-substrate.md` (substrate landing
+discipline)