Product domains
Currnt's product surface broke into six numbered domains (A–F), a Corporate meta-domain for client-branded enterprise portals, and a Mobile + Service API surface (G) that emits JSON instead of HTML. Together they cover ~80 user flows across a 2,278-line routes file.
Each page pairs a curated route table with the domain's headline flow and a list of features that went dormant before the freeze.
7 controllers A · Public web The marketing site, blog, public board catalog, signup, and login flows — the only Currnt surface most visitors ever saw. Sails views served from the same monolith as everything else. 33 controllers B · Treehouse — the internal back-office The 33-controller internal admin where every sales, ops, content, and account-management workflow at Currnt actually happened. Eight functional pillars, hundreds of pages, no public users. 9 controllers C · Boards engine The product. The thing customers actually paid for. The lifecycle of an advisory board from brief to deliverable: recruit experts, host the conversation, transcribe it, summarize it, ship it. 4 controllers D · Content production The blog editor, board-summary generator, marketing-asset pipeline, and AI co-facilitator hooks. Entirely internal to Treehouse — none of these surfaces are public. 5 controllers E · Members & accounts User accounts, profiles, segmentation, account merging, and lifecycle. The bookkeeping that holds the rest of the system together. 6 controllers F · Operations & ops Billing, invoicing, expert payouts, legal/NDA tracking, support tickets, and other internal bookkeeping. Where the platform meets accounting. 3 controllers Corp · Corporate portals Client-branded sub-experiences for enterprise customers running their own private advisory boards. A small surface that punched above its weight commercially. 3 controllers G · Mobile + Service APIs REST endpoints used by the iOS app and a thin layer of service-to-service integrations. The only Currnt surface that doesn't render HTML.