solution-architecture-brief

name	solution-architecture-brief
description	Produce a customer-facing solution architecture that maps supported product components and integration boundaries to the customer environment without redefining core product architecture.

Solution Architecture Brief

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using customer topology, supported interfaces, security model, scale needs, and deployment constraints. Do not fill material gaps with assumptions when they can change the result.
3. Inventory systems and trust boundaries, map data/control flows, identify responsibilities, document assumptions, and validate against product architects when needed.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

The brief is implementable using supported contracts and makes customer/product ownership explicit.