@sellable/mcp 0.1.141 → 0.1.143

package/skills/create-campaign-v2/core/policy.md

@@ -3,17 +3,15 @@
 This policy is the invariant layer for the from-scratch v2 orchestrator. Follow
 it even if prompt prose is ambiguous.
 
-## 1) JSON State Machine First
+## 1) Campaign State First
 
-`core/flow.v2.json` is the source of truth for:
+`core/flow.v2.json` defines the stage order and tool gates. CampaignOffer state,
+the watched app, selected source/list state, and campaign-table rows are the
+runtime source of truth.
 
-- stage order
-- required artifacts
-- produced artifacts
-- allowed tools
-- forbidden tools
-- wait events
-- transitions
+Normal create-campaign-v2 runs do not use local markdown/json artifacts as
+required state. Debug artifacts can exist only for explicit debug/UAT or legacy
+validation harnesses, and they must never override live campaign state.
 
 `SKILL.md` explains how to execute the flow. It does not replace the flow.
 
@@ -28,40 +26,37 @@ bootstrap -> brief-interview
 Do not start at `validate-artifacts` unless resuming a compatibility run where
 the complete upstream artifact set already exists.
 
-## 3) No Mutation Before Approval
+## 3) Shell-First Mutation Gates
 
-Before the user explicitly chooses `approve` at the commit gate, do not call:
+Create the campaign shell early after campaign identity and the initial brief
+are good enough for the customer to watch setup progress. Then enforce these
+mutation gates:
 
-- `create_campaign`
-- `save_rubrics`
-- `import_leads`
-- `confirm_lead_list`
-- `update_campaign`
-- `queue_cells`
-- `start_campaign`
+- Do not call provider search/import tools until the user approves the source
+  plan or explicitly chooses a source.
+- Do not call `import_leads` or `confirm_lead_list` until the concrete source
+  action is approved.
+- Import/confirm only the first bounded review batch before message approval.
+- Do not call `queue_cells` until filter choice is resolved, rubrics are saved
+  when filters are enabled, and the default Use Template path has an approved
+  message template/token rule set.
+- Do not attach a sequence or call `start_campaign` until the user explicitly
+  chooses to launch.
 
 Customer roleplay critique is advisory only. It cannot approve a campaign.
 
-## 4) Artifact Gates
+## 4) State Gates
 
-Do not run a downstream stage until the active step's `requiredArtifacts` exist.
-Intermediate user-review gates are interrupt-only: auto-continue when an
-artifact is confirmed and no strategic tradeoff is present. The final commit
-gate is the only mandatory pre-mint approval gate.
+Do not run a downstream stage until the matching live state exists:
 
-The minimum pre-approval chain is:
-
-```text
-brief.md
-lead-review.md
-lead-sample.json
-lead-filter.md
-message-prep.md (optional)
-message-candidate-drafts.md (optional, generated from find-leads basis rows)
-message-validation.md
-approval-packet.md
-commit-gate-decision.md
-```
+- campaign shell exists before a watch link is shown as active
+- selected source/list state exists before importing a review batch
+- `workflowTableId` and non-empty bounded review-batch rows exist before filter
+  and message branches run
+- `leadScoringRubrics` are saved before queueing ICP filter cells when filters
+  are enabled
+- approved message template/token rules are written to campaign brief before
+  queueing Generate Message cells on the default Use Template path
 
 ## 5) Revision Routing
 
@@ -73,10 +68,11 @@ Revision choices route back to the exact upstream stage:
 - `revise-messaging` -> `message-generation`
 - `abort` -> stop with zero DB mutation
 
-## 6) Post-Approval Tail
+## 6) Post-Message Tail
 
-After `approve`, mint atomically with `create_campaign` and `save_rubrics`.
-Only then surface the watch link and continue the cascade-driven tail.
+After message approval, queue only the bounded review-batch cells needed to move
+the watched app through enrichment, ICP filtering, and approved-template
+message generation. Keep the tail observable through watch narration.
 
 The tail stops at `awaiting-user-greenlight`. Never call `start_campaign`
 inside the autonomous tail.

package/skills/create-campaign-v2/references/draft-lifecycle.md

@@ -1,110 +1,26 @@
-# Draft Lifecycle
+# Legacy Debug Artifact Lifecycle
 
