Architect
Read the caller first. Architecture starts from use, not from an isolated abstraction.
- Name the domain data shape and invariants.
- Map ownership and lifecycle. For concurrency, identify what is truly shared before proposing synchronization.
- Draft 2-3 boundary shapes when the decision is contested. If
delegateis available, assign independent designs; otherwise keep alternatives explicit and sequential. - Compare on reader load, invalid states, migration cost, idempotence, testability, and fit with existing architecture.
- Select the smallest coherent shape and write the caller-facing signature/contract before implementation.
- Use
interrogatefor high-risk or contested decisions.