nw-solution-architect-full-design

name	nw-solution-architect-full-design
description	PROCEDURE — author or amend one durable application DESIGN authority. Trigger: a non-Auto DESIGN mandate.
disable-model-invocation	true

Full Application DESIGN

Kind: PROCEDURE. Job: close one durable application DESIGN authority. Trigger: a non-Auto-shaped DESIGN mandate that is not an AUTO-ARCHITECTURE-CONSULT envelope. Exact Auto uses nw-solution-architect-auto-consult; malformed Auto is BLOCKED by parent grammar, never routed here.

Deterministic sequence

1. Ground — load nw-design; ask only plain-language questions that change equality, carrier, law or irreducible trade-off. Before solution selection give its reviewer ONLY mandate/binding constraints, never authority, algebra, proofs or conclusions; receive its precommitted counterexample challenge. Resolve facts; choose REUSE, EXTEND, REPLACE or CREATE_NEW. Gate: CREATE_NEW disproves safe reuse.
2. Design — decide prefactoring, ports, ownership, paradigm, affected-layer success/refusal/retry/failure laws and triggered residual stress. Gate: caller-visible observations and failure translation are named.
3. Construct — apply triggered algebraic, certainty and stress lenses. In the same authority record nw-design's projection/risk and each public-value witness: producer, consumer, port, invocation, existing symbol or concrete DNB site/symbol, and separate DESIGN/runtime safety/inhabitation/reachability/ liveness status. Gate: no generic site; bounded/synchronous affects liveness only.
4. Formal proof — consume nw-design's bounded fact record only for a separately selected proof obligation; its formal procedure owns availability and refinement. Gate: unavailable tooling affects only that proof.
5. Close substrate — for RED_TO_GREEN read the installed thin schema at ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/lib/nWave/schemas/thin-delivery-contract.schema.json and use its exact closed obligation enum. Label each obligation N. **TOKEN**. Record law, input domain, real public observation, symbols/helper, fixture/lifecycle, one oracle, at most two examples, argv and intended RED. Add PBT only for a selected broad/generated-domain law; otherwise NOT_APPLICABLE (finite exhaustive domain/no law). Gate: no guessed dependency, test-local driving seam or alternate label grammar.
6. Resolve dependencies — establish owner, version, manifest/lock and runtime presence; make the authority-grounded delta when absent, then prove declared=yes and present=yes. Gate: otherwise BLOCKED, never DISTILL/ATD.
7. Review and hand off — continue the same review against its precommitted challenge/criteria. Preserve the brief/ADR as sole authority, then read back the target permanent authority after its final Write/Edit; derive the section-anchor from an actually present Markdown heading, never invent an anchor from a task name or summary. Gate: a missing path or heading returns ARCHITECTURE-BLOCKED; otherwise return IDs, route, boundaries, obligations and oracle, with no DeliveryContract or duplicate narrative.

Composition

• nw-design — durable authority; owns seeded DAG/unseeded-cycle rejection, affected-layer laws and counterexample discipline.
• nw-code-analysis-port — repository structural facts.
• nw-algebraic-design-protocol, nw-certainty-by-construction, nw-stress-analysis — applicable lenses.
• nw-solution-architect-formal-verification — nested formal claim.

Verification

• Authority contains route, boundaries, laws, residue and test substrate.
• Each declared dependency is present in the actual verification runtime.
• Every constructive/refinement claim separates DESIGN from runtime evidence; exact producer/consumer/invocation and citations are closed.
• Terminal result is delivered verbatim to the team lead.