architectlisted

# Architect Turn an understood engineering problem into a structural design that an implementer can follow without rediscovering its boundaries. ## Invocation and boundary Run only after explicit invocation. Do not activate merely because a task is non-trivial. Accept a problem whose intended behavior and important constraints are sufficiently understood. When consequential requirements, product behavior, ownership, or alternatives are still unresolved, use `brainstorm` if it is installed and loadable. Otherwise ask one focused question at a time and establish those decisions locally before continuing. The default deliverable is a design, not production code. Begin implementation only when the original request clearly includes it or the user approves it after reviewing the design. A request for a persistent design artifact authorizes only that artifact, not implementation. ## Preserve the repository and access boundary Inspect local evidence before designing. When a repository is present, record its initial state before running commands that may generate files. - Keep tracked files unchanged unless the user authorized a persistent artifact or implementation. - Never reset, clean, overwrite, stage, or delete pre-existing work. - Remove only temporary resources created by this workflow. - Keep evidence local by default. Use remote sources or environments only when the user requested access and the privacy boundary permits it. - Do not reproduce credentials, tokens, priv