# Product interface task

Read brand.md, tokens.json and icons.json. Build for the target platform using semantic tokens and native controls where possible. Start in light mode. Show explicit amounts and currencies with locale-aware formatting; preserve minor-unit precision. Keep states and next actions clear.

Include default, focus, disabled, loading, empty, error and completed states only where relevant. Payment confirmation must display recipient, amount, currency, fees and timing before submission. A submission acknowledgement is not settlement. Errors must not claim funds are safe or unmoved without authoritative data.

Use one Lucide family for UI icons. Label financial statuses in text. Keep accessible names, keyboard paths, reduced motion, large text and RTL layout in scope. Do not mirror the brand identity or reverse numeric strings when adapting RTL.

Deliver the smallest usable flow, referenced tokens and key-state fixtures. Identify whether each native example is a concept, source example or tested runtime implementation. Never report a device simulator or web mockup as a physical-device test.