Dynamic Architectures Meta-Skill
When to Use This Skill
Invoke this meta-skill when you encounter:
- Growing Networks: Adding capacity during training (new layers, neurons, modules)
- Pruning Networks: Removing capacity that isn't contributing
- Continual Learning: Training on new tasks without forgetting old ones
- Gradient Isolation: Training new modules without destabilizing existing weights
- Modular Composition: Building networks from graftable, composable components
- Lifecycle Management: State machines controlling when to grow, train, integrate, prune
- Progressive Training: Staged capability expansion with warmup and cooldown
This is the entry point for dynamic/morphogenetic neural network patterns. It routes to 7 specialized reference sheets.
How to Access Reference Sheets
IMPORTANT: All reference sheets are located in the SAME DIRECTORY as this SKILL.md file.
When this skill is loaded from:
skills/using-dynamic-architectures/SKILL.md
Reference sheets like continual-learning-foundations.md are at:
skills/using-dynamic-architectures/continual-learning-foundations.md
NOT at:
skills/continual-learning-foundations.md (WRONG PATH)
Core Principle
Dynamic architectures grow capability, not just tune weights.
Static networks are a guess about capacity. Dynamic networks let training signal drive structure. The challenge is growing without forgetting, integrating without destabilizing, and knowing when to act.
Key tensions:
- Stability vs. Plasticity: Preserve existing knowledge while adding new capacity
- Isolation vs. Integration: Train new modules separately, then merge carefully
- Exploration vs. Exploitation: When to add capacity vs. when to stabilize
The 7 Dynamic Architecture Skills
- continual-learning-foundations - EWC, PackNet, rehearsal strategies, catastrophic forgetting theory
- gradient-isolation-techniques - Freezing, gradient masking, stop_grad patterns, alpha blending
- peft-adapter-techniques - LoRA, QLoRA, DoRA, adapter placement, merging strategies
- dynamic-architecture-patterns - Grow/prune patterns, slot-based expansion, capacity scheduling
- modular-neural-composition - MoE, gating, grafting semantics, interface contracts
- ml-lifecycle-orchestration - State machines, quality gates, transition triggers, controllers
- progressive-training-strategies - Staged expansion, warmup/cooldown, knowledge transfer
Routing Decision Framework
Step 1: Identify the Core Problem
Diagnostic Questions:
- "Are you trying to prevent forgetting when training on new data/tasks?"
- "Are you trying to add new capacity to an existing trained network?"
- "Are you designing how multiple modules combine?"
- "Are you deciding WHEN to grow, prune, or integrate?"
Quick Routing:
| Problem |
Primary Skill |
| "Model forgets old tasks when I train new ones" |
continual-learning-foundations |
| "New module destabilizes existing weights" |
gradient-isolation-techniques |
| "Fine-tune LLM efficiently without full training" |
peft-adapter-techniques |
| "Pick a post-LoRA PEFT variant (VeRA / LoRA+ / PiSSA / LoftQ / rsLoRA)" |
peft-adapter-techniques |
| "When should I add more capacity?" |
dynamic-architecture-patterns |
| "How do module outputs combine?" |
modular-neural-composition |
| "Merge several fine-tuned checkpoints (TIES / DARE / SLERP / MergeKit)" |
modular-neural-composition |
| "Production-grade MoE (Switch / Mixtral / DeepSeek-MoE / Expert Choice)" |
modular-neural-composition |
| "How do I manage the grow/train/integrate cycle?" |
ml-lifecycle-orchestration |
| "How do I warm up new modules safely?" |
progressive-training-strategies |
| "Serve many LoRAs in one process (S-LoRA / LoRAX / Punica)" |
not covered by this pack — see the primary sources listed in peft-adapter-techniques.md |
Step 2: Catastrophic Forgetting (Continual Learning)
Symptoms:
- Performance on old tasks drops when training on new tasks
- Model "forgets" previous capabilities
- Fine-tuning overwrites learned features
Route to: continual-learning-foundations.md
Covers:
- Why SGD causes forgetting (loss landscape geometry)
- EWC, SI, MAS (regularization approaches)
- Progressive Neural Networks, PackNet (architectural approaches)
- Experience replay, generative replay (rehearsal approaches)
- Measuring forgetting (backward/forward transfer)
When to Use:
- Training sequentially on multiple tasks
- Fine-tuning without forgetting base capabilities
- Designing systems that accumulate knowledge over time
Step 3: Gradient Isolation
Symptoms:
- New module training affects host network stability
- Want to train on host errors without backprop flowing to host
- Need gradual integration of new capacity
Route to: gradient-isolation-techniques.md
Covers:
- Freezing strategies (full, partial, scheduled)
detach() vs no_grad() semantics
- Dual-path training (residual learning on errors)
- Alpha blending for gradual integration
- Hook-based gradient surgery
When to Use:
- Training "seed" modules that learn from host errors
- Preventing catastrophic interference during growth
- Implementing safe module grafting
Step 4: PEFT Adapters (LoRA, QLoRA)
Symptoms:
- Want to fine-tune large pretrained models efficiently
- Memory constraints prevent full fine-tuning
- Need task-specific adaptation without modifying base weights
Route to: peft-adapter-techniques.md
Covers:
- LoRA (low-rank adaptation) fundamentals
- QLoRA (quantized base + LoRA adapters)
- DoRA (weight-decomposed adaptation)
- Post-LoRA PEFT variants (surveyed through ~2024): LoRA+, VeRA, PiSSA, LoftQ, rsLoRA, LongLoRA — see the knowledge-calibration note in the sheet before treating the list as current
- Adapter placement and rank-selection strategies
- Merging adapters into base model
- Multiple adapter management (multi-tenant serving of adapter pools is out of scope — named as a gap, with primary sources)
When to Use:
- Fine-tuning LLMs on limited compute
- Creating task-specific model variants
- Memory-efficient adaptation of large models
Step 5: Dynamic Architecture Patterns
Symptoms:
- Need to add capacity during training (not just before)
- Want to prune underperforming components
- Deciding when/where to grow the network
Route to: dynamic-architecture-patterns.md
Covers:
- Growth patterns (slot-based, layer widening, depth extension)
- Pruning patterns (magnitude, gradient-based, lottery ticket)
- Trigger conditions (loss plateau, contribution metrics, budgets)
- Capacity scheduling (grow-as-needed vs overparameterize-then-prune)
When to Use:
- Building networks that expand during training
- Implementing neural architecture search lite
- Managing parameter budgets with dynamic allocation
Step 6: Modular Composition
Symptoms:
- Combining outputs from multiple modules
- Designing gating/routing mechanisms
- Need graftable, replaceable components
Route to: modular-neural-composition.md
Covers:
- Combination mechanisms (additive, multiplicative, selective)
- Mixture of Experts — Shazeer baseline through Switch / Mixtral / DeepSeek-MoE, Expert Choice routing, auxiliary-loss-free balancing, sparse upcycling
- Adapter merging & task arithmetic — TIES, DARE / DARE-TIES, SLERP, model souping, MergeKit, LoraHub
- Grafting semantics (input/output attachment points)
- Interface contracts (shape matching, normalization boundaries)
- Multi-module coordination (independent, competitive, cooperative)
When to Use:
- Building modular architectures with interchangeable parts
- Implementing MoE or gated architectures
- Designing residual streams as module communication
Step 7: Lifecycle Orchestration
Symptoms:
- Need to decide WHEN to grow, train, integrate, prune
- Building state machines for module lifecycle
- Want quality gates before integration decisions
Route to: ml-lifecycle-orchestration.md
Covers:
- State machine fundamentals (states, transitions, terminals)
- Gate design patterns (structural, performance, stability, contribution)
- Transition triggers (metric-based, time-based, budget-based)
- Rollback and recovery (cooldown, hysteresis)
- Controller patterns (heuristic, learned/RL, hybrid)
When to Use:
- Designing grow/train/integrate/prune workflows
- Implementing quality gates for safe integration
- Building RL-controlled architecture decisions
Step 8: Progressive Training
Symptoms:
- New modules cause instability when integrated
- Need warmup/cooldown for safe capacity addition
- Planning multi-stage training schedules
Route to: progressive-training-strategies.md
Covers:
- Staged capacity expansion strategies
- Warmup patterns (zero-init, LR warmup, alpha ramp)
- Cooldown and stabilization (settling periods, consolidation)
- Multi-stage schedules (sequential, overlapping, budget-aware)
- Knowledge transfer between stages (inheritance, distillation)
When to Use:
- Ramping new modules safely into production
- Designing curriculum over architecture (not just data)
- Preventing stage transition shock
Common Multi-Skill Scenarios
Scenario: Building a Morphogenetic System
Need: Network that grows seeds, trains them in isolation, and grafts successful ones
Routing sequence:
- dynamic-architecture-patterns - Slot-based expansion, where seeds attach
- gradient-isolation-techniques - Train seeds on host errors without destabilizing host
- modular-neural-composition - How seed outputs blend into host stream
- ml-lifecycle-orchestration - State machine for seed lifecycle
- progressive-training-strategies - Warmup/cooldown for grafting
Scenario: Continual Learning Without Forgetting
Need: Train on sequence of tasks without catastrophic forgetting
Routing sequence:
- continual-learning-foundations - Understand forgetting, choose approach
- gradient-isolation-techniques - If using architectural approach (columns, modules)
- progressive-training-strategies - Staged training across tasks
Scenario: Neural Architecture Search (Lite)
Need: Grow/prune network based on training signal
Routing sequence:
- dynamic-architecture-patterns - Growth/pruning triggers and patterns
- ml-lifecycle-orchestration - Automation via heuristics or RL
- progressive-training-strategies - Stabilization between changes
Scenario: RL-Controlled Architecture
Need: RL agent deciding when to grow, prune, integrate
Routing sequence:
yzmir-morphogenetic-rl (companion pack) - Controller action/observation/reward design, governor and safety gates, rollback-as-RL-signal shaping. This is the canonical home for the RL-controller-decides-mutation loop.
- dynamic-architecture-patterns - What actions the RL agent can take (this pack)
- gradient-isolation-techniques - Safe exploration during training (this pack)
Boundary: yzmir-morphogenetic-rl covers WHEN/HOW the controller decides to grow. This pack covers HOW the growable network trains once a decision is made.
Rationalization Resistance Table
| Rationalization |
Reality |
Counter-Guidance |
| "Just train a bigger model from scratch" |
Transfer + growth often beats from-scratch |
"Check continual-learning-foundations for why" |
| "I'll freeze everything except the new layer" |
Full freeze may be too restrictive |
"Check gradient-isolation-techniques for partial strategies" |
| "I'll add capacity whenever loss plateaus" |
Need more than loss plateau (contribution check) |
"Check ml-lifecycle-orchestration for proper gates" |
| "Modules can just sum their outputs" |
Naive summation can cause interference |
"Check modular-neural-composition for combination mechanisms" |
| "I'll integrate immediately when training finishes" |
Need warmup/holding period |
"Check progressive-training-strategies for safe integration" |
| "EWC solves all forgetting problems" |
EWC has limitations, may need architectural approach |
"Check continual-learning-foundations for trade-offs" |
Red Flags Checklist
Watch for these signs of incorrect approach:
Relationship to Other Packs
| Request |
Primary Pack |
Why |
| "Implement PPO for architecture decisions" |
yzmir-deep-rl |
RL algorithm implementation |
| "Evaluate architecture changes without mutation" |
yzmir-deep-rl/counterfactual-reasoning |
Counterfactual simulation |
| "Debug PyTorch gradient flow" |
yzmir-pytorch-engineering |
Low-level PyTorch debugging |
| "Optimize training loop performance" |
yzmir-training-optimization |
General training optimization |
| "FSDP2 + QLoRA, FP8 / low-precision training" |
yzmir-training-optimization |
Distributed/low-precision throughput |
| "Apply PEFT recipes to LLMs (instruction tuning, RLHF)" |
yzmir-llm-specialist |
PEFT applied to LLMs in production |
| "Design transformer architecture" |
yzmir-neural-architectures |
Static architecture design |
| "Deploy morphogenetic model" |
yzmir-ml-production |
Production deployment |
| "Serve many LoRAs in one process (S-LoRA / LoRAX / Punica)" |
no pack |
Multi-tenant adapter serving is an acknowledged gap — go to the S-LoRA / Punica papers directly |
Intersection with deep-rl + morphogenetic-rl: If using RL to control architecture decisions (when to grow/prune), the canonical home for that work is yzmir-morphogenetic-rl (controller, governor, rollback shaping). Compose with yzmir-deep-rl's policy gradient / actor-critic methods for the algorithm side, and this pack's lifecycle orchestration for the network-training side.
Counterfactual evaluation: Before committing to a live mutation (grow/prune), use deep-rl's counterfactual-reasoning.md to simulate the change and evaluate outcomes without risk. This is critical for production morphogenetic systems.
Diagnostic Question Templates
Use these to route users:
Problem Classification
- "Are you training on multiple tasks sequentially, or growing a single-task network?"
- "Do you have an existing trained model you want to extend, or starting fresh?"
- "Is the issue forgetting (old performance drops) or instability (training explodes)?"
Architectural Questions
- "Where do new modules attach to the existing network?"
- "How should new module outputs combine with existing outputs?"
- "What triggers growth? Loss plateau, manual, or learned?"
Lifecycle Questions
- "What states can a module be in? (training, integrating, permanent, removed)"
- "What conditions must be met before integration?"
- "What happens if a module fails to improve performance?"
Summary: Routing Decision Tree
START: Dynamic architecture problem
├─ Forgetting old tasks?
│ └─ → continual-learning-foundations
├─ New module destabilizes existing?
│ └─ → gradient-isolation-techniques
├─ Fine-tuning LLM efficiently?
│ └─ → peft-adapter-techniques
├─ When/where to add capacity?
│ └─ → dynamic-architecture-patterns
├─ How modules combine?
│ └─ → modular-neural-composition
├─ Managing grow/train/integrate cycle?
│ └─ → ml-lifecycle-orchestration
├─ Warmup/cooldown for new capacity?
│ └─ → progressive-training-strategies
└─ Building complete morphogenetic system?
└─ → Start with dynamic-architecture-patterns
→ Then gradient-isolation-techniques
→ Then ml-lifecycle-orchestration
Reference Sheets
After routing, load the appropriate reference sheet:
- continual-learning-foundations.md - EWC, PackNet, rehearsal, forgetting theory
- gradient-isolation-techniques.md - Freezing, detach, alpha blending, hook surgery
- peft-adapter-techniques.md - LoRA, QLoRA, DoRA, adapter merging
- dynamic-architecture-patterns.md - Grow/prune patterns, triggers, scheduling
- modular-neural-composition.md - MoE, gating, grafting, interface contracts
- ml-lifecycle-orchestration.md - State machines, gates, controllers
- progressive-training-strategies.md - Staged expansion, warmup/cooldown
1---2name: using-dynamic-architectures3description: Use when building networks that grow, prune, or adapt topology during training. Routes to continual learning, gradient isolation, modular composition, and lifecycle orchestration skills.4---56# Dynamic Architectures Meta-Skill78## When to Use This Skill910Invoke this meta-skill when you encounter:1112- **Growing Networks**: Adding capacity during training (new layers, neurons, modules)13- **Pruning Networks**: Removing capacity that isn't contributing14- **Continual Learning**: Training on new tasks without forgetting old ones15- **Gradient Isolation**: Training new modules without destabilizing existing weights16- **Modular Composition**: Building networks from graftable, composable components17- **Lifecycle Management**: State machines controlling when to grow, train, integrate, prune18- **Progressive Training**: Staged capability expansion with warmup and cooldown1920This is the **entry point** for dynamic/morphogenetic neural network patterns. It routes to 7 specialized reference sheets.2122## How to Access Reference Sheets2324**IMPORTANT**: All reference sheets are located in the SAME DIRECTORY as this SKILL.md file.2526When this skill is loaded from:27 `skills/using-dynamic-architectures/SKILL.md`2829Reference sheets like `continual-learning-foundations.md` are at:30 `skills/using-dynamic-architectures/continual-learning-foundations.md`3132NOT at:33 `skills/continual-learning-foundations.md` (WRONG PATH)3435---3637## Core Principle3839**Dynamic architectures grow capability, not just tune weights.**4041Static networks are a guess about capacity. Dynamic networks let training signal drive structure. The challenge is growing without forgetting, integrating without destabilizing, and knowing when to act.4243Key tensions:44- **Stability vs. Plasticity**: Preserve existing knowledge while adding new capacity45- **Isolation vs. Integration**: Train new modules separately, then merge carefully46- **Exploration vs. Exploitation**: When to add capacity vs. when to stabilize4748## The 7 Dynamic Architecture Skills49501. **continual-learning-foundations** - EWC, PackNet, rehearsal strategies, catastrophic forgetting theory512. **gradient-isolation-techniques** - Freezing, gradient masking, stop_grad patterns, alpha blending523. **peft-adapter-techniques** - LoRA, QLoRA, DoRA, adapter placement, merging strategies534. **dynamic-architecture-patterns** - Grow/prune patterns, slot-based expansion, capacity scheduling545. **modular-neural-composition** - MoE, gating, grafting semantics, interface contracts556. **ml-lifecycle-orchestration** - State machines, quality gates, transition triggers, controllers567. **progressive-training-strategies** - Staged expansion, warmup/cooldown, knowledge transfer5758## Routing Decision Framework5960### Step 1: Identify the Core Problem6162**Diagnostic Questions:**6364- "Are you trying to prevent forgetting when training on new data/tasks?"65- "Are you trying to add new capacity to an existing trained network?"66- "Are you designing how multiple modules combine?"67- "Are you deciding WHEN to grow, prune, or integrate?"6869**Quick Routing:**7071| Problem | Primary Skill |72|---------|---------------|73| "Model forgets old tasks when I train new ones" | continual-learning-foundations |74| "New module destabilizes existing weights" | gradient-isolation-techniques |75| "Fine-tune LLM efficiently without full training" | peft-adapter-techniques |76| "Pick a post-LoRA PEFT variant (VeRA / LoRA+ / PiSSA / LoftQ / rsLoRA)" | peft-adapter-techniques |77| "When should I add more capacity?" | dynamic-architecture-patterns |78| "How do module outputs combine?" | modular-neural-composition |79| "Merge several fine-tuned checkpoints (TIES / DARE / SLERP / MergeKit)" | modular-neural-composition |80| "Production-grade MoE (Switch / Mixtral / DeepSeek-MoE / Expert Choice)" | modular-neural-composition |81| "How do I manage the grow/train/integrate cycle?" | ml-lifecycle-orchestration |82| "How do I warm up new modules safely?" | progressive-training-strategies |83| "Serve many LoRAs in one process (S-LoRA / LoRAX / Punica)" | *not covered by this pack* — see the primary sources listed in peft-adapter-techniques.md |8485---8687### Step 2: Catastrophic Forgetting (Continual Learning)8889**Symptoms:**9091- Performance on old tasks drops when training on new tasks92- Model "forgets" previous capabilities93- Fine-tuning overwrites learned features9495**Route to:** [continual-learning-foundations.md](continual-learning-foundations.md)9697**Covers:**98- Why SGD causes forgetting (loss landscape geometry)99- EWC, SI, MAS (regularization approaches)100- Progressive Neural Networks, PackNet (architectural approaches)101- Experience replay, generative replay (rehearsal approaches)102- Measuring forgetting (backward/forward transfer)103104**When to Use:**105- Training sequentially on multiple tasks106- Fine-tuning without forgetting base capabilities107- Designing systems that accumulate knowledge over time108109---110111### Step 3: Gradient Isolation112113**Symptoms:**114115- New module training affects host network stability116- Want to train on host errors without backprop flowing to host117- Need gradual integration of new capacity118119**Route to:** [gradient-isolation-techniques.md](gradient-isolation-techniques.md)120121**Covers:**122- Freezing strategies (full, partial, scheduled)123- `detach()` vs `no_grad()` semantics124- Dual-path training (residual learning on errors)125- Alpha blending for gradual integration126- Hook-based gradient surgery127128**When to Use:**129- Training "seed" modules that learn from host errors130- Preventing catastrophic interference during growth131- Implementing safe module grafting132133---134135### Step 4: PEFT Adapters (LoRA, QLoRA)136137**Symptoms:**138139- Want to fine-tune large pretrained models efficiently140- Memory constraints prevent full fine-tuning141- Need task-specific adaptation without modifying base weights142143**Route to:** [peft-adapter-techniques.md](peft-adapter-techniques.md)144145**Covers:**146- LoRA (low-rank adaptation) fundamentals147- QLoRA (quantized base + LoRA adapters)148- DoRA (weight-decomposed adaptation)149- Post-LoRA PEFT variants (surveyed through ~2024): LoRA+, VeRA, PiSSA, LoftQ, rsLoRA, LongLoRA — see the knowledge-calibration note in the sheet before treating the list as current150- Adapter placement and rank-selection strategies151- Merging adapters into base model152- Multiple adapter management (multi-tenant *serving* of adapter pools is out of scope — named as a gap, with primary sources)153154**When to Use:**155- Fine-tuning LLMs on limited compute156- Creating task-specific model variants157- Memory-efficient adaptation of large models158159---160161### Step 5: Dynamic Architecture Patterns162163**Symptoms:**164165- Need to add capacity during training (not just before)166- Want to prune underperforming components167- Deciding when/where to grow the network168169**Route to:** [dynamic-architecture-patterns.md](dynamic-architecture-patterns.md)170171**Covers:**172- Growth patterns (slot-based, layer widening, depth extension)173- Pruning patterns (magnitude, gradient-based, lottery ticket)174- Trigger conditions (loss plateau, contribution metrics, budgets)175- Capacity scheduling (grow-as-needed vs overparameterize-then-prune)176177**When to Use:**178- Building networks that expand during training179- Implementing neural architecture search lite180- Managing parameter budgets with dynamic allocation181182---183184### Step 6: Modular Composition185186**Symptoms:**187188- Combining outputs from multiple modules189- Designing gating/routing mechanisms190- Need graftable, replaceable components191192**Route to:** [modular-neural-composition.md](modular-neural-composition.md)193194**Covers:**195- Combination mechanisms (additive, multiplicative, selective)196- Mixture of Experts — Shazeer baseline through Switch / Mixtral / DeepSeek-MoE, Expert Choice routing, auxiliary-loss-free balancing, sparse upcycling197- Adapter merging & task arithmetic — TIES, DARE / DARE-TIES, SLERP, model souping, MergeKit, LoraHub198- Grafting semantics (input/output attachment points)199- Interface contracts (shape matching, normalization boundaries)200- Multi-module coordination (independent, competitive, cooperative)201202**When to Use:**203- Building modular architectures with interchangeable parts204- Implementing MoE or gated architectures205- Designing residual streams as module communication206207---208209### Step 7: Lifecycle Orchestration210211**Symptoms:**212213- Need to decide WHEN to grow, train, integrate, prune214- Building state machines for module lifecycle215- Want quality gates before integration decisions216217**Route to:** [ml-lifecycle-orchestration.md](ml-lifecycle-orchestration.md)218219**Covers:**220- State machine fundamentals (states, transitions, terminals)221- Gate design patterns (structural, performance, stability, contribution)222- Transition triggers (metric-based, time-based, budget-based)223- Rollback and recovery (cooldown, hysteresis)224- Controller patterns (heuristic, learned/RL, hybrid)225226**When to Use:**227- Designing grow/train/integrate/prune workflows228- Implementing quality gates for safe integration229- Building RL-controlled architecture decisions230231---232233### Step 8: Progressive Training234235**Symptoms:**236237- New modules cause instability when integrated238- Need warmup/cooldown for safe capacity addition239- Planning multi-stage training schedules240241**Route to:** [progressive-training-strategies.md](progressive-training-strategies.md)242243**Covers:**244- Staged capacity expansion strategies245- Warmup patterns (zero-init, LR warmup, alpha ramp)246- Cooldown and stabilization (settling periods, consolidation)247- Multi-stage schedules (sequential, overlapping, budget-aware)248- Knowledge transfer between stages (inheritance, distillation)249250**When to Use:**251- Ramping new modules safely into production252- Designing curriculum over architecture (not just data)253- Preventing stage transition shock254255---256257## Common Multi-Skill Scenarios258259### Scenario: Building a Morphogenetic System260261**Need:** Network that grows seeds, trains them in isolation, and grafts successful ones262263**Routing sequence:**2641. **dynamic-architecture-patterns** - Slot-based expansion, where seeds attach2652. **gradient-isolation-techniques** - Train seeds on host errors without destabilizing host2663. **modular-neural-composition** - How seed outputs blend into host stream2674. **ml-lifecycle-orchestration** - State machine for seed lifecycle2685. **progressive-training-strategies** - Warmup/cooldown for grafting269270### Scenario: Continual Learning Without Forgetting271272**Need:** Train on sequence of tasks without catastrophic forgetting273274**Routing sequence:**2751. **continual-learning-foundations** - Understand forgetting, choose approach2762. **gradient-isolation-techniques** - If using architectural approach (columns, modules)2773. **progressive-training-strategies** - Staged training across tasks278279### Scenario: Neural Architecture Search (Lite)280281**Need:** Grow/prune network based on training signal282283**Routing sequence:**2841. **dynamic-architecture-patterns** - Growth/pruning triggers and patterns2852. **ml-lifecycle-orchestration** - Automation via heuristics or RL2863. **progressive-training-strategies** - Stabilization between changes287288### Scenario: RL-Controlled Architecture289290**Need:** RL agent deciding when to grow, prune, integrate291292**Routing sequence:**2931. **`yzmir-morphogenetic-rl`** (companion pack) - Controller action/observation/reward design, governor and safety gates, rollback-as-RL-signal shaping. This is the canonical home for the RL-controller-decides-mutation loop.2942. **dynamic-architecture-patterns** - What actions the RL agent can take (this pack)2953. **gradient-isolation-techniques** - Safe exploration during training (this pack)296297**Boundary:** `yzmir-morphogenetic-rl` covers WHEN/HOW the controller decides to grow. This pack covers HOW the growable network trains once a decision is made.298299---300301## Rationalization Resistance Table302303| Rationalization | Reality | Counter-Guidance |304|-----------------|---------|------------------|305| "Just train a bigger model from scratch" | Transfer + growth often beats from-scratch | "Check continual-learning-foundations for why" |306| "I'll freeze everything except the new layer" | Full freeze may be too restrictive | "Check gradient-isolation-techniques for partial strategies" |307| "I'll add capacity whenever loss plateaus" | Need more than loss plateau (contribution check) | "Check ml-lifecycle-orchestration for proper gates" |308| "Modules can just sum their outputs" | Naive summation can cause interference | "Check modular-neural-composition for combination mechanisms" |309| "I'll integrate immediately when training finishes" | Need warmup/holding period | "Check progressive-training-strategies for safe integration" |310| "EWC solves all forgetting problems" | EWC has limitations, may need architectural approach | "Check continual-learning-foundations for trade-offs" |311312---313314## Red Flags Checklist315316Watch for these signs of incorrect approach:317318- [ ] **No Isolation**: Training new modules without gradient isolation from host319- [ ] **No Warmup**: Integrating new capacity at full amplitude immediately320- [ ] **No Gates**: Integrating based only on time, not performance metrics321- [ ] **Naive Combination**: Summing module outputs without gating or blending322- [ ] **Ignoring Forgetting**: Adding new tasks without measuring old task performance323- [ ] **No Rollback**: No plan for what happens if integration fails324325---326327## Relationship to Other Packs328329| Request | Primary Pack | Why |330|---------|--------------|-----|331| "Implement PPO for architecture decisions" | yzmir-deep-rl | RL algorithm implementation |332| "Evaluate architecture changes without mutation" | yzmir-deep-rl/counterfactual-reasoning | Counterfactual simulation |333| "Debug PyTorch gradient flow" | yzmir-pytorch-engineering | Low-level PyTorch debugging |334| "Optimize training loop performance" | yzmir-training-optimization | General training optimization |335| "FSDP2 + QLoRA, FP8 / low-precision training" | yzmir-training-optimization | Distributed/low-precision throughput |336| "Apply PEFT recipes to LLMs (instruction tuning, RLHF)" | yzmir-llm-specialist | PEFT *applied to LLMs in production* |337| "Design transformer architecture" | yzmir-neural-architectures | Static architecture design |338| "Deploy morphogenetic model" | yzmir-ml-production | Production deployment |339| "Serve many LoRAs in one process (S-LoRA / LoRAX / Punica)" | *no pack* | Multi-tenant adapter serving is an acknowledged gap — go to the S-LoRA / Punica papers directly |340341**Intersection with deep-rl + morphogenetic-rl:** If using RL to control architecture decisions (when to grow/prune), the canonical home for that work is `yzmir-morphogenetic-rl` (controller, governor, rollback shaping). Compose with `yzmir-deep-rl`'s policy gradient / actor-critic methods for the algorithm side, and this pack's lifecycle orchestration for the network-training side.342343**Counterfactual evaluation:** Before committing to a live mutation (grow/prune), use deep-rl's `counterfactual-reasoning.md` to simulate the change and evaluate outcomes without risk. This is critical for production morphogenetic systems.344345---346347## Diagnostic Question Templates348349Use these to route users:350351### Problem Classification352353- "Are you training on multiple tasks sequentially, or growing a single-task network?"354- "Do you have an existing trained model you want to extend, or starting fresh?"355- "Is the issue forgetting (old performance drops) or instability (training explodes)?"356357### Architectural Questions358359- "Where do new modules attach to the existing network?"360- "How should new module outputs combine with existing outputs?"361- "What triggers growth? Loss plateau, manual, or learned?"362363### Lifecycle Questions364365- "What states can a module be in? (training, integrating, permanent, removed)"366- "What conditions must be met before integration?"367- "What happens if a module fails to improve performance?"368369---370371## Summary: Routing Decision Tree372373```374START: Dynamic architecture problem375376├─ Forgetting old tasks?377│ └─ → continual-learning-foundations378379├─ New module destabilizes existing?380│ └─ → gradient-isolation-techniques381382├─ Fine-tuning LLM efficiently?383│ └─ → peft-adapter-techniques384385├─ When/where to add capacity?386│ └─ → dynamic-architecture-patterns387388├─ How modules combine?389│ └─ → modular-neural-composition390391├─ Managing grow/train/integrate cycle?392│ └─ → ml-lifecycle-orchestration393394├─ Warmup/cooldown for new capacity?395│ └─ → progressive-training-strategies396397└─ Building complete morphogenetic system?398 └─ → Start with dynamic-architecture-patterns399 → Then gradient-isolation-techniques400 → Then ml-lifecycle-orchestration401```402403---404405## Reference Sheets406407After routing, load the appropriate reference sheet:4084091. [continual-learning-foundations.md](continual-learning-foundations.md) - EWC, PackNet, rehearsal, forgetting theory4102. [gradient-isolation-techniques.md](gradient-isolation-techniques.md) - Freezing, detach, alpha blending, hook surgery4113. [peft-adapter-techniques.md](peft-adapter-techniques.md) - LoRA, QLoRA, DoRA, adapter merging4124. [dynamic-architecture-patterns.md](dynamic-architecture-patterns.md) - Grow/prune patterns, triggers, scheduling4135. [modular-neural-composition.md](modular-neural-composition.md) - MoE, gating, grafting, interface contracts4146. [ml-lifecycle-orchestration.md](ml-lifecycle-orchestration.md) - State machines, gates, controllers4157. [progressive-training-strategies.md](progressive-training-strategies.md) - Staged expansion, warmup/cooldown