@contractspec/example.product-intent 3.7.7 → 3.7.10

package/.turbo/turbo-build.log

@@ -2,30 +2,32 @@ $ contractspec-bun-build prebuild
 $ bun run prebuild && bun run build:bundle && bun run build:types
 $ contractspec-bun-build prebuild
 $ contractspec-bun-build transpile
-[contractspec-bun-build] transpile target=bun root=src entries=9 noBundle=false
-Bundled 9 modules in 33ms
+[contractspec-bun-build] transpile target=bun root=src entries=10 noBundle=false
+Bundled 10 modules in 46ms
 
   docs/index.js                     1.41 KB   (entry point)
+  ./script.js                       16.50 KB  (entry point)
   ./sync-actions.js                 15.97 KB  (entry point)
   docs/product-intent.docblock.js   1.41 KB   (entry point)
-  ./index.js                        11.44 KB  (entry point)
+  ./index.js                        14.46 KB  (entry point)
   ./example.js                      0.95 KB   (entry point)
-  ./product-intent.feature.js       0.60 KB   (entry point)
-  ./script.js                       16.50 KB  (entry point)
   ./load-evidence.js                9.86 KB   (entry point)
   ./posthog-signals.js              7.59 KB   (entry point)
+  ./product-intent.discovery.js     3.0 KB    (entry point)
+  ./product-intent.feature.js       0.60 KB   (entry point)
 
-[contractspec-bun-build] transpile target=node root=src entries=9 noBundle=false
-Bundled 9 modules in 27ms
+[contractspec-bun-build] transpile target=node root=src entries=10 noBundle=false
+Bundled 10 modules in 46ms
 
   docs/index.js                     1.40 KB   (entry point)
+  ./script.js                       16.51 KB  (entry point)
   ./sync-actions.js                 15.97 KB  (entry point)
   docs/product-intent.docblock.js   1.40 KB   (entry point)
-  ./index.js                        11.44 KB  (entry point)
+  ./index.js                        14.46 KB  (entry point)
   ./example.js                      0.94 KB   (entry point)
-  ./product-intent.feature.js       0.59 KB   (entry point)
-  ./script.js                       16.51 KB  (entry point)
   ./load-evidence.js                9.86 KB   (entry point)
   ./posthog-signals.js              7.58 KB   (entry point)
+  ./product-intent.discovery.js     3.0 KB    (entry point)
+  ./product-intent.feature.js       0.59 KB   (entry point)
 
 $ contractspec-bun-build types

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # @contractspec/example.product-intent
 
+## 3.7.10
+
+### Patch Changes
+
+- 1a44cb6: feat: improve examples to increase coverage of Contracts type
+- Updated dependencies [1a44cb6]
+  - @contractspec/integration.providers-impls@3.8.2
+  - @contractspec/lib.contracts-integrations@3.8.2
+  - @contractspec/lib.product-intent-utils@3.7.10
+  - @contractspec/lib.contracts-spec@4.1.2
+  - @contractspec/lib.analytics@3.7.10
+  - @contractspec/lib.ai-agent@7.0.10
+
+## 3.7.9
+
+### Patch Changes
+
+- fix: release
+- Updated dependencies
+  - @contractspec/integration.providers-impls@3.8.1
+  - @contractspec/lib.contracts-integrations@3.8.1
+  - @contractspec/lib.product-intent-utils@3.7.9
+  - @contractspec/lib.contracts-spec@4.1.1
+  - @contractspec/lib.analytics@3.7.9
+  - @contractspec/lib.ai-agent@7.0.9
+
 ## 3.7.6
 
 ### Patch Changes

package/README.md

@@ -6,12 +6,12 @@ Website: https://contractspec.io
 
 ## What This Demonstrates
 
+- Canonical `product-intent` export via `ProductIntentDiscoverySpec`.
 - Evidence loading and ingestion pipeline.
 - PostHog signal extraction for product analytics.
 - Action synchronization across tools.
 - Script-based execution pattern.
 - `src/docs/` contains docblocks and documentation-facing exports.
-- `src/docs/` contains docblocks and documentation-facing exports.
 
 ## Running Locally
 
@@ -33,6 +33,7 @@ Use `@contractspec/example.product-intent` as a reference implementation, or imp
 - `src/load-evidence.test.ts` is part of the package's public or composition surface.
 - `src/load-evidence.ts` is part of the package's public or composition surface.
 - `src/posthog-signals.ts` is part of the package's public or composition surface.
