founder-schema 0.3.0 → 0.4.0

package/dist/domains/onboarding/onboarding.d.ts

@@ -0,0 +1,1018 @@
+/**
+ * founder-schema — Onboarding: steps, enums, and the two shapes of the answers
+ *
+ * ONE LIST DEFINES THE FLOW, AND IT IS DERIVED. Each step's fields are a pick
+ * of the finish body (`ONBOARDING_STEP_SCHEMAS`), and `FOUNDER_ONBOARDING_STEPS`
+ * is built FROM those picks: its `fields`, and even whether a step may be
+ * skipped, come from the schema rather than from a second hand-written list.
+ * GymMonk arrived at one list after keeping two in sync by hand, where a step
+ * could exist with no title or, worse, no validation gate at all; until 0.2.0
+ * this file still wrote the field lists twice.
+ *
+ * TWO SHAPES, ONE SET OF RULES. A half-filled form legitimately holds `null`
+ * for a choice nobody has made yet; the finalize body only ever sees completed
+ * answers. So the rules are written once and expressed over both shapes:
+ * `onboardingFormSchema` for work in progress and `completeOnboardingBodySchema`
+ * for the end. Letting those two drift is how a wizard says a step is optional
+ * and then answers 422 at Finish.
+ *
+ * NO COPY IN HERE. Step titles, help lines and topic category names are
+ * translation KEYS (`titleKey`, `helpKey`, `labelKey`), Jansathi's rule for
+ * every config string: an English sentence in a shared package is a sentence
+ * every other language has to match by wording.
+ *
+ * @module founder-schema/domains/onboarding
+ */
+import { z } from 'zod';
+/**
+ * 18, ruled by the user 2026-09-21. Under-18 would pull in parental-consent
+ * duties under the DPDP Act, which is a different and larger problem than a
+ * validation rule.
+ *
+ * ⚠️ The SERVER refuses at finalize. This schema exists so the member sees a
+ * useful message; it is not the gate.
+ */
+export declare const MIN_AGE_YEARS = 18;
+/** A sanity ceiling, not a product rule. Catches a mistyped year. */
+export declare const MAX_AGE_YEARS = 120;
+/**
+ * Whole years completed, by the calendar.
+ *
+ * ⚠️ NOT `elapsedMs / (365.25 * day)`, which is what the sibling product uses.
+ * That approximation reads 17.9986 at the start of somebody's eighteenth
+ * birthday and only crosses 18 about halfway through the day, so it refuses
+ * them for the half of their birthday they are most likely to be signing up on.
+ * Measured: it disagrees with the calendar on all 400 of the next 400 days.
+ * An age gate is exactly the place an approximation is not good enough.
+ */
+export declare function ageInYears(isoDate: string, now?: Date): number;
+/** A calendar date with no time component, `YYYY-MM-DD`. */
+export declare const isoDateSchema: z.ZodString;
+export type IsoDate = z.infer<typeof isoDateSchema>;
+/**
+ * Date of birth, with the age gate applied per parse.
+ *
+ * ⚠️ THE CLIENT IS NOT THE GATE. This schema exists so the member sees a useful
+ * message, and the server must refuse the same dates at finalize regardless.
+ * The sibling dating product validates the identical rule on its client and
+ * still shipped a defect where an under-age date of birth produced a live,
+ * discoverable profile, because the client was the only thing checking.
+ */
+export declare const dateOfBirthSchema: z.ZodString;
+export type DateOfBirth = z.infer<typeof dateOfBirthSchema>;
+export declare const BUSINESS_TYPE_VALUES: readonly ["startup", "sme", "enterprise"];
+export declare const businessTypeSchema: z.ZodEnum<{
+    startup: "startup";
+    sme: "sme";
+    enterprise: "enterprise";
+}>;
+export type BusinessType = z.infer<typeof businessTypeSchema>;
+/**
+ * ONE vocabulary, used TWICE: a member picks these as their `interests`, and a
+ * post carries them as its `topics`. That is what makes relevance an index
+ * lookup rather than a guess, and it is why this list is not called "interests"
+ * - naming it for one of its two jobs would have invited a second list for the
+ * other, which is the mistake this package has already made once with goals.
+ * (User's ruling via hary, 2026-09-21.)
+ *
+ * Deliberately DISTINCT from two neighbours that will otherwise collect the
+ * same words:
+ *
+ *   industry  what your company does
+ *   skills    what you can do
+ *   interests what you want to read about
+ *
+ * If the copy does not keep them apart, members fill all three identically and
+ * every one of them stops telling us anything.
+ *
+ * A closed list, consistent with industry, skill and stage, for the reason
+ * already written beside those: free text means two people typing "growth" and
+ * "Growth Marketing" never match, and matching is the entire point. The cost is
+ * that adding an interest needs a publish.
+ *
+ * Tuned down from the dating product's 246, which is mostly dating material.
+ * Values reuse its exact strings wherever one existed, so its Hindi
+ * translations can be lifted across.
+ *
+ * ⚠️ Stored per member. Append only; removing a value orphans data.
+ */
+export declare const TOPIC_VALUES: readonly ["mentoring", "leadership", "networking", "public_speaking", "teaching", "hiring_talent", "personal_branding", "career_transition", "remote_work", "ai_ml", "blockchain", "crypto_web3", "robotics", "data_science", "cybersecurity", "game_dev", "ux_design", "app_development", "open_source", "electronics", "space_exploration", "green_tech", "deeptech", "no_code", "entrepreneurship", "investing", "stock_trading", "personal_finance", "fundraising", "marketing", "sales", "consulting", "ecommerce", "retail", "real_estate", "supply_chain", "product_management", "growth", "b2b_saas", "d2c", "meditation", "journaling", "self_improvement", "productivity", "reading", "online_courses", "philosophy", "psychology", "therapy", "sleep_optimization", "gym", "yoga", "photography", "writing", "graphic_design", "filmmaking", "digital_art", "content_creation", "blogging", "vlogging", "podcasts", "animation", "music_production", "volunteering", "ngo_work", "environmental", "women_empowerment", "community_service", "social_enterprise", "education_access"];
+export declare const topicSchema: z.ZodEnum<{
+    ai_ml: "ai_ml";
+    b2b_saas: "b2b_saas";
+    d2c: "d2c";
+    deeptech: "deeptech";
+    robotics: "robotics";
+    growth: "growth";
+    sales: "sales";
+    marketing: "marketing";
+    supply_chain: "supply_chain";
+    fundraising: "fundraising";
+    mentoring: "mentoring";
+    leadership: "leadership";
+    networking: "networking";
+    public_speaking: "public_speaking";
+    teaching: "teaching";
+    hiring_talent: "hiring_talent";
+    personal_branding: "personal_branding";
+    career_transition: "career_transition";
+    remote_work: "remote_work";
+    blockchain: "blockchain";
+    crypto_web3: "crypto_web3";
+    data_science: "data_science";
+    cybersecurity: "cybersecurity";
+    game_dev: "game_dev";
+    ux_design: "ux_design";
+    app_development: "app_development";
+    open_source: "open_source";
+    electronics: "electronics";
+    space_exploration: "space_exploration";
+    green_tech: "green_tech";
+    no_code: "no_code";
+    entrepreneurship: "entrepreneurship";
+    investing: "investing";
+    stock_trading: "stock_trading";
+    personal_finance: "personal_finance";
+    consulting: "consulting";
+    ecommerce: "ecommerce";
+    retail: "retail";
+    real_estate: "real_estate";
+    product_management: "product_management";
+    meditation: "meditation";
+    journaling: "journaling";
+    self_improvement: "self_improvement";
+    productivity: "productivity";
+    reading: "reading";
+    online_courses: "online_courses";
+    philosophy: "philosophy";
+    psychology: "psychology";
+    therapy: "therapy";
+    sleep_optimization: "sleep_optimization";
+    gym: "gym";
+    yoga: "yoga";
+    photography: "photography";
+    writing: "writing";
+    graphic_design: "graphic_design";
+    filmmaking: "filmmaking";
+    digital_art: "digital_art";
+    content_creation: "content_creation";
+    blogging: "blogging";
+    vlogging: "vlogging";
+    podcasts: "podcasts";
+    animation: "animation";
+    music_production: "music_production";
+    volunteering: "volunteering";
+    ngo_work: "ngo_work";
+    environmental: "environmental";
+    women_empowerment: "women_empowerment";
+    community_service: "community_service";
+    social_enterprise: "social_enterprise";
+    education_access: "education_access";
+}>;
+export type Topic = z.infer<typeof topicSchema>;
+/**
+ * The grouping the picker renders.
+ *
+ * ⚠️ `TOPIC_VALUES` above is the single source of truth and this is typed
+ * against it, so a typo here is a compile error rather than a chip that renders
+ * and can never be selected. The dating product keeps a categorised list and a
+ * flat list side by side and they have already drifted apart by two values;
+ * a test in this package asserts these two agree exactly, in both directions.
+ */
+export declare const TOPIC_CATEGORY_KEYS: readonly ["career", "tech", "business", "growth", "creative", "impact"];
+export type TopicCategoryKey = (typeof TOPIC_CATEGORY_KEYS)[number];
+/**
+ * ⚠ TRANSLATION KEY SHAPE, for whoever builds the picker: `topics.category.<key>`
+ * for a category and `topics.value.<topic>` for a topic. The dating product's
+ * interests JSON is keyed by CATEGORY NAME instead, so all five of its label
+ * lookups miss and every chip renders its raw English in every locale, with a
+ * fully translated Hindi file sitting unreachable.
+ */
+export interface TopicCategory {
+    key: TopicCategoryKey;
+    /** A translation key. The English lives in the client's message files, not here. */
+    labelKey: `topics.category.${TopicCategoryKey}`;
+    values: readonly Topic[];
+}
+export declare const TOPIC_CATEGORIES: readonly TopicCategory[];
+/**
+ * How many a member must pick. A minimum exists because these drive feed
+ * relevance and zero of them means no relevance at all.
+ *
+ * ⚠️ If 3 turns out to be hard to reach against this list, that is a signal
+ * about the LIST, not about the minimum. The sibling product enforces no
+ * minimum at all, and its own field config says "pick up to 10" while every
+ * screen and schema enforces 20.
+ */
+export declare const INTERESTS_MIN = 3;
+export declare const INTERESTS_MAX = 10;
+/**
+ * The step keys, in order, as a literal union, so a consumer can key a table by
+ * step and have TypeScript insist on every one. Before 0.2.0 `key` was a plain
+ * string and the web client kept its own copy of this list to get the same
+ * check; a test there held the two together. Now there is one list.
+ */
+export declare const ONBOARDING_STEP_KEYS: readonly ["identity", "contact", "location", "goals", "interests", "business", "guidelines"];
+export type OnboardingStepKey = (typeof ONBOARDING_STEP_KEYS)[number];
+/**
+ * The community guidelines a member agrees to at the last step, by version.
+ *
+ * The finish body accepts THIS version and no other: an old tab still showing
+ * last month's text cannot record agreement to text it never displayed, and
+ * `'whatever'` is not a version. Until 0.2.0 any non-empty string passed, and
+ * the web client held this constant on its own.
+ *
+ * ⚠ Changing the guidelines text means bumping this, in the same publish.
+ * Every member who agreed to an earlier version keeps that version on their
+ * profile; that record is the point.
+ */
+export declare const GUIDELINES_VERSION: "2026-10-03";
+export declare const guidelinesVersionSchema: z.ZodLiteral<"2026-10-03">;
+/**
+ * The links the contact step collects, picked from the profile's own links so
+ * the two cannot disagree on what a link is. The phone is `phoneSchema`: ten
+ * digits, stored raw with no country code, on the account rather than here.
+ */
+export declare const contactLinksSchema: z.ZodObject<{
+    linkedin: z.ZodOptional<z.ZodURL>;
+    x: z.ZodOptional<z.ZodURL>;
+    instagram: z.ZodOptional<z.ZodURL>;
+}, z.core.$strip>;
+export type ContactLinks = z.infer<typeof contactLinksSchema>;
+/** A team size has at most this many digits: `TEAM_SIZE_MAX` written out. */
+export declare const TEAM_SIZE_DIGITS_MAX: number;
+/**
+ * The answers so far, keyed by the finish body's own field names: what each
+ * step SAVES (`PATCH /onboarding`, merged per field), what `GET` hands back
+ * to resume, and so the only keys a draft may hold
+ * (`ONBOARDING_DRAFT_KEYS`).
+ *
+ * RAW, on purpose: a draft is what the member TYPED, not what Finish will send.
+ * A half-typed link is ordinary text, a team size is digits as typed, and every
+ * choice is `null` until made ("not answered" is not "answered with nothing").
+ * Nothing here is required; whether a member may FINISH is
+ * `completeOnboardingBodySchema`'s decision, and the client builds that body
+ * from these answers.
+ *
+ * Screens may hold a different shape on top of this one (the web draws first
+ * and last name as two fields and joins them into `displayName`). Derive that
+ * type from `OnboardingForm` rather than writing it out, so a field added here
+ * reaches every screen.
+ *
+ * A stored draft is UNTRUSTED when it comes back: an older client, or another
+ * one, wrote it, and the server stores values opaquely. Read it with
+ * `readOnboardingDraft`, never by casting.
+ */
+export declare const onboardingFormSchema: z.ZodObject<{
+    displayName: z.ZodString;
+    gender: z.ZodNullable<z.ZodEnum<{
+        other: "other";
+        male: "male";
+        female: "female";
+        prefer_not_to_say: "prefer_not_to_say";
+    }>>;
+    dateOfBirth: z.ZodString;
+    headline: z.ZodString;
+    about: z.ZodString;
+    avatarUploadKey: z.ZodNullable<z.ZodString>;
+    skills: z.ZodArray<z.ZodEnum<{
+        engineering: "engineering";
+        product: "product";
+        design: "design";
+        data: "data";
+        growth: "growth";
+        sales: "sales";
+        marketing: "marketing";
+        operations: "operations";
+        finance: "finance";
+        legal: "legal";
+        hr_people: "hr_people";
+        supply_chain: "supply_chain";
+        research: "research";
+        fundraising: "fundraising";
+        community: "community";
+    }>>;
+    phone: z.ZodString;
+    links: z.ZodObject<{
+        linkedin: z.ZodString;
+        x: z.ZodString;
+        instagram: z.ZodString;
+    }, z.core.$strip>;
+    location: z.ZodNullable<z.ZodObject<{
+        city: z.ZodString;
+        state: z.ZodString;
+        country: z.ZodString;
+    }, z.core.$strip>>;
+    goals: z.ZodArray<z.ZodEnum<{
+        find_cofounder: "find_cofounder";
+        find_investors: "find_investors";
+        find_customers: "find_customers";
+        hiring: "hiring";
+        partnerships: "partnerships";
+        mentorship: "mentorship";
+        grow_network: "grow_network";
+        business_ideas: "business_ideas";
+        market_insights: "market_insights";
+        learn_startup: "learn_startup";
+        start_company: "start_company";
+    }>>;
+    interests: z.ZodArray<z.ZodEnum<{
+        ai_ml: "ai_ml";
+        b2b_saas: "b2b_saas";
+        d2c: "d2c";
+        deeptech: "deeptech";
+        robotics: "robotics";
+        growth: "growth";
+        sales: "sales";
+        marketing: "marketing";
+        supply_chain: "supply_chain";
+        fundraising: "fundraising";
+        mentoring: "mentoring";
+        leadership: "leadership";
+        networking: "networking";
+        public_speaking: "public_speaking";
+        teaching: "teaching";
+        hiring_talent: "hiring_talent";
+        personal_branding: "personal_branding";
+        career_transition: "career_transition";
+        remote_work: "remote_work";
+        blockchain: "blockchain";
+        crypto_web3: "crypto_web3";
+        data_science: "data_science";
+        cybersecurity: "cybersecurity";
+        game_dev: "game_dev";
+        ux_design: "ux_design";
+        app_development: "app_development";
+        open_source: "open_source";
+        electronics: "electronics";
+        space_exploration: "space_exploration";
+        green_tech: "green_tech";
+        no_code: "no_code";
+        entrepreneurship: "entrepreneurship";
+        investing: "investing";
+        stock_trading: "stock_trading";
+        personal_finance: "personal_finance";
+        consulting: "consulting";
+        ecommerce: "ecommerce";
+        retail: "retail";
+        real_estate: "real_estate";
+        product_management: "product_management";
+        meditation: "meditation";
+        journaling: "journaling";
+        self_improvement: "self_improvement";
+        productivity: "productivity";
+        reading: "reading";
+        online_courses: "online_courses";
+        philosophy: "philosophy";
+        psychology: "psychology";
+        therapy: "therapy";
+        sleep_optimization: "sleep_optimization";
+        gym: "gym";
+        yoga: "yoga";
+        photography: "photography";
+        writing: "writing";
+        graphic_design: "graphic_design";
+        filmmaking: "filmmaking";
+        digital_art: "digital_art";
+        content_creation: "content_creation";
+        blogging: "blogging";
+        vlogging: "vlogging";
+        podcasts: "podcasts";
+        animation: "animation";
+        music_production: "music_production";
+        volunteering: "volunteering";
+        ngo_work: "ngo_work";
+        environmental: "environmental";
+        women_empowerment: "women_empowerment";
+        community_service: "community_service";
+        social_enterprise: "social_enterprise";
+        education_access: "education_access";
+    }>>;
+    venture: z.ZodObject<{
+        name: z.ZodString;
+        website: z.ZodString;
+        industry: z.ZodNullable<z.ZodEnum<{
+            agritech: "agritech";
+            ai_ml: "ai_ml";
+            b2b_saas: "b2b_saas";
+            consumer: "consumer";
+            climate: "climate";
+            d2c: "d2c";
+            deeptech: "deeptech";
+            edtech: "edtech";
+            fintech: "fintech";
+            gaming: "gaming";
+            healthtech: "healthtech";
+            logistics: "logistics";
+            manufacturing: "manufacturing";
+            marketplace: "marketplace";
+            media: "media";
+            mobility: "mobility";
+            proptech: "proptech";
+            robotics: "robotics";
+            services: "services";
+            space: "space";
+            other: "other";
+        }>>;
+        stage: z.ZodNullable<z.ZodEnum<{
+            idea: "idea";
+            validation: "validation";
+            mvp: "mvp";
+            pre_seed: "pre_seed";
+            seed: "seed";
+            series_a_plus: "series_a_plus";
+            profitable: "profitable";
+            exited: "exited";
+        }>>;
+        teamSize: z.ZodString;
+    }, z.core.$strip>;
+    businessType: z.ZodNullable<z.ZodEnum<{
+        startup: "startup";
+        sme: "sme";
+        enterprise: "enterprise";
+    }>>;
+    guidelinesVersion: z.ZodNullable<z.ZodString>;
+}, z.core.$strip>;
+export type OnboardingForm = z.infer<typeof onboardingFormSchema>;
+/** The business step before anything is chosen. */
+export declare const EMPTY_ONBOARDING_VENTURE: OnboardingForm['venture'];
+/**
+ * A stored draft as an `OnboardingForm`, FIELD BY FIELD.
+ *
+ * Every field is checked against its own vocabulary and cut to its own limit;
+ * one that does not fit becomes "not answered" (`''`, `null`, `[]`) and the
+ * rest of the draft survives. Never coerced into a different answer: a value
+ * outside a vocabulary is dropped, not mapped to the nearest one. A photo key
+ * is never restored (see `avatarUploadKey`), and agreement only counts for the
+ * CURRENT guidelines.
+ *
+ * It fills in no answer the member did not give: a blank country stays blank.
+ * Whatever a screen shows by default is that screen's choice.
+ */
+export declare function readOnboardingDraft(draft: unknown): OnboardingForm;
+/**
+ * What the client sends to finish. Completed answers only.
+ *
+ * ⚠️ EVERY OPTIONAL FIELD HERE MUST BE ABSENT WHEN UNANSWERED, never a default
+ * standing in for one. The sibling gym product sent `bloodGroup ?? 'O+'`, so
+ * every member who skipped the question was recorded as O-positive: a real
+ * answer, indistinguishable from one somebody gave, sitting on a screen staff
+ * would read in an emergency. Absent has to stay absent.
+ *
+ * ⚠️ AND THIS IS NOT THE GATE EITHER. The server re-checks the age and refuses
+ * at finalize. `isOnboarded` may be set here and nowhere else: four of the
+ * profile's partial indexes are gated on it, so a half-built profile carrying
+ * it true appears in Discover half-built.
+ *
+ * Location, venture and links are the profile's own shapes, not copies: the
+ * copies are how the profile model came to lack Instagram.
+ */
+export declare const completeOnboardingBodySchema: z.ZodObject<{
+    displayName: z.ZodString;
+    gender: z.ZodEnum<{
+        other: "other";
+        male: "male";
+        female: "female";
+        prefer_not_to_say: "prefer_not_to_say";
+    }>;
+    dateOfBirth: z.ZodString;
+    headline: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+    about: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+    avatarUploadKey: z.ZodOptional<z.ZodString>;
+    phone: z.ZodString;
+    links: z.ZodOptional<z.ZodObject<{
+        linkedin: z.ZodOptional<z.ZodURL>;
+        x: z.ZodOptional<z.ZodURL>;
+        instagram: z.ZodOptional<z.ZodURL>;
+    }, z.core.$strip>>;
+    location: z.ZodOptional<z.ZodObject<{
+        city: z.ZodString;
+        state: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+        country: z.ZodString;
+    }, z.core.$strip>>;
+    goals: z.ZodArray<z.ZodEnum<{
+        find_cofounder: "find_cofounder";
+        find_investors: "find_investors";
+        find_customers: "find_customers";
+        hiring: "hiring";
+        partnerships: "partnerships";
+        mentorship: "mentorship";
+        grow_network: "grow_network";
+        business_ideas: "business_ideas";
+        market_insights: "market_insights";
+        learn_startup: "learn_startup";
+        start_company: "start_company";
+    }>>;
+    interests: z.ZodArray<z.ZodEnum<{
+        ai_ml: "ai_ml";
+        b2b_saas: "b2b_saas";
+        d2c: "d2c";
+        deeptech: "deeptech";
+        robotics: "robotics";
+        growth: "growth";
+        sales: "sales";
+        marketing: "marketing";
+        supply_chain: "supply_chain";
+        fundraising: "fundraising";
+        mentoring: "mentoring";
+        leadership: "leadership";
+        networking: "networking";
+        public_speaking: "public_speaking";
+        teaching: "teaching";
+        hiring_talent: "hiring_talent";
+        personal_branding: "personal_branding";
+        career_transition: "career_transition";
+        remote_work: "remote_work";
+        blockchain: "blockchain";
+        crypto_web3: "crypto_web3";
+        data_science: "data_science";
+        cybersecurity: "cybersecurity";
+        game_dev: "game_dev";
+        ux_design: "ux_design";
+        app_development: "app_development";
+        open_source: "open_source";
+        electronics: "electronics";
+        space_exploration: "space_exploration";
+        green_tech: "green_tech";
+        no_code: "no_code";
+        entrepreneurship: "entrepreneurship";
+        investing: "investing";
+        stock_trading: "stock_trading";
+        personal_finance: "personal_finance";
+        consulting: "consulting";
+        ecommerce: "ecommerce";
+        retail: "retail";
+        real_estate: "real_estate";
+        product_management: "product_management";
+        meditation: "meditation";
+        journaling: "journaling";
+        self_improvement: "self_improvement";
+        productivity: "productivity";
+        reading: "reading";
+        online_courses: "online_courses";
+        philosophy: "philosophy";
+        psychology: "psychology";
+        therapy: "therapy";
+        sleep_optimization: "sleep_optimization";
+        gym: "gym";
+        yoga: "yoga";
+        photography: "photography";
+        writing: "writing";
+        graphic_design: "graphic_design";
+        filmmaking: "filmmaking";
+        digital_art: "digital_art";
+        content_creation: "content_creation";
+        blogging: "blogging";
+        vlogging: "vlogging";
+        podcasts: "podcasts";
+        animation: "animation";
+        music_production: "music_production";
+        volunteering: "volunteering";
+        ngo_work: "ngo_work";
+        environmental: "environmental";
+        women_empowerment: "women_empowerment";
+        community_service: "community_service";
+        social_enterprise: "social_enterprise";
+        education_access: "education_access";
+    }>>;
+    skills: z.ZodOptional<z.ZodArray<z.ZodEnum<{
+        engineering: "engineering";
+        product: "product";
+        design: "design";
+        data: "data";
+        growth: "growth";
+        sales: "sales";
+        marketing: "marketing";
+        operations: "operations";
+        finance: "finance";
+        legal: "legal";
+        hr_people: "hr_people";
+        supply_chain: "supply_chain";
+        research: "research";
+        fundraising: "fundraising";
+        community: "community";
+    }>>>;
+    venture: z.ZodOptional<z.ZodObject<{
+        name: z.ZodString;
+        industry: z.ZodEnum<{
+            agritech: "agritech";
+            ai_ml: "ai_ml";
+            b2b_saas: "b2b_saas";
+            consumer: "consumer";
+            climate: "climate";
+            d2c: "d2c";
+            deeptech: "deeptech";
+            edtech: "edtech";
+            fintech: "fintech";
+            gaming: "gaming";
+            healthtech: "healthtech";
+            logistics: "logistics";
+            manufacturing: "manufacturing";
+            marketplace: "marketplace";
+            media: "media";
+            mobility: "mobility";
+            proptech: "proptech";
+            robotics: "robotics";
+            services: "services";
+            space: "space";
+            other: "other";
+        }>;
+        stage: z.ZodEnum<{
+            idea: "idea";
+            validation: "validation";
+            mvp: "mvp";
+            pre_seed: "pre_seed";
+            seed: "seed";
+            series_a_plus: "series_a_plus";
+            profitable: "profitable";
+            exited: "exited";
+        }>;
+        tagline: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+        website: z.ZodOptional<z.ZodURL>;
+        teamSize: z.ZodOptional<z.ZodNumber>;
+    }, z.core.$strip>>;
+    businessType: z.ZodOptional<z.ZodEnum<{
+        startup: "startup";
+        sme: "sme";
+        enterprise: "enterprise";
+    }>>;
+    guidelinesVersion: z.ZodLiteral<"2026-10-03">;
+}, z.core.$strip>;
+export type CompleteOnboardingBody = z.infer<typeof completeOnboardingBodySchema>;
+/** What a form may hand to the finish body before parsing. */
+export type CompleteOnboardingBodyInput = z.input<typeof completeOnboardingBodySchema>;
+/**
+ * Each step's slice of the finish body, picked FROM it, so a client validating
+ * "may I leave this step" and the server validating the finish apply the very
+ * same rules. A copy would drift, and the drift shows up as a wizard that lets
+ * a step pass and a finish that refuses it, on the last screen.
+ *
+ * THIS IS THE ONE PLACE A STEP'S FIELDS ARE WRITTEN. `FOUNDER_ONBOARDING_STEPS`
+ * below reads them from here. A test asserts that every finish field belongs to
+ * exactly one step.
+ *
+ * These validate the FINISH shape (skipped = absent), not the in-progress form:
+ * a client maps its form state to the slice first. The server does not run them
+ * on a draft save, because a half-answered step must be storable.
+ */
+export declare const ONBOARDING_STEP_SCHEMAS: {
+    readonly identity: z.ZodObject<{
+        about: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+        displayName: z.ZodString;
+        headline: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+        skills: z.ZodOptional<z.ZodArray<z.ZodEnum<{
+            engineering: "engineering";
+            product: "product";
+            design: "design";
+            data: "data";
+            growth: "growth";
+            sales: "sales";
+            marketing: "marketing";
+            operations: "operations";
+            finance: "finance";
+            legal: "legal";
+            hr_people: "hr_people";
+            supply_chain: "supply_chain";
+            research: "research";
+            fundraising: "fundraising";
+            community: "community";
+        }>>>;
+        gender: z.ZodEnum<{
+            other: "other";
+            male: "male";
+            female: "female";
+            prefer_not_to_say: "prefer_not_to_say";
+        }>;
+        dateOfBirth: z.ZodString;
+        avatarUploadKey: z.ZodOptional<z.ZodString>;
+    }, z.core.$strip>;
+    readonly contact: z.ZodObject<{
+        links: z.ZodOptional<z.ZodObject<{
+            linkedin: z.ZodOptional<z.ZodURL>;
+            x: z.ZodOptional<z.ZodURL>;
+            instagram: z.ZodOptional<z.ZodURL>;
+        }, z.core.$strip>>;
+        phone: z.ZodString;
+    }, z.core.$strip>;
+    readonly location: z.ZodObject<{
+        location: z.ZodOptional<z.ZodObject<{
+            city: z.ZodString;
+            state: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+            country: z.ZodString;
+        }, z.core.$strip>>;
+    }, z.core.$strip>;
+    readonly goals: z.ZodObject<{
+        goals: z.ZodArray<z.ZodEnum<{
+            find_cofounder: "find_cofounder";
+            find_investors: "find_investors";
+            find_customers: "find_customers";
+            hiring: "hiring";
+            partnerships: "partnerships";
+            mentorship: "mentorship";
+            grow_network: "grow_network";
+            business_ideas: "business_ideas";
+            market_insights: "market_insights";
+            learn_startup: "learn_startup";
+            start_company: "start_company";
+        }>>;
+    }, z.core.$strip>;
+    readonly interests: z.ZodObject<{
+        interests: z.ZodArray<z.ZodEnum<{
+            ai_ml: "ai_ml";
+            b2b_saas: "b2b_saas";
+            d2c: "d2c";
+            deeptech: "deeptech";
+            robotics: "robotics";
+            growth: "growth";
+            sales: "sales";
+            marketing: "marketing";
+            supply_chain: "supply_chain";
+            fundraising: "fundraising";
+            mentoring: "mentoring";
+            leadership: "leadership";
+            networking: "networking";
+            public_speaking: "public_speaking";
+            teaching: "teaching";
+            hiring_talent: "hiring_talent";
+            personal_branding: "personal_branding";
+            career_transition: "career_transition";
+            remote_work: "remote_work";
+            blockchain: "blockchain";
+            crypto_web3: "crypto_web3";
+            data_science: "data_science";
+            cybersecurity: "cybersecurity";
+            game_dev: "game_dev";
+            ux_design: "ux_design";
+            app_development: "app_development";
+            open_source: "open_source";
+            electronics: "electronics";
+            space_exploration: "space_exploration";
+            green_tech: "green_tech";
+            no_code: "no_code";
+            entrepreneurship: "entrepreneurship";
+            investing: "investing";
+            stock_trading: "stock_trading";
+            personal_finance: "personal_finance";
+            consulting: "consulting";
+            ecommerce: "ecommerce";
+            retail: "retail";
+            real_estate: "real_estate";
+            product_management: "product_management";
+            meditation: "meditation";
+            journaling: "journaling";
+            self_improvement: "self_improvement";
+            productivity: "productivity";
+            reading: "reading";
+            online_courses: "online_courses";
+            philosophy: "philosophy";
+            psychology: "psychology";
+            therapy: "therapy";
+            sleep_optimization: "sleep_optimization";
+            gym: "gym";
+            yoga: "yoga";
+            photography: "photography";
+            writing: "writing";
+            graphic_design: "graphic_design";
+            filmmaking: "filmmaking";
+            digital_art: "digital_art";
+            content_creation: "content_creation";
+            blogging: "blogging";
+            vlogging: "vlogging";
+            podcasts: "podcasts";
+            animation: "animation";
+            music_production: "music_production";
+            volunteering: "volunteering";
+            ngo_work: "ngo_work";
+            environmental: "environmental";
+            women_empowerment: "women_empowerment";
+            community_service: "community_service";
+            social_enterprise: "social_enterprise";
+            education_access: "education_access";
+        }>>;
+    }, z.core.$strip>;
+    readonly business: z.ZodObject<{
+        venture: z.ZodOptional<z.ZodObject<{
+            name: z.ZodString;
+            industry: z.ZodEnum<{
+                agritech: "agritech";
+                ai_ml: "ai_ml";
+                b2b_saas: "b2b_saas";
+                consumer: "consumer";
+                climate: "climate";
+                d2c: "d2c";
+                deeptech: "deeptech";
+                edtech: "edtech";
+                fintech: "fintech";
+                gaming: "gaming";
+                healthtech: "healthtech";
+                logistics: "logistics";
+                manufacturing: "manufacturing";
+                marketplace: "marketplace";
+                media: "media";
+                mobility: "mobility";
+                proptech: "proptech";
+                robotics: "robotics";
+                services: "services";
+                space: "space";
+                other: "other";
+            }>;
+            stage: z.ZodEnum<{
+                idea: "idea";
+                validation: "validation";
+                mvp: "mvp";
+                pre_seed: "pre_seed";
+                seed: "seed";
+                series_a_plus: "series_a_plus";
+                profitable: "profitable";
+                exited: "exited";
+            }>;
+            tagline: z.ZodPreprocess<z.ZodOptional<z.ZodString>, unknown>;
+            website: z.ZodOptional<z.ZodURL>;
+            teamSize: z.ZodOptional<z.ZodNumber>;
+        }, z.core.$strip>>;
+        businessType: z.ZodOptional<z.ZodEnum<{
+            startup: "startup";
+            sme: "sme";
+            enterprise: "enterprise";
+        }>>;
+    }, z.core.$strip>;
+    readonly guidelines: z.ZodObject<{
+        guidelinesVersion: z.ZodLiteral<"2026-10-03">;
+    }, z.core.$strip>;
+};
+/** One step's slice, parsed: `OnboardingStepBody<'contact'>` is `{ phone, links? }`. */
+export type OnboardingStepBody<K extends OnboardingStepKey> = z.infer<(typeof ONBOARDING_STEP_SCHEMAS)[K]>;
+/** A finish-body field name. */
+export type OnboardingField = keyof CompleteOnboardingBody;
+/**
+ * One step of the wizard, as a client renders it.
+ *
+ * `fields` is what gates leaving this step: a field that appears in no step is
+ * unreachable twice over, because Continue will not surface its error and the
+ * final submit's jump-to-the-bad-step finds no step to jump to and leaves the
+ * last screen dead.
+ */
+export interface OnboardingStepConfig {
+    /** Stable identifier. Safe for analytics and for a resume cursor, unlike an index. */
+    key: OnboardingStepKey;
+    /** Translation keys. The words live in the client's message files. */
+    titleKey: `onboarding.steps.${OnboardingStepKey}.title`;
+    helpKey: `onboarding.steps.${OnboardingStepKey}.help`;
+    /** The step's slice of the finish body, in schema order. */
+    fields: readonly OnboardingField[];
+    /**
+     * False when the whole step may be passed without answering anything.
+     * DERIVED: a step is optional exactly when its slice accepts an empty
+     * object, so "skippable" can never disagree with what the finish accepts.
+     */
+    required: boolean;
+}
+export declare const FOUNDER_ONBOARDING_STEPS: readonly OnboardingStepConfig[];
+export declare const ONBOARDING_TOTAL_STEPS: number;
+/** Fields gating each step, in step order. Read from the same picks. */
+export declare const ONBOARDING_STEP_FIELDS: readonly (readonly OnboardingField[])[];
+/** What finishing answers: the new profile's id and the handle derived for it. */
+export declare const completeOnboardingResponseSchema: z.ZodObject<{
+    id: z.ZodString;
+    username: z.ZodString;
+}, z.core.$strip>;
+export type CompleteOnboardingResponse = z.infer<typeof completeOnboardingResponseSchema>;
+/**
+ * The keys a draft may hold: exactly the in-progress form's fields.
+ *
+ * ⚠ The server writes each key as a dot path (`draft.<key>`). Unchecked, a key
+ * holding a dot writes somewhere nested the form never asked for, and the
+ * collection fills with whatever a client invents. Until 0.2.0 the backend
+ * kept its own copy of this list and DROPPED unknown keys without a word; now a
+ * draft carrying one is refused, with the key in the issue's path.
+ */
+export declare const onboardingDraftKeySchema: z.ZodEnum<{
+    location: "location";
+    about: "about";
+    displayName: "displayName";
+    headline: "headline";
+    venture: "venture";
+    skills: "skills";
+    goals: "goals";
+    links: "links";
+    interests: "interests";
+    gender: "gender";
+    dateOfBirth: "dateOfBirth";
+    avatarUploadKey: "avatarUploadKey";
+    phone: "phone";
+    businessType: "businessType";
+    guidelinesVersion: "guidelinesVersion";
+}>;
+export declare const ONBOARDING_DRAFT_KEYS: ("location" | "about" | "displayName" | "headline" | "venture" | "skills" | "goals" | "links" | "interests" | "gender" | "dateOfBirth" | "avatarUploadKey" | "phone" | "businessType" | "guidelinesVersion")[];
+export type OnboardingDraftKey = z.infer<typeof onboardingDraftKeySchema>;
+/**
+ * Where the member got to, kept in its own collection, separate from the
+ * profile.
+ *
+ * `step` is a flat index into `FOUNDER_ONBOARDING_STEPS`, not a `(step, sub)`
+ * pair: one number is what lets a member start on the web and resume elsewhere,
+ * provided both ends agree on the encoding.
+ *
+ * The draft's KEYS come from the form; its VALUES are opaque on purpose. A
+ * half-answered step must be storable even though it would fail the finish,
+ * and everything in it is re-validated strictly at finalize.
+ *
+ * `partialRecord`, not `record`: in Zod 4 an enum-keyed `z.record` demands
+ * every key, and a draft holds whichever steps the member has reached.
+ */
+export declare const onboardingDraftSchema: z.ZodRecord<z.ZodEnum<{
+    location: "location";
+    about: "about";
+    displayName: "displayName";
+    headline: "headline";
+    venture: "venture";
+    skills: "skills";
+    goals: "goals";
+    links: "links";
+    interests: "interests";
+    gender: "gender";
+    dateOfBirth: "dateOfBirth";
+    avatarUploadKey: "avatarUploadKey";
+    phone: "phone";
+    businessType: "businessType";
+    guidelinesVersion: "guidelinesVersion";
+}> & z.core.$partial, z.ZodUnknown>;
+export type OnboardingDraft = z.infer<typeof onboardingDraftSchema>;
+export declare const onboardingProgressSchema: z.ZodObject<{
+    step: z.ZodNumber;
+    draft: z.ZodOptional<z.ZodRecord<z.ZodEnum<{
+        location: "location";
+        about: "about";
+        displayName: "displayName";
+        headline: "headline";
+        venture: "venture";
+        skills: "skills";
+        goals: "goals";
+        links: "links";
+        interests: "interests";
+        gender: "gender";
+        dateOfBirth: "dateOfBirth";
+        avatarUploadKey: "avatarUploadKey";
+        phone: "phone";
+        businessType: "businessType";
+        guidelinesVersion: "guidelinesVersion";
+    }> & z.core.$partial, z.ZodUnknown>>;
+}, z.core.$strip>;
+export type OnboardingProgress = z.infer<typeof onboardingProgressSchema>;
+/**
+ * `PATCH` body: any subset of the cursor, merged server-side. No defaults.
+ * `step` may equal `ONBOARDING_TOTAL_STEPS`: "past the last step", which the
+ * client sends on its way to finish.
+ */
+export declare const onboardingProgressUpdateSchema: z.ZodObject<{
+    step: z.ZodOptional<z.ZodNumber>;
+    draft: z.ZodOptional<z.ZodRecord<z.ZodEnum<{
+        location: "location";
+        about: "about";
+        displayName: "displayName";
+        headline: "headline";
+        venture: "venture";
+        skills: "skills";
+        goals: "goals";
+        links: "links";
+        interests: "interests";
+        gender: "gender";
+        dateOfBirth: "dateOfBirth";
+        avatarUploadKey: "avatarUploadKey";
+        phone: "phone";
+        businessType: "businessType";
+        guidelinesVersion: "guidelinesVersion";
+    }> & z.core.$partial, z.ZodUnknown>>;
+}, z.core.$strip>;
+export type OnboardingProgressUpdate = z.infer<typeof onboardingProgressUpdateSchema>;
+/**
+ * What the client reads on return, from `GET` and from every `PATCH`.
+ *
+ * ⚠️ `onboarded` is the gate and it comes from the profile, not from the
+ * cursor: a finished member on a new device must be recognised even when the
+ * cursor row is gone, and a cursor that failed to load must never make an
+ * unfinished member look finished.
+ */
+export declare const onboardingStatusSchema: z.ZodObject<{
+    onboarded: z.ZodBoolean;
+    step: z.ZodNumber;
+    draft: z.ZodOptional<z.ZodRecord<z.ZodEnum<{
+        location: "location";
+        about: "about";
+        displayName: "displayName";
+        headline: "headline";
+        venture: "venture";
+        skills: "skills";
+        goals: "goals";
+        links: "links";
+        interests: "interests";
+        gender: "gender";
+        dateOfBirth: "dateOfBirth";
+        avatarUploadKey: "avatarUploadKey";
+        phone: "phone";
+        businessType: "businessType";
+        guidelinesVersion: "guidelinesVersion";
+    }> & z.core.$partial, z.ZodUnknown>>;
+}, z.core.$strip>;
+export type OnboardingStatus = z.infer<typeof onboardingStatusSchema>;
+//# sourceMappingURL=onboarding.d.ts.map