Mobile app is end-user only — no admin, no CA portal, no marketing landing

Decision

The Chitragupt mobile app (Expo) ships only end-user surfaces: Auth, Onboarding, Verification, Dashboard, Inbox, Review, Tax, Expense, Portfolio, Family (end-user side), Hire-a-CA marketplace browse, Payment, Settings. It does NOT ship:

• Admin pillar — admin dashboards, refunds, disputes, grievances, payouts, users, support tickets, parser-failures, payment-reconciliation, CA-applications. All admin work is web-only.
• CA portal — CA-side client list, client drill-in, per-pillar drill-ins, preflight checklist, earnings, disputes, pricing, profile editor. CAs do their work on the web.
• Marketing landing — public landing pages, pricing, FAQ, terms, privacy, refund, grievance. A regular user reaching the app already signed up; they don't need the marketing funnel inside the app.

Why

• Admins and CAs are power-user personas who work on desktops with multiple windows, complex tables, and bulk operations. Mobile would be a worse experience and double the surface area to maintain.
• The marketing landing's job is to convert visitors who haven't installed the app yet — by definition, a user on the mobile app has already converted. The web marketing site stays the single source of public-facing pricing / FAQ / legal copy.
• Cuts mobile wireframe + implementation scope by ~30 surfaces (~25%).

Impact

• .context/designs/mobile/ will have no admin/, ca/, or marketing/ directories. (Currently empty for admin and ca; mobile marketing was never created.)
• .context/designs/mobile/hire-ca/ STAYS — that's the end-user-facing marketplace browse, not the marketing landing.
• .context/features/index.md V2 description updated to clarify mobile scope.
• Cross-platform consistency-sweep rules updated: when comparing a web admin/CA/marketing page, there is no mobile twin to diff against — intra-platform check only.
• Future audits should NOT flag missing mobile twins for admin/CA/marketing pages.

Status

Active.

Sources

• User decision 2026-06-27 wireframe consistency sweep.