# Signal

Signal is a compact subscription control center. Its cobalt summary band, square signal mark, segmented usage rails, and numbered service tickets create a technical identity without pretending the miniapp can observe VPN connectivity.

The subscription page is the entry point. The summary filters by active accounts or accounts needing attention. Active tickets emphasize remaining data and one-action link copying. Expired tickets explain the interruption and put renewal first. Missing or administrator-disabled accounts lead with support. Every subscription opens the shared full details and action flows.

The design uses near-black type, white surfaces, narrow borders, 8px corners, and a single cobalt accent. Status colors have explicit text alongside them. The usage rail encodes actual percentage used; its segments remain neutral until usage is available. The signal motif in the wordmark is purely decorative. There are no network quality or connectivity claims.

Persian is the default through the shared controller. Labels use the shared translation context; technical usernames retain their exact content in LTR text. Both host themes use explicit tokens. Mobile safe areas, visible focus, keyboard buttons, reduced motion, and nontruncated technical identities are supported.

This concept does not use the Refero skill, as requested for the three independently directed concepts. Its visual references are the supplied native miniapp screenshots and the visual language of service tickets, transport signage, and precise utility controls. It intentionally avoids a landing-page or simulated-device layout.

The concept owns presentation only. `../shared/app.js` mounts it, and the shared API owns subscriptions, usage, ledger history, purchases, renewals, account switching, errors, and persistence. There are no local fixtures, duplicated stores, or financial calculations in this folder.