Explore project-delivery for coordinated multi-day project builds

[BjRo]

Motivation

Explore an explicitly initiated project-delivery experience in which an agent can spend one to multiple days building a substantial, high-quality project in coordinated steps, using adaptive-delivery for each bounded milestone.

A thorough project specification is a prerequisite and remains the reference throughout execution. Completing individual tasks is insufficient evidence that the integrated product satisfies the original intent.

The proposed project owner maintains that intent, selects successive milestones, and assesses the whole project. Each adaptive-delivery owner retains responsibility for its bounded engineering outcome.

Acceptance criteria

• Begin from a thorough project specification that defines product behavior and user journeys, failure cases, quality expectations, constraints, exclusions, acceptance evidence, and decision authority.
• Support coordinated work over one to multiple days, with each bounded delivery milestone delegated through adaptive-delivery.
• Preserve the specification and accepted decisions across context changes so work can establish what remains unfinished, what decisions are authorized, and how completion is demonstrated.
• Allow milestone sequencing and implementation plans to adapt to evidence while preserving the agreed project outcome. Changes to scope or acceptance criteria require an explicit decision.
• Account for dependencies between milestones and assess the integrated result against complete user journeys and project-level acceptance criteria.
• Keep implementation, repair, and milestone verification with the relevant adaptive-delivery owner; the project owner selects and assesses project-level outcomes.
• Define the finish condition, execution/spending limits, human escalation, and the treatment of pending questions.
• Establish an explicit composition contract for repeated milestone delegation and project-level assessment. Current recipes delegate once; this exploration does not silently extend their authority or introduce a general workflow runtime.
• Evaluate the hypothesis against one adaptive-delivery owner handling the same substantial project from the same specification, comparing coherence, missed requirements, defects, human interventions, and cost before claiming an improvement.

Open questions

• How much product and design judgment may the project owner exercise independently within the specification?
• Does multi-day delivery need to survive closed sessions or machine restarts, and what environment support would provide reliable execution and resumption?
• What new orchestration boundary should own successive milestone selection while retaining the current native-owner architecture?

This issue captures an exploratory direction, not a settled implementation plan or authorization to restore retired orchestration machinery.

Repository sources: docs/specs/layer-composition.md, docs/design.md, and docs/decisions/ADR-0004-use-native-goal-ownership-for-core-orchestration.md.