content-inheritancelisted

# Content Inheritance Dead content has living parts. Harvest them. ## When to Activate - User says `/inherit` or `/content-inheritance` - User says `/inherit {file}` to harvest a specific piece - Auto-suggested by content-network for dead nodes - Auto-suggested by content-expiry for expired content ## Commands ### `/inherit` — Scan for harvestable dead content ### `/inherit {file}` — Harvest specific content ### `/inherit transplant {source} {target}` — Move parts between content ## Harvestable Parts | Part | Example | Reuse Potential | |------|---------|----------------| | Data points | "87% of..." with source | Very High — facts don't expire | | Frameworks | "The 3-step method" | Very High — structures are reusable | | Examples | Case study, personal story | High — stories are timeless | | Quotes | Expert quotes with attribution | High | | Analogies | "AI is like a Swiss Army knife" | Medium | | Structure | Section flow, heading pattern | Medium | | CTAs | Well-performing call to action | High | | Visuals | Image prompts, design specs | Medium | ## Workflow ### Step 1: Identify Dead Content ``` Dead content scan (from content-network + expiry): Candidates for inheritance: 1. "{title}" ({date}) — DEAD ({N} PV, declining) Harvestable parts: - 3 data points with sources - 1 original framework ("The X Method") - 1 case study (still relevant) - 2 strong analogies Value: HIGH — good parts in a dead article 2. "{title}" ({date}) — EXPIRED (da