solution-architecture

name	solution-architecture
description	Use when an approved Electron PRD needs architecture, process ownership, data flow, IPC contracts, stack decisions, migration, or rollback design. Do not use before PRD approval or for feature coding, independent review, debugging, or release execution.

Solution Architecture

Write the smallest implementable, secure design in the sidecar CONTRACT.md.

1. Read sidecar PROJECT.md, approved PRD.md, repository evidence, and references/electron-architecture.md.
2. Detect and preserve the existing stack and commands. Do not select a business stack without user approval.
3. Assign renderer, preload, main, utility/worker, and shared ownership. Define serializable contracts, runtime validation, sender authorization, cancellation, cleanup, stable errors, data ownership, migration, rollback, development/packaged behavior, and platform differences.
4. Complete the CONTRACT sections for renderer, main/preload/IPC, errors, permissions, and cross-track acceptance. Make frontend/backend scopes disjoint or state an explicit serialized dependency.
5. Record alternatives, risks, security/privacy impact, and approval in the sidecar. After approval, route to mts-split.

Do not code from an unapproved contract or use the preload bridge as a generic privileged API. Do not select authority based on host brand.