orchestrator-session-context-lifecycle

To keep orchestrator sessions resumable across gate-based workflows, you need a structured lifecycle that manages session resumes, gate progression, and checkpointing. This ensures context is maintained and sessions can resume without losing state.

Orchestrator session context maintenance is the process of emitting context updates and persisting universal principles across actions. You need it when workflows span multiple gates and risk losing context, becoming non-resumable, or hindering audits.

To start or resume an orchestrator session while tracking blockers, initialize the session context and record gate status, artifacts, blockers, and next micro-goals. This enables part-time session management and structured gate transitions.

Log archiving for orchestrator sessions works by archiving per-slice logs while preserving global governance history. This maintains an auditable record of decisions and actions across the session lifecycle.

Yes, you can track parallel agent runs and surface their statuses asynchronously through async run tracking. This monitors parallel agent executions and provides visibility into their current statuses during the session.

No dependencies are required to automate orchestrator session lifecycles. The skill operates independently to manage starting, resuming, and closing sessions, including context maintenance, memory updates, and log archiving.