meta-orchestrator

To prevent frame-drift across multiple orchestrator sessions, you need frame-shift governance to coordinate cross-project prioritization, scope meta-level decisions, and enforce spawn discipline. This maintains alignment and prevents fragmentation over time.

The best way to manage orchestrator session handoffs is to automate handoff review by evaluating SESSION_HANDOFF.md files. This detects friction patterns and drives systemic improvements to reduce future handoff friction.

Capturing strategic decisions in session management workflows requires distinguishing WHICH vs HOW decisions. You then seed the knowledge base with these decisions and improvements to maintain systemic evolution and cross-project focus.

Yes, you need the orchestrator dependency to use meta-orchestrator. It provides a high-level management layer that enforces spawn discipline, guardrails, and pattern detection to oversee and improve existing orchestrator sessions.

You should not use a meta-level orchestrator for workflow sessions if you lack recurring friction patterns or cross-project handoffs. It is designed for advanced system evolution and frame-shift governance, not simple, isolated task execution.

Orchestrator session fragmentation occurs due to unmanaged frame-drift across projects and time. You fix it by applying frame-shift governance, enforcing spawn discipline, and proposing tooling changes based on detected friction patterns.