ITSOL Initiative Delivery

Use this workflow for a broad business source whose complete intended outcome needs multiple implementation and QA phases. It is a delivery-scope layer, not a fourth authority mode: resolve itsol-workflow-mode, then record delivery_scope: initiative. Normally combine it with autonomous-planned; governed remains valid when the user requests initiative-level approvals. Never use direct for an initiative.

Non-negotiable contract

• Analyze the complete source before choosing implementation work.
• Give every requirement a stable ID and explicit disposition. Never silently pick one slice and call the initiative complete.
• Preserve the original source as an immutable snapshot. Maintain clarified intent, roadmap, architecture, decisions, traceability, progress, and phase evidence as living repository artifacts.
• Use the harness-native durable initiative-state capability. Do not rely on conversation history as the only state.
• Decompose work into dependency-aware, outcome-oriented vertical phases. Existing Business, Technical, TDD, delegation, code-review, integration, and QA workflows apply inside each phase.
• Self-review the initiative roadmap and required phase plans proportionately. Use isolated review when required by policy or justified by material initiative risk; a materially changed reviewed roadmap invalidates its earlier verdict.
• Continue through executable phases without returning for routine approval in autonomous-planned.
• Ask only for a material business, product, scope, data, security, rollout, or architecture decision that cannot be safely recommended under delegated authority, or for a separately protected action.

Lifecycle