+- `src/product-intent.discovery.ts` defines the exported product-intent spec.
 - `src/product-intent.feature.ts` defines a feature entrypoint.
 
 ## Public Entry Points
@@ -43,9 +44,11 @@ Use `@contractspec/example.product-intent` as a reference implementation, or imp
 - Export `./example` resolves through `./src/example.ts`.
 - Export `./load-evidence` resolves through `./src/load-evidence.ts`.
 - Export `./posthog-signals` resolves through `./src/posthog-signals.ts`.
+- Export `./product-intent.discovery` resolves through `./src/product-intent.discovery.ts`.
 - Export `./product-intent.feature` resolves through `./src/product-intent.feature.ts`.
 - Export `./script` resolves through `./src/script.ts`.
 - Export `./sync-actions` resolves through `./src/sync-actions.ts`.
+- The package publishes 9 total export subpaths; keep docs aligned with `package.json`.
 
 ## Local Commands
 

package/dist/contracts.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/index.d.ts

@@ -3,4 +3,5 @@ export type { EvidenceLoadOptions, EvidenceLoadWithSignalsOptions, } from './loa
 export { DEFAULT_CHUNK_SIZE, DEFAULT_EVIDENCE_ROOT, DEFAULT_TRANSCRIPT_DIRS, loadEvidenceChunks, loadEvidenceChunksWithSignals, } from './load-evidence';
 export type { PosthogEvidenceOptions } from './posthog-signals';
 export { loadPosthogEvidenceChunks, resolvePosthogEvidenceOptionsFromEnv, } from './posthog-signals';
+export * from './product-intent.discovery';
 export * from './product-intent.feature';

package/dist/index.js

@@ -337,6 +337,79 @@ async function loadEvidenceChunksWithSignals(options = {}) {
   return [...baseChunks, ...posthogChunks];
 }
 
