# Engineering Design

<!-- guide: How affected repositories implement approved specs and system
     obligations. Reference upstream ids; do not restate them. Remove guides. -->

## Inputs

<!-- guide: Exact upstream artifacts this design implements (specs, selected
     system-analysis modules, ux-design, security-analysis). -->

## Architecture Drivers

<!-- guide: Requirements, NFR ids, constraints and risks that force decisions. -->

## Technical Goals / Non-Goals

## Implementation Impact Map

| Area | Affected | Outcome or N/A reason |
| --- | --- | --- |
| main | | |
| frontend | | |
| backend | | |

## Decisions

<!-- guide: Per decision: context, chosen option, rejected alternatives, driver it
     satisfies. Group by repository when that helps. -->

## Components and Responsibilities

## Data / Storage Changes

## Contract Implementation

<!-- guide: How each contract is produced/consumed and how published OpenAPI is
     compared with the target contract. N/A when no contracts changed. -->

## Cross-cutting Implementation

## UI Implementation

<!-- guide: With ux-design.md: component composition, state, data fetching, how
     each UI state is produced — no restated UX. Without ux-design.md: state
     new/changed, reuse or N/A with reason, plus the needed screen/state detail. -->

## Developer Verification Strategy

## Migration / Rollout / Rollback

## Solution Assessment

<!-- guide: Required for new auth, security, storage, integration, observability,
     caching, concurrency or shared tooling; otherwise N/A with reason. -->

## Risks / Trade-offs

## ADR Candidates