# Engineering Design

## Context and Constraints

## Technical Goals / Non-Goals

## Implementation Impact Map

### main

### frontend

### backend

### qa
<!-- Use only after a real QA/E2E repository exists. -->

## Decisions

### main

### frontend

### backend

### qa

## Cross-cutting Implementation

## Data / Storage Changes

## Contract Implementation

## Developer Verification Strategy

## UI/UX Package

<!-- Choose new/changed, reuse or N/A with reason. For applicable UI include
     package revision, screens, states, interactions, responsive/a11y behavior.
     For reuse give immutable store ID + path from OpenSpec root, reused part
     and differences. Keep materials accessible after archive. Inline Markdown
     needs no self-hash; mutable external-only URLs are not an approved package. -->

**Applicability and scope:**

**Package revision:**

**Screens, states and interactions:**

**Responsive behavior:**

**Reused source and differences:**

<!-- If local PNG/SVG exports are needed, list each under visuals/ with a
     relative path, purpose and SHA-256. SVG must be self-contained (no scripts,
     handlers, external fonts/assets). Otherwise remove the table and state
     that the package is fully inline. One Design approval covers all materials. -->

| Material ID | Relative path | Screen/state and purpose | SHA-256 |
| --- | --- | --- | --- |
| <!-- id --> | <!-- visuals/file.png --> | <!-- purpose --> | <!-- digest --> |

## Risks / Trade-offs

## Migration / Rollout / Rollback

## Solution Assessment