design-ux-architecture

UX architecture

Version-Timestamp: 2026-09-12T11:35:16-04:00

Project-local instruction draft. Manual selection does not install a tool or grant permissions.

Inputs

Research questions, participant constraints/consent, evidence, actor/persona needs selected under the audience input rule, business requirements and current service boundaries. Reuse valid existing prerequisites; missing audience research follows the shared rule's hold or specifically authorized provisional-exploration branch, never a self-declared exception.

Method

Define research questions and how each answer changes a decision. Choose a method and recruitment criteria, note sampling limitations and avoid presenting synthetic participants as real users. Separate observation, interpretation and recommendation. Map journey stages, actor actions, touchpoints, barriers, emotions only when evidenced, backstage dependencies and recovery. Create a content inventory and information hierarchy based on user tasks. Specify entry, success, alternative, error, cancellation and recovery paths with stable IDs. Check keyboard and assistive-technology needs alongside physical reach, privacy and shared-device concerns when relevant. Prioritize requirements using importance, uncertainty and consequence.

Output contract

Fill design work, selecting the sections relevant to this capability. Include: Research protocol, findings, journey map, content/IA outline, task-flow states, prioritized requirements and unresolved assumptions. Refer to stable IDs and paths rather than pasting full research or personas.

Acceptance

Verify the recorded audience selection, rationale, evidence limits and named use under the shared audience input rule. Reassess affected audience inputs on scope, evidence or intended-use changes; preserve historical results and hold dependent use until required conditions are resolved. Audience records alone never prove usability or production acceptance.

Every recommendation links to a need or declared hypothesis; consent/privacy boundaries exist; error and recovery states are included; real-user validation is accurately labeled. Apply quality boundaries. Unsupported checks remain pending with an owner and next action. For a revision, load stage handoff and compare only the authorized delta.

Writing continuation

Use content writing for UXD-22 wording and page content, while this capability owns task/state logic. Feed realistic copy back into wireframes and component specifications before final layout.

Focused craft methods

Read only the relevant method for the selected task; preserve existing prerequisites and canonical record ownership.

• Retail and physical display communication: use when retail context affects the requested output.

Website specialization

Version-Timestamp: 2026-09-11T20:48:53-04:00

Select relevant website methods for scoped website work. Reuse accepted foundation records and preserve this capability as their owner.

Historical evidence boundary

Keep superseded evidence and prior results in the project history, with version links from the handoff. The validated active evidence register accepts current sources only. Do not put historical sources into active support or relabel them current to pass validation. Preserve history outside that active register.

Applied decision method

Version-Timestamp: 2026-09-27 14:25:39 AST

Read UX and content decisions when connecting task evidence, state behavior and truthful messages. The card adds original worked reasoning; reuse this capability's existing prerequisites, records and acceptance checks. Load only the selected card. Its fictional example is teaching material, not tested project evidence.