@sellable/mcp 0.1.142 → 0.1.144

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.