CA namespace consolidation: portal → /ca/portal/*, user-facing → /ca/*

Decision

Consolidate all CA-touching routes under one /ca/* namespace: portal routes move to /ca/portal/*, user-facing browse/hire/consultation routes move to /ca/* (/ca, /ca/[caId], /ca/hire, /ca/ask/*).

Why

Three overlapping CA-touching surfaces (/hire-ca marketing browse, /get-a-ca authenticated checkout, /ask-ca/* consultation) created a confusing redirect chain (browse → sign-in → re-pick CA → checkout) and lacked a single namespace. CA portal routes occupied /ca/* and collided with any user-facing /ca/* consolidation. One namespace eliminates the architectural ambiguity.

Impact

• Portal moves: /ca/{earnings,pricing,profile,disputes,clients,kyc,match-requests,onboarding-pending,settings/pricing} → /ca/portal/*.
• Client viewing under CA moves: /clients/* → /ca/portal/clients/*.
• User-facing renames: /hire-ca → /ca (browse), /hire-ca/[caId] → /ca/[caId] (detail), /get-a-ca → /ca/hire (checkout), /ask-ca/* → /ca/ask/* (consultation history + detail + upgrade).
• Old routes deleted (no redirects — pre-launch).
• All internal link refs swept; .context/wiki/surfaces/* updated to reflect the new surface.
• Affects pillar-ca-portal, ca-category-consultation, ca-category-itr-filing, ca-category-notice-defence, marketplace-economics.

Status

Active.

Sources

• .context/wiki/decisions/* § "2026-05-31 — CA namespace consolidation: portal → /ca/portal/*, user-facing → /ca/*"