start-orchestrator

To bootstrap a new project workflow, the orchestrator detects the absence of an instruction file and automatically begins the CataForge startup path from your project description without writing downstream documentation.

To resume an in-progress workflow safely, the orchestrator recognizes continuation mode, checks the framework.json version state, and restores the current phase-aware routing to recover your project.

You need to check the framework version for an existing deployment when resuming an orchestration flow, ensuring the framework.json state is inspected to safely restore and route the current project phase.

No, the orchestrator does not write downstream documentation itself; it strictly handles instruction file detection, framework.json inspection, and initial phase-aware handoff into the orchestrated process.

Starting a CataForge project requires providing a project description or continuation state so the orchestrator can detect instruction files, inspect framework versions, and route the workflow phases.