Architect

Resolve the design question before implementation. A mechanical caller or signature change does not need a design exercise.

Scope

Inspect the relevant contracts and consumers. Use How when an architectural explanation would resolve a material uncertainty. Reuse an existing source model instead of repeating subsystem exploration.

Sketch only the types, signatures, or module boundaries needed to assess the decision. Compare distinct designs when the user requests alternatives or consequential uncertainty remains. Use independent candidates when separate expertise justifies the cost and delegation is available. Do not require a fixed candidate count or an unavailable comparison skill. For a requested multi-candidate review, use the candidate brief and design rationale.

Assess interface depth, ownership, and consumer requirements. Use design red flags when a proposed abstraction needs review. Use architecture guidance for prerequisite and dependency decisions.

Completion

For design-only requests, return the recommendation, necessary sketch, tradeoffs, and unresolved decisions. For authorized implementation, continue through Programming without another approval gate. Pause when the user requests a checkpoint or a missing decision materially changes scope.

If implementation disproves the design, reassess the affected assumption. Revise the sketch or compare another design when evidence warrants it. Do not restart the complete investigation for an ordinary parameter correction.

Use verification guidance to assess the result and reuse valid evidence.