create-ailk 0.1.0 → 0.2.0

package/templates/database/flows/presets.ts

@@ -0,0 +1,315 @@
+/**
+ * @file presets.ts
+ * @description The three static capture presets — form, waitlist,
+ * lead-magnet — as flow-config DATA (#3958 §3.1), plus the `roadmap` preset
+ * (#3963 D2) — the acquisition-shape segmentation → thank-you → deliverable
+ * funnel that is the Release's terminal integration unit. Each is a linear
+ * flow the merged engine (#3956) serves unmodified: no preset-specific
+ * branch exists anywhere in `flow-engine.ts`, and none may be added here
+ * either.
+ *
+ * Every preset collects contact fields BEFORE any segmentation and sets
+ * `mapsTo: "email"` on its email field, so the engine denormalizes onto
+ * `FlowSession.email` — the indexed column #3962's abandon-email query
+ * reads. All copy is a `LocalizedString` carrying the flow's `defaultLocale`
+ * ("en") key, never a bare string (AC3) — `flowConfigSchema` rejects a bare
+ * string by construction, verified by
+ * `database/__tests__/flows-presets.test.ts`.
+ *
+ * This module is data only, no logic, and imports only the `FlowConfig` type
+ * from `@working-theory/validation` — it introduces no dependency from
+ * `database/` toward `apps/*` (architecture.yaml's import boundary).
+ *
+ * `database/flows/` is a plain directory, not a declared `database/`
+ * namespace (architecture.yaml's `namespaces.members` lists only auth,
+ * config, inbox, content, ops) — it holds no Prisma models and no
+ * cross-namespace relation, so the namespace-isolation rules don't apply to
+ * it.
+ */
+
+import type { FlowConfig } from "@working-theory/validation";
+
+const en = (s: string) => ({ en: s });
+
+/**
+ * Form preset — a general-purpose contact form. Two steps: collect name,
+ * email, and an optional message; confirm.
+ */
+const formPreset: FlowConfig = {
+  slug: "form",
+  defaultLocale: "en",
+  steps: [
+    {
+      key: "contact",
+      type: "field",
+      copy: { title: en("Get in touch") },
+      fields: [
+        {
+          name: "name",
+          inputType: "text",
+          copy: { label: en("Name") },
+        },
+        {
+          name: "email",
+          inputType: "email",
+          required: true,
+          mapsTo: "email",
+          copy: { label: en("Email") },
+        },
+        {
+          name: "message",
+          inputType: "textarea",
+          copy: {
+            label: en("Message"),
+            help: en("Tell us a bit about what you need."),
+          },
+        },
+      ],
+    },
+    {
+      key: "done",
+      type: "message",
+      copy: {
+        title: en("Thanks — we'll be in touch"),
+        body: en("We've received your message and will reply shortly."),
+      },
+    },
+  ],
+};
+
+/**
+ * Waitlist preset — a minimal signup: email only, plus an optional name.
+ */
+const waitlistPreset: FlowConfig = {
+  slug: "waitlist",
+  defaultLocale: "en",
+  steps: [
+    {
+      key: "contact",
+      type: "field",
+      copy: { title: en("Join the waitlist") },
+      fields: [
+        {
+          name: "email",
+          inputType: "email",
+          required: true,
+          mapsTo: "email",
+          copy: { label: en("Email") },
+        },
+        {
+          name: "name",
+          inputType: "text",
+          copy: { label: en("Name (optional)") },
+        },
+      ],
+    },
+    {
+      key: "done",
+      type: "message",
+      copy: {
+        title: en("You're on the list"),
+        body: en("We'll email you as soon as a spot opens up."),
+      },
+    },
+  ],
+};
+
+/**
+ * Lead-magnet preset — collect contact info, then ask one qualifying
+ * question before delivering the message step. The qualifier declares no
+ * `segments` band map (spec §7 item 4 — resolved: a downstream seam #3959
+ * owns opt-in, and these presets stay valid unchanged under it), so the
+ * "segment" reserved-name check never applies here.
+ */
+const leadMagnetPreset: FlowConfig = {
+  slug: "lead-magnet",
+  defaultLocale: "en",
+  steps: [
+    {
+      key: "contact",
+      type: "field",
+      copy: { title: en("Get the guide") },
+      fields: [
+        {
+          name: "email",
+          inputType: "email",
+          required: true,
+          mapsTo: "email",
+          copy: { label: en("Email") },
+        },
+        {
+          name: "name",
+          inputType: "text",
+          copy: { label: en("Name (optional)") },
+        },
+      ],
+    },
+    {
+      key: "qualifier",
+      type: "segmentation",
+      copy: { title: en("What best describes your role?") },
+      questions: [
+        {
+          name: "role",
+          options: [
+            { value: "founder", label: en("Founder / Owner") },
+            { value: "marketer", label: en("Marketer") },
+            { value: "other", label: en("Something else") },
+          ],
+        },
+      ],
+    },
+    {
+      key: "done",
+      type: "message",
+      copy: {
+        title: en("Check your inbox"),
+        body: en("Your guide is on its way — thanks for the interest."),
+      },
+    },
+  ],
+};
+
+/**
+ * Roadmap preset — the acquisition-shape funnel (#3963 D2), the Release's
+ * terminal integration unit. Linear, three collection steps (name, email,
+ * segmentation — no phone/address; the acquisition-capture research's §5
+ * over-collection is deliberately NOT reproduced), a two-band `segments` map
+ * derived from a single marketing-spend question, `thankYou` routing each
+ * band to a distinct TY page, `deliverables` mapping each band to a distinct
+ * asset, and `abandonEmail` authored but shipped dark (`mode: "dark"`,
+ * #3962). Copy grounded in the positionary strategy chain (POSITIONING.md
+ * §1a's two audiences — Spend-defenders vs Story-shippers — and MESSAGING.md
+ * Beat 1's marketing-spend insight); the two bands map company marketing
+ * spend onto "early" (pre-systematic spend) vs "scaling" (real, measured
+ * spend) rather than reproducing the acquisition-capture's employee/revenue
+ * vocabulary verbatim.
+ */
+const roadmapPreset: FlowConfig = {
+  slug: "roadmap",
+  defaultLocale: "en",
+  steps: [
+    {
+      key: "name",
+      type: "field",
+      copy: { title: en("Let's start with your name") },
+      fields: [
+        {
+          name: "name",
+          inputType: "text",
+          required: true,
+          copy: { label: en("Name") },
+        },
+      ],
+    },
+    {
+      key: "email",
+      type: "field",
+      copy: { title: en("Where should we send your roadmap?") },
+      fields: [
+        {
+          name: "email",
+          inputType: "email",
+          required: true,
+          mapsTo: "email",
+          copy: { label: en("Work email") },
+        },
+      ],
+    },
+    {
+      key: "stage",
+      type: "segmentation",
+      copy: { title: en("Where does your marketing spend stand today?") },
+      questions: [
+        {
+          name: "spend",
+          options: [
+            {
+              value: "not_yet_systematic",
+              label: en("Not yet systematic — we're still finding our story"),
+            },
+            {
+              value: "under_50k",
+              label: en("Under $50K/year"),
+            },
+            {
+              value: "50k_250k",
+              label: en("$50K–$250K/year"),
+            },
+            {
+              value: "250k_1m",
+              label: en("$250K–$1M/year"),
+            },
+            {
+              value: "1m_plus",
+              label: en("$1M+/year"),
+            },
+          ],
+        },
+      ],
+      segments: {
+        question: "spend",
+        bands: [
+          { key: "early", values: ["not_yet_systematic", "under_50k"] },
+          { key: "scaling", values: ["50k_250k", "250k_1m", "1m_plus"] },
+        ],
+      },
+    },
+    {
+      key: "done",
+      type: "message",
+      copy: {
+        title: en("Check your inbox"),
+        body: en("Your positioning roadmap is on its way."),
+      },
+    },
+  ],
+  thankYou: {
+    default: "roadmap-thanks",
+    bySegment: {
+      early: "roadmap-thanks",
+      scaling: "roadmap-thanks-qualified",
+    },
+  },
+  deliverables: {
+    assets: [
+      { segment: "early", assetKey: "roadmap-early" },
+      { segment: "scaling", assetKey: "roadmap-scaling" },
+    ],
+    copy: {
+      subject: en("Your positioning roadmap is ready"),
+      body: en(
+        "Thanks for the detail — attached is your roadmap for getting your positioning authored, published, and proven against real demand.",
+      ),
+      cta: en("Download your roadmap"),
+    },
+  },
+  abandonEmail: {
+    // Authored, shipped dark (#3962 D2) — selection + audit only, no send.
+    // Flipping to "enabled" is a one-line config change the operator may
+    // make post-launch (spec §Clarifications).
+    mode: "dark",
+    delayMinutes: 60,
+    copy: {
+      subject: en("Still want your positioning roadmap?"),
+      body: en(
+        "You started building your roadmap but didn't finish — pick up where you left off and we'll send it your way.",
+      ),
+      cta: en("Finish your roadmap"),
+    },
+  },
+};
+
+/**
+ * The four static capture presets, in scaffold/seed order. Consumed by
+ * `apps/api/src/bin/seed-presets.ts` via
+ * `seedFlowPresets` (`apps/api/src/services/flow-engine.ts`), which writes
+ * each through the existing validated `upsertFlowDefinition` path — no
+ * second write path is introduced.
+ */
+export const FLOW_PRESETS: FlowConfig[] = [
+  formPreset,
+  waitlistPreset,
+  leadMagnetPreset,
+  roadmapPreset,
+];

package/templates/database/inbox/__tests__/schema.test.ts

@@ -26,6 +26,10 @@ describe("inbox namespace — Prisma client model presence", () => {
   it("emits Callback model file", () => {
     expect(existsSync(resolve(MODELS_DIR, "Callback.ts"))).toBe(true);
   });
+
+  it("emits ProjectListing model file (#4998)", () => {
+    expect(existsSync(resolve(MODELS_DIR, "ProjectListing.ts"))).toBe(true);
+  });
 });
 
 describe("inbox namespace — architecture lint", () => {