browser/openspec/changes/architecture-delivery-stream/proposal.md

Why

The bootstrap architecture is broad enough that implementing it as one large change would make review, verification, and rollback hard. The project needs an explicit OpenSpec delivery stream that breaks the platform, run executor, frontend console, and plugin system into ordered, single-session changes that can be implemented one at a time.

What Changes

• Add a delivery workflow for creating and implementing architecture OpenSpec changes in dependency order.
• Define a per-change handoff format so each new chat can implement exactly one OpenSpec change without guessing scope.
• Define closing criteria for each implementation chat before the next OpenSpec change is started.
• Define the initial architecture backlog across platform/, run/, platform_web/, and plugins/.
• Keep the bootstrap architecture as the baseline and require every follow-up change to reference it instead of redefining product scope.

Capabilities

New Capabilities

• architecture-delivery-workflow: Ordered OpenSpec backlog, per-change handoff rules, implementation-chat closure criteria, and progress tracking for the full architecture delivery stream.

Modified Capabilities

• None.

Impact

• Adds planning artifacts under openspec/changes/architecture-delivery-stream/.
• Affects how future OpenSpec changes are created, implemented, validated, and handed off between chats.
• Does not implement backend, run, frontend, or plugin runtime code directly.
• Requires future implementation chats to run scripts/check-structure.sh and openspec validate <change> --strict before marking work complete.