| name | integration/ecosystem-sync |
| description | Use when synchronizing intelligence, state, or knowledge across the FrankX ecosystem — ensures consistency and coherence across ACOS, Arcanea, AI-Ops, and Starlight. Default skill for Starlight Orchestrator and Starlight Prime. |
| type | developer-tooling |
Ecosystem Sync
"When all systems are in sync, the whole becomes unstoppable."
When This Skill Activates
- Synchronizing state, patterns, or knowledge across the ecosystem
- Keywords: "sync", "synchronize", "align", "ecosystem", "all systems"
- Default for: Starlight Orchestrator, Starlight Prime
What This Skill Does
Synchronizes intelligence, state, and knowledge across all FrankX ecosystem repositories. Ensures consistency and coherence across ACOS, Arcanea, AI-Ops, and Starlight.
Procedures
Procedure 1: State Synchronization
- Read current state from all repo contexts
- Identify state discrepancies or drift
- Determine the authoritative source for each piece of state
- Update non-authoritative copies to match
- Log sync operations in Operational Vault
- Send sync confirmation via Broadcast Channel
Procedure 2: Pattern Propagation
- Identify patterns that should be consistent across repos
- Check each repo's implementation of the pattern
- Find repos that are behind or divergent
- Create update recommendations for each repo
- Package as Transmissions to respective channels
- Track propagation status
Procedure 3: Knowledge Federation
- Identify knowledge that exists in one repo but is relevant to others
- Extract and package the knowledge
- Adapt to each target repo's format and conventions
- Send via appropriate Transmission channels
- Store federation event in Wisdom Vault
- Update cross-references in vault indices
Integration Points
- Vault: Operational Vault (sync state), Wisdom Vault (federated knowledge)
- Context: All repo contexts (read and update)
- Transmissions: All channels (sync communication)
- Agents: Orchestrator (primary), Prime (authorization)
Quality Criteria
- Is synchronization complete (no missed repos)?
- Are authoritative sources correctly identified?
- Are patterns properly adapted per repo conventions?
- Is sync state tracked and auditable?