-Phase 84 validates the Phase 83 brief through chained artifacts in one draft
-directory:
+Normal `create-campaign-v2` does not use a local draft directory. CampaignOffer
+state, the watched app, selected source/list state, and campaign-table rows are
+the source of truth.
 
-`.sellable/create-campaign-v2/drafts/{workspace-slug}/{campaign-slug}/`
+Use this reference only for explicit debug/UAT work or compatibility validation
+harnesses that intentionally emit local diagnostic artifacts. Do not load it for
+normal customer-facing create-campaign runs.
 
-Required files as the chain advances:
+## Rules For Debug/UAT Artifacts
 
-```text
-brief.md
-lead-review.md
-lead-sample.json
-lead-filter.md
-message-validation.md
-rubric.json   # optional
-```
+- Treat artifacts as diagnostic copies, not durable campaign state.
+- Never surface local artifact paths to customers unless they explicitly ask for
+  debug output.
+- Never resume a live campaign from diagnostic files when CampaignOffer state is
+  available.
+- Never let diagnostic files override selected source/list ids, table ids, row
+  ids, saved rubrics, approved templates, or watch narration.
+- Keep all customer approvals and product mutations tied to live campaign state.
 
-## Artifact Roles
+## Compatibility Boundary
 
-- `brief.md`
-  - stable Phase 83 thesis
-  - preserved during validation
-- `lead-review.md`
-  - human-readable analysis of the preview run
-- `lead-sample.json`
-  - machine-readable lead sample for filter and message validation
-- `lead-filter.md`
-  - primary keep/exclude output for the middle step
-  - owns required keep rules, required exclude rules, sample false positives,
-    pass-rate judgment, and the final recommendation
-- `rubric.json`
-  - optional implementation sidecar only
-  - must be derived from `lead-filter.md`, not designed separately
-- `message-validation.md`
-  - final message check against the validated lead set
-
-## Serial Step Order
-
-Run in this order only:
-
-1. find leads
-2. filter leads
-3. generate message
-
-Do not skip ahead unless the required upstream artifacts already exist and are
-complete.
-
-## Atomic Writes
-
-Every artifact edit must be written as:
-
-1. read the current artifact if it exists
-2. compute the full replacement contents
-3. write `{artifact}.tmp`
-4. rename `{artifact}.tmp` -> `{artifact}`
-
-If the write fails before rename, the old artifact remains the valid state.
-
-## Resume Rules
-
-- `brief.md` only -> run `find leads`
-- `lead-review.md` + `lead-sample.json` present -> run `filter leads` and
-  `generate message` from the same find-leads basis
-- `lead-filter.md` present and `message-validation.md` missing -> run
-  `generate message`
-- `message-validation.md` present and `lead-filter.md` missing -> run
-  `filter leads`
-- `message-validation.md` + `lead-filter.md` present -> reconcile and stop,
-  validation complete
-
-Invalid partial states must stop for repair:
-
-- `lead-review.md` exists but `lead-sample.json` is missing
-- `lead-sample.json` exists but `lead-review.md` is missing
-- `lead-filter.md` exists without both upstream lead artifacts
-- approval packet or commit gate exists without both `message-validation.md`
-  and `lead-filter.md`
-
-## Revision Rules
-
-- `revise-brief`
-  - preserve `brief.md`
-  - delete `lead-review.md`
-  - delete `lead-sample.json`
-  - delete `lead-filter.md`
-  - delete `message-validation.md`
-  - delete `rubric.json` if present
-- `revise-leads`
-  - delete `lead-review.md`
-  - delete `lead-sample.json`
-  - delete downstream artifacts (`lead-filter.md`, `message-validation.md`, `rubric.json`)
-- `revise-filter`
-  - preserve lead preview artifacts
-  - delete `lead-filter.md`
-  - delete `message-validation.md`
-  - delete `rubric.json` if present
-- `revise-message`
-  - preserve upstream artifacts
-  - delete `message-validation.md`
-
-## No-Mutation Boundary
-
-During Phase 84, the artifact chain is local draft state only. Do not:
-
-- create or update a `CampaignOffer`
-- import leads
-- persist a selected lead list
-- create workflow rows
-- attach sequences
+Legacy validation harnesses may still use a serial artifact chain to test
+prompt behavior without mutating product state. That boundary does not apply to
+normal shell-first create-campaign execution.