+// src/product-intent.discovery.ts
+import {
+  OwnersEnum,
+  StabilityEnum
+} from "@contractspec/lib.contracts-spec/ownership";
+import { defineProductIntentSpec } from "@contractspec/lib.contracts-spec/product-intent/spec";
+var ProductIntentDiscoverySpec = defineProductIntentSpec({
+  id: "product-intent.discovery.activation",
+  meta: {
+    key: "product-intent.discovery.activation",
+    version: "1.0.0",
+    title: "Product Intent Discovery",
+    description: "Discovery contract for activation friction using transcripts, analytics signals, and generated tasks.",
+    domain: "product",
+    owners: [OwnersEnum.PlatformCore],
+    tags: ["product-intent", "discovery", "activation", "analytics"],
+    stability: StabilityEnum.Experimental,
+    goal: "Prioritize the next activation improvement with grounded evidence.",
+    context: "Evidence is collected from interview transcripts, support tickets, and PostHog funnels before turning into task-ready outputs."
+  },
+  question: "Which activation and onboarding friction should we prioritize next?",
+  runtimeContext: {
+    evidenceRoot: "packages/examples/product-intent/evidence",
+    analyticsProvider: "posthog"
+  },
+  tickets: {
+    tickets: [
+      {
+        ticketId: "PI-101",
+        title: "Add a guided onboarding checklist",
+        summary: "Give new users an explicit checklist after signup so they can see the next activation milestone.",
+        evidenceIds: ["INT-002", "INT-014", "PH-dropoff-checkout"],
+        acceptanceCriteria: [
+          "Users see a checklist within the first session.",
+          "Checklist completion is tracked in analytics."
+        ],
+        priority: "high",
+        tags: ["activation", "onboarding"]
+      }
+    ]
+  },
+  tasks: {
+    packId: "product-intent.discovery.activation.tasks",
+    patchId: "product-intent.discovery.activation.patch",
+    overview: "Introduce a checklist-driven onboarding path and instrument it for activation measurement.",
+    tasks: [
+      {
+        id: "task-ui-checklist",
+        title: "Model the onboarding checklist surface",
+        surface: ["ui", "docs"],
+        why: "The product intent needs a visible activation guide and matching contract docs.",
+        acceptance: [
+          "A checklist surface is defined in contracts.",
+          "Documentation explains the activation milestone mapping."
+        ],
+        agentPrompt: "Add the onboarding checklist contract surface and document the milestone states."
+      },
+      {
+        id: "task-analytics-checklist",
+        title: "Track checklist completion events",
+        surface: ["api", "tests"],
+        why: "Success must be measurable after rollout.",
+        acceptance: [
+          "Checklist completion emits analytics events.",
+          "Tests cover the event contract and payload shape."
+        ],
+        agentPrompt: "Emit activation checklist events and add test coverage for the telemetry payloads.",
+        dependsOn: ["task-ui-checklist"]
+      }
+    ]
+  }
+});
+
 // src/product-intent.feature.ts
 import { defineFeature } from "@contractspec/lib.contracts-spec";
 var ProductIntentFeature = defineFeature({
@@ -360,6 +433,7 @@ export {
   loadEvidenceChunks,
   example_default as example,
   ProductIntentFeature,
+  ProductIntentDiscoverySpec,
   DEFAULT_TRANSCRIPT_DIRS,
   DEFAULT_EVIDENCE_ROOT,
   DEFAULT_CHUNK_SIZE

package/dist/node/index.js

@@ -336,6 +336,79 @@ async function loadEvidenceChunksWithSignals(options = {}) {
   return [...baseChunks, ...posthogChunks];
 }
 
+// src/product-intent.discovery.ts
+import {
+  OwnersEnum,
+  StabilityEnum
+} from "@contractspec/lib.contracts-spec/ownership";
+import { defineProductIntentSpec } from "@contractspec/lib.contracts-spec/product-intent/spec";
+var ProductIntentDiscoverySpec = defineProductIntentSpec({
+  id: "product-intent.discovery.activation",
+  meta: {
+    key: "product-intent.discovery.activation",
+    version: "1.0.0",
+    title: "Product Intent Discovery",
+    description: "Discovery contract for activation friction using transcripts, analytics signals, and generated tasks.",
+    domain: "product",
+    owners: [OwnersEnum.PlatformCore],
+    tags: ["product-intent", "discovery", "activation", "analytics"],
+    stability: StabilityEnum.Experimental,
+    goal: "Prioritize the next activation improvement with grounded evidence.",
+    context: "Evidence is collected from interview transcripts, support tickets, and PostHog funnels before turning into task-ready outputs."
+  },
+  question: "Which activation and onboarding friction should we prioritize next?",
+  runtimeContext: {
+    evidenceRoot: "packages/examples/product-intent/evidence",
+    analyticsProvider: "posthog"
+  },
+  tickets: {
+    tickets: [
+      {
+        ticketId: "PI-101",
+        title: "Add a guided onboarding checklist",
+        summary: "Give new users an explicit checklist after signup so they can see the next activation milestone.",
+        evidenceIds: ["INT-002", "INT-014", "PH-dropoff-checkout"],
+        acceptanceCriteria: [
+          "Users see a checklist within the first session.",
+          "Checklist completion is tracked in analytics."
+        ],
+        priority: "high",
+        tags: ["activation", "onboarding"]
+      }
+    ]
+  },
+  tasks: {
+    packId: "product-intent.discovery.activation.tasks",
+    patchId: "product-intent.discovery.activation.patch",
+    overview: "Introduce a checklist-driven onboarding path and instrument it for activation measurement.",
+    tasks: [
+      {
+        id: "task-ui-checklist",
+        title: "Model the onboarding checklist surface",
+        surface: ["ui", "docs"],
+        why: "The product intent needs a visible activation guide and matching contract docs.",
+        acceptance: [
+          "A checklist surface is defined in contracts.",
+          "Documentation explains the activation milestone mapping."
+        ],
+        agentPrompt: "Add the onboarding checklist contract surface and document the milestone states."
+      },
+      {
+        id: "task-analytics-checklist",
+        title: "Track checklist completion events",
+        surface: ["api", "tests"],
+        why: "Success must be measurable after rollout.",
+        acceptance: [
+          "Checklist completion emits analytics events.",
+          "Tests cover the event contract and payload shape."
+        ],
+        agentPrompt: "Emit activation checklist events and add test coverage for the telemetry payloads.",
+        dependsOn: ["task-ui-checklist"]
+      }
+    ]
+  }
+});
+
 // src/product-intent.feature.ts
 import { defineFeature } from "@contractspec/lib.contracts-spec";
 var ProductIntentFeature = defineFeature({
@@ -359,6 +432,7 @@ export {
   loadEvidenceChunks,
   example_default as example,
   ProductIntentFeature,
+  ProductIntentDiscoverySpec,
   DEFAULT_TRANSCRIPT_DIRS,
   DEFAULT_EVIDENCE_ROOT,
   DEFAULT_CHUNK_SIZE

package/dist/node/product-intent.discovery.js

@@ -0,0 +1,75 @@
+// src/product-intent.discovery.ts
+import {
+  OwnersEnum,
+  StabilityEnum
+} from "@contractspec/lib.contracts-spec/ownership";
+import { defineProductIntentSpec } from "@contractspec/lib.contracts-spec/product-intent/spec";
+var ProductIntentDiscoverySpec = defineProductIntentSpec({
+  id: "product-intent.discovery.activation",
+  meta: {
+    key: "product-intent.discovery.activation",
+    version: "1.0.0",
+    title: "Product Intent Discovery",
+    description: "Discovery contract for activation friction using transcripts, analytics signals, and generated tasks.",
+    domain: "product",
+    owners: [OwnersEnum.PlatformCore],
+    tags: ["product-intent", "discovery", "activation", "analytics"],
+    stability: StabilityEnum.Experimental,
+    goal: "Prioritize the next activation improvement with grounded evidence.",
+    context: "Evidence is collected from interview transcripts, support tickets, and PostHog funnels before turning into task-ready outputs."
+  },
+  question: "Which activation and onboarding friction should we prioritize next?",
+  runtimeContext: {
+    evidenceRoot: "packages/examples/product-intent/evidence",
+    analyticsProvider: "posthog"
+  },
+  tickets: {
+    tickets: [
+      {
+        ticketId: "PI-101",
+        title: "Add a guided onboarding checklist",
+        summary: "Give new users an explicit checklist after signup so they can see the next activation milestone.",
+        evidenceIds: ["INT-002", "INT-014", "PH-dropoff-checkout"],
+        acceptanceCriteria: [
+          "Users see a checklist within the first session.",
+          "Checklist completion is tracked in analytics."
+        ],
+        priority: "high",
+        tags: ["activation", "onboarding"]
+      }
+    ]
+  },
+  tasks: {
+    packId: "product-intent.discovery.activation.tasks",
+    patchId: "product-intent.discovery.activation.patch",
+    overview: "Introduce a checklist-driven onboarding path and instrument it for activation measurement.",
+    tasks: [
+      {
+        id: "task-ui-checklist",
+        title: "Model the onboarding checklist surface",
+        surface: ["ui", "docs"],
+        why: "The product intent needs a visible activation guide and matching contract docs.",
+        acceptance: [
+          "A checklist surface is defined in contracts.",
+          "Documentation explains the activation milestone mapping."
+        ],
+        agentPrompt: "Add the onboarding checklist contract surface and document the milestone states."
+      },
+      {
+        id: "task-analytics-checklist",
+        title: "Track checklist completion events",
+        surface: ["api", "tests"],
+        why: "Success must be measurable after rollout.",
+        acceptance: [
+          "Checklist completion emits analytics events.",
+          "Tests cover the event contract and payload shape."
+        ],
+        agentPrompt: "Emit activation checklist events and add test coverage for the telemetry payloads.",
+        dependsOn: ["task-ui-checklist"]
+      }
+    ]
+  }
+});
+export {
+  ProductIntentDiscoverySpec
+};

package/dist/product-intent.discovery.d.ts

@@ -0,0 +1,4 @@
+export declare const ProductIntentDiscoverySpec: import("@contractspec/lib.contracts-spec/product-intent/spec").ProductIntentSpec<{
+    evidenceRoot: string;
+    analyticsProvider: string;
+}>;

package/dist/product-intent.discovery.js

@@ -0,0 +1,76 @@
+// @bun
+// src/product-intent.discovery.ts
+import {
+  OwnersEnum,
+  StabilityEnum
+} from "@contractspec/lib.contracts-spec/ownership";
+import { defineProductIntentSpec } from "@contractspec/lib.contracts-spec/product-intent/spec";
+var ProductIntentDiscoverySpec = defineProductIntentSpec({
+  id: "product-intent.discovery.activation",
+  meta: {
+    key: "product-intent.discovery.activation",
+    version: "1.0.0",
+    title: "Product Intent Discovery",
+    description: "Discovery contract for activation friction using transcripts, analytics signals, and generated tasks.",
+    domain: "product",
+    owners: [OwnersEnum.PlatformCore],
+    tags: ["product-intent", "discovery", "activation", "analytics"],
+    stability: StabilityEnum.Experimental,
+    goal: "Prioritize the next activation improvement with grounded evidence.",
+    context: "Evidence is collected from interview transcripts, support tickets, and PostHog funnels before turning into task-ready outputs."
+  },
+  question: "Which activation and onboarding friction should we prioritize next?",
+  runtimeContext: {
+    evidenceRoot: "packages/examples/product-intent/evidence",
+    analyticsProvider: "posthog"
+  },
+  tickets: {
+    tickets: [
+      {
+        ticketId: "PI-101",
+        title: "Add a guided onboarding checklist",
+        summary: "Give new users an explicit checklist after signup so they can see the next activation milestone.",
+        evidenceIds: ["INT-002", "INT-014", "PH-dropoff-checkout"],
+        acceptanceCriteria: [
+          "Users see a checklist within the first session.",
+          "Checklist completion is tracked in analytics."
+        ],
+        priority: "high",
+        tags: ["activation", "onboarding"]
+      }
+    ]
+  },
+  tasks: {
+    packId: "product-intent.discovery.activation.tasks",
+    patchId: "product-intent.discovery.activation.patch",
+    overview: "Introduce a checklist-driven onboarding path and instrument it for activation measurement.",
+    tasks: [
+      {
+        id: "task-ui-checklist",
+        title: "Model the onboarding checklist surface",
+        surface: ["ui", "docs"],
+        why: "The product intent needs a visible activation guide and matching contract docs.",
+        acceptance: [
+          "A checklist surface is defined in contracts.",
+          "Documentation explains the activation milestone mapping."
+        ],
+        agentPrompt: "Add the onboarding checklist contract surface and document the milestone states."
+      },
+      {
+        id: "task-analytics-checklist",
+        title: "Track checklist completion events",
+        surface: ["api", "tests"],
+        why: "Success must be measurable after rollout.",
+        acceptance: [
+          "Checklist completion emits analytics events.",
+          "Tests cover the event contract and payload shape."
+        ],
+        agentPrompt: "Emit activation checklist events and add test coverage for the telemetry payloads.",
+        dependsOn: ["task-ui-checklist"]
+      }
+    ]
+  }
+});
+export {
+  ProductIntentDiscoverySpec
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contractspec/example.product-intent",
-  "version": "3.7.7",
+  "version": "3.7.10",
   "description": "Product intent example: evidence ingestion and prompt-ready outputs.",
   "keywords": [
     "contractspec",
@@ -48,6 +48,12 @@
       "node": "./dist/node/posthog-signals.js",
       "default": "./dist/posthog-signals.js"
     },
+    "./product-intent.discovery": {
+      "types": "./dist/product-intent.discovery.d.ts",
+      "bun": "./dist/product-intent.discovery.js",
+      "node": "./dist/node/product-intent.discovery.js",
+      "default": "./dist/product-intent.discovery.js"
+    },
     "./product-intent.feature": {
       "types": "./dist/product-intent.feature.d.ts",
       "bun": "./dist/product-intent.feature.js",
@@ -83,17 +89,17 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@contractspec/lib.analytics": "3.7.7",
-    "@contractspec/lib.contracts-spec": "4.0.0",
-    "@contractspec/lib.contracts-integrations": "3.7.7",
-    "@contractspec/lib.ai-agent": "7.0.7",
-    "@contractspec/lib.product-intent-utils": "3.7.7",
-    "@contractspec/integration.providers-impls": "3.7.7"
+    "@contractspec/lib.analytics": "3.7.10",
+    "@contractspec/lib.contracts-spec": "4.1.2",
+    "@contractspec/lib.contracts-integrations": "3.8.2",
+    "@contractspec/lib.ai-agent": "7.0.10",
+    "@contractspec/lib.product-intent-utils": "3.7.10",
+    "@contractspec/integration.providers-impls": "3.8.2"
   },
   "devDependencies": {
-    "@contractspec/tool.typescript": "3.7.6",
+    "@contractspec/tool.typescript": "3.7.8",
     "typescript": "^5.9.3",
-    "@contractspec/tool.bun": "3.7.6"
+    "@contractspec/tool.bun": "3.7.8"
   },
   "publishConfig": {
     "access": "public",
@@ -134,6 +140,12 @@
         "node": "./dist/node/posthog-signals.js",
         "default": "./dist/posthog-signals.js"
       },
+      "./product-intent.discovery": {
+        "types": "./dist/product-intent.discovery.d.ts",
+        "bun": "./dist/product-intent.discovery.js",
+        "node": "./dist/node/product-intent.discovery.js",
+        "default": "./dist/product-intent.discovery.js"
+      },
       "./product-intent.feature": {
         "types": "./dist/product-intent.feature.d.ts",
         "bun": "./dist/product-intent.feature.js",

package/src/contracts.test.ts

@@ -0,0 +1,14 @@
+import { describe, expect, test } from 'bun:test';
+import { ProductIntentDiscoverySpec, ProductIntentFeature } from './index';
+
+describe('@contractspec/example.product-intent', () => {
+	test('exports the canonical product intent spec', () => {
+		expect(ProductIntentDiscoverySpec.meta.key).toBe(
+			'product-intent.discovery.activation'
+		);
+		expect(ProductIntentDiscoverySpec.question).toContain('activation');
+		expect(ProductIntentDiscoverySpec.tickets?.tickets).toHaveLength(1);
+		expect(ProductIntentDiscoverySpec.tasks?.tasks).toHaveLength(2);
+		expect(ProductIntentFeature.meta.key).toBe('product-intent');
+	});
+});

package/src/index.ts

@@ -15,4 +15,5 @@ export {
 	loadPosthogEvidenceChunks,
 	resolvePosthogEvidenceOptionsFromEnv,
 } from './posthog-signals';
+export * from './product-intent.discovery';
 export * from './product-intent.feature';

package/src/product-intent.discovery.ts

@@ -0,0 +1,79 @@
+import {
+	OwnersEnum,
+	StabilityEnum,
+} from '@contractspec/lib.contracts-spec/ownership';
+import { defineProductIntentSpec } from '@contractspec/lib.contracts-spec/product-intent/spec';
+
+export const ProductIntentDiscoverySpec = defineProductIntentSpec({
+	id: 'product-intent.discovery.activation',
+	meta: {
+		key: 'product-intent.discovery.activation',
+		version: '1.0.0',
+		title: 'Product Intent Discovery',
+		description:
+			'Discovery contract for activation friction using transcripts, analytics signals, and generated tasks.',
+		domain: 'product',
+		owners: [OwnersEnum.PlatformCore],
+		tags: ['product-intent', 'discovery', 'activation', 'analytics'],
+		stability: StabilityEnum.Experimental,
+		goal: 'Prioritize the next activation improvement with grounded evidence.',
+		context:
+			'Evidence is collected from interview transcripts, support tickets, and PostHog funnels before turning into task-ready outputs.',
+	},
+	question:
+		'Which activation and onboarding friction should we prioritize next?',
+	runtimeContext: {
+		evidenceRoot: 'packages/examples/product-intent/evidence',
+		analyticsProvider: 'posthog',
+	},
+	tickets: {
+		tickets: [
+			{
+				ticketId: 'PI-101',
+				title: 'Add a guided onboarding checklist',
+				summary:
+					'Give new users an explicit checklist after signup so they can see the next activation milestone.',
+				evidenceIds: ['INT-002', 'INT-014', 'PH-dropoff-checkout'],
+				acceptanceCriteria: [
+					'Users see a checklist within the first session.',
+					'Checklist completion is tracked in analytics.',
+				],
+				priority: 'high',
+				tags: ['activation', 'onboarding'],
+			},
+		],
+	},
+	tasks: {
+		packId: 'product-intent.discovery.activation.tasks',
+		patchId: 'product-intent.discovery.activation.patch',
+		overview:
+			'Introduce a checklist-driven onboarding path and instrument it for activation measurement.',
+		tasks: [
+			{
+				id: 'task-ui-checklist',
+				title: 'Model the onboarding checklist surface',
+				surface: ['ui', 'docs'],
+				why: 'The product intent needs a visible activation guide and matching contract docs.',
+				acceptance: [
+					'A checklist surface is defined in contracts.',
+					'Documentation explains the activation milestone mapping.',
+				],
+				agentPrompt:
+					'Add the onboarding checklist contract surface and document the milestone states.',
+			},
+			{
+				id: 'task-analytics-checklist',
+				title: 'Track checklist completion events',
+				surface: ['api', 'tests'],
+				why: 'Success must be measurable after rollout.',
+				acceptance: [
+					'Checklist completion emits analytics events.',
+					'Tests cover the event contract and payload shape.',
+				],
+				agentPrompt:
+					'Emit activation checklist events and add test coverage for the telemetry payloads.',
+				dependsOn: ['task-ui-checklist'],
+			},
+		],
+	},
+});