heir-sync-management
Heir Sync Management
Safely synchronize cognitive architecture from Master to Heirs without contamination.
Scope: Master-only skill. Covers sync pipelines, PII protection, drift detection, skill promotion, and clean-slate distribution.
Core Concepts
| Concept | Definition |
|---|---|
| Heir | Platform-specific deployment inheriting Master's DNA (VS Code, M365, GitHub Copilot Web) |
| Deployment Channel | Delivery mechanism for an heir (Marketplace, Teams Package, .github/ commit) |
| Integration | Cross-heir communication (OneDrive Sync, GitHub Cloud) |
| Translation Heir | Heir requiring format/schema conversion (e.g., M365 — export pipeline) |
| Deployment Heir | Heir needing only configuration, no code translation (e.g., GitHub Copilot Web — .github/ files only) |
| Contamination | Master-specific data leaking into heir packages |
| Drift | Heir diverging from Master's architecture over time |
| Promotion | Elevating heir-developed capabilities back to Master |
More from fabioc-aloha/lithium
bicep avm mastery
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure
9brain qa
Semantic, logic, code, and architectural validation of Alex's cognitive architecture — not just file counts, but meaning coherence
1infrastructure as code skill
**Domain**: DevOps & Cloud Engineering
1skill-activation
Internal metacognitive skill for automatic capability discovery — self-triggers when uncertain about available skills
1dream-state
Neural maintenance, synapse validation, automated health diagnostics, and unconscious processing
1ui/ux design
User interface design, user experience optimization, accessibility compliance, design systems
1