# JuniperWorks campaign launch gate — evidence-and-artifact workbook

**Case packet version:** 2026.08.31-practice-3

**Case brief record:** CB01

This fictional, sanitized training case contains fabricated campaign and audience data. It includes no real personal or confidential records and does not provide legal, privacy, advertising, or revenue guarantees.

## How to use this workbook

Complete only what the fictional packet supports. Cite the module input ID beside each material statement. Write **not supplied** for missing operational records, approvals, dates, test results, or identities. Label anything you design as a **learner proposal**. Do not contact people, access systems, run tests, sign records, or present a proposed control as an observed fact. Each module contains a prerequisite gate, six-to-eight task-specific operating steps, field-by-field guidance, schema-exact supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, a completion test, blank artifact tables, and mapped criteria. Row counts are contractual: if an assignment calls for 47 requirements, 20 records, 40 evaluations, or 27 tasks, the corresponding table contains that many stable rows.

## Module 1 — Make the brief decidable

**Task mode:** bounded-case-starter

**Prompt:** Resolve the competing expectations into one primary objective and supporting constraints.

**Deliverable:** A campaign-brief proposal with objective, audience, budget, capacity, metric, and decision use, plus an approval-request field left pending.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M01-I01 | case-fact | F01 | The campaign budget ceiling is $24,000. | |
| M01-I02 | case-fact | F02 | Marketing seeks awareness, finance expects eighty qualified registrations, and sales capacity is twenty handoffs. | |
| M01-I03 | case-fact | F10 | The one-hour sales target conflicts with Mountain Time business-hour coverage. | |
| M01-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M01-S01 | assignment-scope | F01, F02, F10 | Build a starter version of “A campaign-brief proposal with objective, audience, budget, capacity, metric, and decision use, plus an approval-request field left pending.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F01, F02, F10, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm F01, F02, and F10; record that the primary objective, valid-registration definition, qualification rule, coverage plan, and approval are not supplied.
- [ ] STOP. If the primary objective, valid-registration definition, qualification rule, or coverage plan is missing or conflicts with F01/F02/F10, route the decision to authorized marketing/finance and sales/service leadership; do not claim campaign approval or execute launch.

### Operating procedure

1. Capture the $24,000 ceiling, competing objectives, eighty-registration expectation, twenty-handoff capacity, and coverage conflict.
2. Define valid registration separately from qualified handoff.
3. Select one primary objective as a learner proposal and list other expectations as constraints.
4. Test the proposed objective against sales capacity and business-hour coverage.
5. Define repeat, revise, and stop signals before launch.
6. Route objective, capacity, and response-target decisions to marketing, finance, and sales owners for approval.

### Field-by-field guidance — M01-A01

| Field | What high-quality completion requires |
|---|---|
| Section | Name the brief section or decision topic this row resolves. Module use: Use the brief to turn conflicting campaign expectations into one measurable, capacity-aware decision. |
| Supported statement | Write a bounded statement supported by cited packet facts. Module use: Use the brief to turn conflicting campaign expectations into one measurable, capacity-aware decision. |
| Source input ID | Cite the exact Fxx or module input ID supporting the entry. Module use: Use the brief to turn conflicting campaign expectations into one measurable, capacity-aware decision. |
| Assumption or gap | Separate a provisional assumption from evidence that is absent. Module use: Use the brief to turn conflicting campaign expectations into one measurable, capacity-aware decision. |
| Decision requested | Frame the exact approval, clarification, or risk decision needed. Module use: Use the brief to turn conflicting campaign expectations into one measurable, capacity-aware decision. |
| Reviewer | Name the qualified review role and leave approval pending. Module use: Use the brief to turn conflicting campaign expectations into one measurable, capacity-aware decision. |
| Status | Use a truthful state such as draft, open—not supplied, review pending, or blocked. Module use: Use the brief to turn conflicting campaign expectations into one measurable, capacity-aware decision. |

### Completed supported example — M01-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Section | Supported statement | Source input ID | Assumption or gap | Decision requested | Reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Primary campaign decision | Budget ceiling is $24,000; finance expects 80 qualified registrations while sales capacity is 20 handoffs. | F01, F02 | Valid-registration and qualification definitions are not supplied; objective is a learner proposal. | Approve one primary objective and a capacity-compatible handoff limit. | Marketing owner with finance and sales reviewers | Draft — cross-functional approval pending |

### Completed known-gap example — M01-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Section | Supported statement | Source input ID | Assumption or gap | Decision requested | Reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Response-time commitment | The one-hour target conflicts with Mountain Time business-hour coverage. | F10 | Staffing schedule and approved exception rule are not supplied. | Approve a business-hour service target or funded coverage change. | Sales/service owner | Open — not supplied |

### Supporting artifact build sequence

1. **M01-A02 · Campaign approval request** — Produce a bounded, reviewable campaign approval request from cited packet evidence while exposing unsupported fields and required approvals. Build 1 row from M01-I02, M01-I03 and address M01-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

#### M01-A02 · Campaign approval request

**Reference-only completed row.** Use it to understand the evidence boundary; do not present it as your own completed work.

**Criterion demonstrated:** M01-EC02

**Why this row is included:** The canonical M01-A02 route maps M01-EC02. This row converts the supplied 20-handoff capacity and conflicting objectives into an explicit approval decision without claiming that an owner approved it.

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Decision requested: approve one primary campaign objective and a capacity-compatible limit of no more than 20 discovery handoffs during the campaign month. | M01-I02 (F02) states that sales can accept no more than 20 discovery handoffs during the campaign month. | M01-I02 (F02) also records finance's expectation of 80 qualified registrations and marketing's awareness objective; M01-I03 (F10) records that the one-hour response target conflicts with Mountain Time business-hour coverage. | Learner-proposed options: align the objective and handoff limit to current capacity; fund additional qualified coverage; or hold launch until the objective, qualification rule, and response commitment are reconciled. | Authorized marketing owner with sales and finance review; the named decision maker is not supplied. | Marketing, sales, and finance approval is not supplied; response-time approval also remains pending. | Open — capacity-aligned decision and approvals pending |

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop campaign approval when the primary objective, valid outcome, capacity, or service coverage is unresolved. |
| **Go** | Proceed to review when one objective and its repeat/revise/stop metric fit the $24,000 ceiling and twenty-handoff capacity. |
| **Escalate** | Escalate objective conflicts to marketing/finance and coverage conflicts to sales/service leadership. |

### Completion test

- [ ] Objective, audience, budget, capacity, outcome definition, and decision use are explicit.
- [ ] F01/F02/F10 are preserved without manufactured targets.
- [ ] Approval and launch status remain pending.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M01-A01 | M01-EC01 | M01-I01 (F01) | The campaign budget ceiling is $24,000. | State the supplied condition with its limitation and frame the decision that an authorized reviewer must make. Cite M01-I01 (F01) in the row. | This is one evidence-backed starter entry, not a completed campaign brief or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M01-A02 | M01-EC02 | The packet does not supply the complete live records, approvals, or execution results needed to finish the campaign approval request. | Without that evidence, the learner cannot truthfully satisfy M01-EC02 or represent this artifact as complete. | Marketing process owner and approval reviewer | Record the missing evidence in M01-A02, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M01-I03:** What bounded decision can the Marketing process owner and approval reviewer make from M01-I03, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M01-A01 · Campaign brief

**Purpose:** Produce a bounded, reviewable campaign brief from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M01-I01, M01-I02, M01-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M01-EC01:** Defines valid registration and qualified handoff separately
- **M01-EC03:** States what result would support repeat, revision, or stop
- **M01-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Section | Supported statement | Source input ID | Assumption or gap | Decision requested | Reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 01A01R-01 |  |  |  |  |  | Not started |
| 01A01R-02 |  |  |  |  |  | Not started |
| 01A01R-03 |  |  |  |  |  | Not started |
| 01A01R-04 |  |  |  |  |  | Not started |
| 01A01R-05 |  |  |  |  |  | Not started |
| 01A01R-06 |  |  |  |  |  | Not started |
| 01A01R-07 |  |  |  |  |  | Not started |
| 01A01R-08 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M01-I01).
- [ ] Every mapped rubric criterion (M01-EC01, M01-EC03, M01-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M01-A02 · Campaign approval request

**Purpose:** Produce a bounded, reviewable campaign approval request from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M01-I02, M01-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M01-EC02:** Fits the objective to actual sales capacity

| Decision | Evidence for | Evidence against | Options and tradeoffs | Decision owner | Required approval | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 01A02R-01 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M01-I02, M01-I03).
- [ ] Every mapped rubric criterion (M01-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M01-A01 · Campaign brief | 8 | M01-EC01, M01-EC03, M01-EC04 | M01-I01, M01-I02, M01-I03 |
| M01-A02 · Campaign approval request | 1 | M01-EC02 | M01-I02, M01-I03 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M01-EC01:** Defines valid registration and qualified handoff separately
- [ ] **M01-EC02:** Fits the objective to actual sales capacity
- [ ] **M01-EC03:** States what result would support repeat, revision, or stop
- [ ] **M01-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 2 — Build the eligible audience

**Task mode:** bounded-case-starter

**Prompt:** Apply purpose, consent, suppression, minimization, duplication, and segment rules before activation.

**Deliverable:** An aggregate audience decision table and suppression-test plan with test records and results explicitly pending.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M02-I01 | case-fact | F03 | The audience file contains 9,400 business contacts. | |
| M02-I02 | case-fact | F04 | The file includes 620 opt-outs, 240 duplicates, and 85 rows with personal observations. | |
| M02-I03 | case-fact | F05 | Permission for follow-up is not documented for 730 trade-show scan records. | |
| M02-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M02-S01 | assignment-scope | F03, F04, F05 | Build a starter version of “An aggregate audience decision table and suppression-test plan with test records and results explicitly pending.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F03, F04, F05, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm F03–F05; record that row-level contacts, consent records, suppression execution, duplicate resolution, and test results are absent.
- [ ] STOP. If consent evidence, suppression status, duplicate resolution, or row-level eligibility is missing or conflicts with F03–F05, route the audience to the authorized privacy/marketing-operations reviewer; do not claim audience approval or execute activation, suppression, or deduplication.

### Operating procedure

1. Record the 9,400-contact population and each aggregate risk count.
2. Define exclusion for 620 opt-outs and quarantine for 85 personal-observation rows.
3. Define deduplication for 240 duplicates without claiming records were merged.
4. Quarantine 730 trade-show scans until purpose/permission evidence is reviewed.
5. Specify inclusion, exclusion, duplicate, and unresolved-purpose decisions with owners.
6. Quality-check counts, rules, source IDs, and pending execution/results.

### Field-by-field guidance — M02-A01

| Field | What high-quality completion requires |
|---|---|
| Item ID | Use a stable local identifier; it is not evidence of a live record. Module use: Use the table to make aggregate eligibility, suppression, deduplication, minimization, and permission rules inspectable. |
| Supported evidence | State only the packet-supported observation, preserving confidence and uncertainty. Module use: Use the table to make aggregate eligibility, suppression, deduplication, minimization, and permission rules inspectable. |
| Source input ID | Cite the exact Fxx or module input ID supporting the entry. Module use: Use the table to make aggregate eligibility, suppression, deduplication, minimization, and permission rules inspectable. |
| Criterion or required state | State the observable rule, gate, or condition the entry is tested against. Module use: Use the table to make aggregate eligibility, suppression, deduplication, minimization, and permission rules inspectable. |
| Gap or learner proposal | Write “not supplied” for missing evidence; label any designed rule as a learner proposal. Module use: Use the table to make aggregate eligibility, suppression, deduplication, minimization, and permission rules inspectable. |
| Owner or reviewer | Name an authorized role, never an invented person or completed approval. Module use: Use the table to make aggregate eligibility, suppression, deduplication, minimization, and permission rules inspectable. |
| Status | Use a truthful state such as draft, open—not supplied, review pending, or blocked. Module use: Use the table to make aggregate eligibility, suppression, deduplication, minimization, and permission rules inspectable. |

### Completed supported example — M02-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| AUD-OPT-OUT | 620 contacts are recorded as opted out. | F04 | Required state: exclude from activation; row-level suppression result is not supplied. | Learner proposal — suppression rule and failure test. | Marketing operations and privacy reviewer | Draft — execution not performed |

### Completed known-gap example — M02-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| AUD-TRADESHOW | 730 trade-show scan records lack documented follow-up permission. | F05 | Permission-review rule required; individual purpose/consent records are not supplied. | Quarantine until authorized permission review. | Privacy/marketing owner | Blocked — not supplied |

### Supporting artifact build sequence

1. **M02-A02 · Suppression-test plan** — Produce a bounded, reviewable suppression-test plan from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M02-I02 and address M02-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop activation when opt-outs, personal observations, unresolved permission, or failed suppression remain in scope. |
| **Go** | Proceed only after approved rules and test evidence show eligible, deduplicated, minimized records. |
| **Escalate** | Escalate undocumented purpose/permission and sensitive observations to privacy review. |

### Completion test

- [ ] F03–F05 counts reconcile to clearly named decision categories.
- [ ] Each category has inclusion/exclusion/quarantine logic and owner.
- [ ] No row-level processing or suppression result is claimed.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M02-A01 | M02-EC01 | M02-I01 (F03) | The audience file contains 9,400 business contacts. | Place the supplied condition in the appropriate comparison row and leave every unsupplied requirement visibly open. Cite M02-I01 (F03) in the row. | This is one evidence-backed starter entry, not a completed aggregate audience decision table or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M02-A01 | M02-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the aggregate audience decision table. | Without that evidence, the learner cannot truthfully satisfy M02-EC01 or represent this artifact as complete. | Marketing process owner and approval reviewer | Record the missing evidence in M02-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M02-I03:** What bounded decision can the Marketing process owner and approval reviewer make from M02-I03, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M02-A01 · Aggregate audience decision table

**Purpose:** Produce a bounded, reviewable aggregate audience decision table from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M02-I01, M02-I03, M02-I02

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M02-EC01:** Uses F03 through F05 to define removal, quarantine, deduplication, and permission-review rules without claiming row-level processing
- **M02-EC03:** Documents proposed inclusion, exclusion, deduplication, and customer-treatment logic for authorized review
- **M02-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Item ID | Supported evidence | Source input ID | Criterion or required state | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 02A01R-01 |  |  |  |  |  | Not started |
| 02A01R-02 |  |  |  |  |  | Not started |
| 02A01R-03 |  |  |  |  |  | Not started |
| 02A01R-04 |  |  |  |  |  | Not started |
| 02A01R-05 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M02-I01, M02-I03).
- [ ] Every mapped rubric criterion (M02-EC01, M02-EC03, M02-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M02-A02 · Suppression-test plan

**Purpose:** Produce a bounded, reviewable suppression-test plan from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M02-I02

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M02-EC02:** Specifies suppression success, duplicate, unresolved-purpose, and failure test cases without claiming execution

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 02A02R-01 |  |  |  |  |  | Not started |
| 02A02R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M02-I02).
- [ ] Every mapped rubric criterion (M02-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M02-A01 · Aggregate audience decision table | 5 | M02-EC01, M02-EC03, M02-EC04 | M02-I01, M02-I03, M02-I02 |
| M02-A02 · Suppression-test plan | 2 | M02-EC02 | M02-I02 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M02-EC01:** Uses F03 through F05 to define removal, quarantine, deduplication, and permission-review rules without claiming row-level processing
- [ ] **M02-EC02:** Specifies suppression success, duplicate, unresolved-purpose, and failure test cases without claiming execution
- [ ] **M02-EC03:** Documents proposed inclusion, exclusion, deduplication, and customer-treatment logic for authorized review
- [ ] **M02-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 3 — Control claims and assets

**Task mode:** bounded-case-starter

**Prompt:** Repair the delay claim and reconcile approved, live, speaker, and image versions.

**Deliverable:** A claim-ledger starter, asset gap manifest, and version-control release checklist; no version-seven asset package or approval is represented as supplied.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M03-I01 | case-fact | F06 | The 35-percent delay claim uses three selected customers; the full eight-customer review ranges from a 9-percent increase to a 31-percent decrease using different definitions and periods. | |
| M03-I02 | case-fact | F07 | The approved design is version seven and the live page is version six with an old price. | |
| M03-I03 | case-fact | F11 | Legal and privacy reviews and the speaker release remain incomplete. | |
| M03-I04 | case-fact | F12 | The license record for one proposed image cannot be found. | |
| M03-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M03-S01 | assignment-scope | F06, F07, F11, F12 | Build a starter version of “A claim-ledger starter, asset gap manifest, and version-control release checklist; no version-seven asset package or approval is represented as supplied.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F06, F07, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm F06, F07, F11, and F12; obtain no customer-level calculations, approved asset package, release, legal/privacy approval, or image license.
- [ ] STOP. If claim calculations, asset version, release, legal/privacy approval, or image license is missing or conflicts with F06/F07/F11/F12, route it to the authorized evidence, legal/privacy, and rights reviewers; do not claim asset approval or execute publication or release.

### Operating procedure

1. Record the exact 35-percent claim and identify its three-customer selection.
2. Record the full eight-customer range and the differing definitions/periods.
3. Separate observed range from proposed public wording.
4. Name the calculation, source, period, owner, and limitation needed for authorization.
5. Link claim release to version, approval, speaker release, and image-license gates.
6. Block publication until claim support and every material asset right are verified.

### Field-by-field guidance — M03-A01

| Field | What high-quality completion requires |
|---|---|
| Claim ID | Assign a stable training-ledger ID; it is not a live asset record. |
| Claim text | Write the exact proposed claim or asset assertion and clearly mark blocked or proposed language. |
| Population | State the represented population and selection limits; use Not supplied when unavailable. |
| Definition | Record the metric definition and any inconsistent definitions. |
| Period | Record the measurement period or Not supplied when periods differ or are absent. |
| Calculation or source | Cite the module input/fact ID and calculation record; do not invent operands. |
| Limitation | State selection, definition, period, license, release, or version limits. |
| Approval owner | Name the authorized marketing, legal, privacy, or rights-review role. |
| Asset version | Record the evidenced version or Not applicable; never infer the approved live version. |
| Release status | Use Blocked, Draft — review pending, or Released only when explicit evidence supports it. |

### Completed supported example — M03-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Claim ID | Claim text | Population | Definition | Period | Calculation or source | Limitation | Approval owner | Asset version | Release status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| CLAIM-01 | Proposed “35-percent delay reduction” claim — blocked from publication. | Three selected customers; full review covers eight customers. | Definitions differ across the selected and full-customer review. | Different periods; exact comparable period not supplied. | M03-I01 (F06): full review ranges from a 9-percent increase to a 31-percent decrease. | Selection, definition, and period differences do not support the proposed headline. | Marketing evidence owner and legal reviewer | Not applicable to evidence row | Blocked — substantiation not supplied |

### Completed known-gap example — M03-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Claim ID | Claim text | Population | Definition | Period | Calculation or source | Limitation | Approval owner | Asset version | Release status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| CLAIM-ASSET-02 | Price and speaker-content publication gate | Not applicable | Approved design and live-page version must match. | Current publication window not supplied. | M03-I02 (F07); M03-I03 (F11); M03-I04 (F12) | Live page is version six while approved design is version seven; reviews, release, and one image license record are incomplete. | Marketing, legal/privacy, speaker-release, and rights-review owners | Live v6; approved design v7 | Blocked — approval package incomplete |

### Supporting artifact build sequence

1. **M03-A02 · Asset gap manifest** — Produce a bounded, reviewable asset gap manifest from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M03-I02, M03-I04 and address M03-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M03-A03 · Version-control release checklist** — Produce a bounded, reviewable version-control release checklist from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M03-I03 and address M03-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop publication when claim population/definition differs materially, the live asset is stale, or required releases/licenses are missing. |
| **Go** | Proceed only when claim math, definitions, period, asset version, rights, and approvals are traceable. |
| **Escalate** | Escalate statistical claim wording to evidence/legal review and missing rights to the asset owner. |

### Completion test

- [ ] Selected-sample and full-range evidence are both visible.
- [ ] Every proposed claim has source, owner, limitation, and release gate.
- [ ] No approval or publication is implied.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M03-A01 | M03-EC01 | M03-I01 (F06) | The 35-percent delay claim uses three selected customers; the full eight-customer review ranges from a 9-percent increase to a 31-percent decrease using different definitions and periods. | Open a traceable register entry for the supplied condition and route the unresolved decision to the named authorized role. Cite M03-I01 (F06) in the row. | This is one evidence-backed starter entry, not a completed marketing claim ledger or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M03-A01 | M03-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the marketing claim ledger. | Without that evidence, the learner cannot truthfully satisfy M03-EC01 or represent this artifact as complete. | Marketing process owner and approval reviewer | Record the missing evidence in M03-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M03-I04:** What bounded decision can the Marketing process owner and approval reviewer make from M03-I04, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M03-A01 · Marketing claim ledger

**Purpose:** Produce a bounded, reviewable marketing claim ledger from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M03-I01, M03-I02, M03-I03, M03-I04

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M03-EC01:** Represents the three selected customers and full eight-customer range in F06 with definitions, period differences, and limitations

| Claim ID | Claim text | Population | Definition | Period | Calculation or source | Limitation | Approval owner | Asset version | Release status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 03A01R-01 |  |  |  |  |  |  |  |  | Not started |
| 03A01R-02 |  |  |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M03-I01).
- [ ] Every mapped rubric criterion (M03-EC01) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M03-A02 · Asset gap manifest

**Purpose:** Produce a bounded, reviewable asset gap manifest from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M03-I02, M03-I04

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M03-EC02:** Links each evidenced or proposed asset row to approval, owner, license, and effective-version fields without inventing the missing records

| Item | Source or location | Version or date | Owner | Access or review status | Gap |
| --- | --- | --- | --- | --- | --- |
| 03A02R-01 |  |  |  |  | Not started |
| 03A02R-02 |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M03-I02, M03-I04).
- [ ] Every mapped rubric criterion (M03-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M03-A03 · Version-control release checklist

**Purpose:** Produce a bounded, reviewable version-control release checklist from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M03-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M03-EC03:** Blocks publication of missing releases or unsupported claims

| Check ID | Control or check | Evidence required | Source input ID | Owner | Result | Exception or gap | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 03A03R-01 |  |  |  |  |  |  | Not started |
| 03A03R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M03-I03).
- [ ] Every mapped rubric criterion (M03-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M03-A01 · Marketing claim ledger | 2 | M03-EC01 | M03-I01, M03-I02, M03-I03, M03-I04 |
| M03-A02 · Asset gap manifest | 2 | M03-EC02 | M03-I02, M03-I04 |
| M03-A03 · Version-control release checklist | 2 | M03-EC03 | M03-I03 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M03-EC01:** Represents the three selected customers and full eight-customer range in F06 with definitions, period differences, and limitations
- [ ] **M03-EC02:** Links each evidenced or proposed asset row to approval, owner, license, and effective-version fields without inventing the missing records
- [ ] **M03-EC03:** Blocks publication of missing releases or unsupported claims

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 4 — Preflight tracking

**Task mode:** bounded-case-starter

**Prompt:** Specify event, parameter, form, routing, accessibility, mobile, privacy, and failure tests.

**Deliverable:** A tracking plan and preflight evidence-capture checklist with execution, signature, and results fields explicitly pending.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M04-I01 | case-fact | F07 | The approved design is version seven and the live page is version six with an old price. | |
| M04-I02 | case-fact | F08 | Campaign parameters are inconsistent and duplicate conversion events are not tested. | |
| M04-I03 | case-fact | F11 | Legal and privacy reviews and the speaker release remain incomplete. | |
| M04-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M04-S01 | assignment-scope | F07, F08, F11 | Build a starter version of “A tracking plan and preflight evidence-capture checklist with execution, signature, and results fields explicitly pending.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F07, F08, F11, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm F07, F08, and F11; record that event schema, parameter convention, accessibility/mobile results, privacy approval, signatures, and launch authorization are absent.
- [ ] STOP. If the event schema, parameter convention, accessibility/mobile evidence, or privacy authorization is missing or conflicts with F07/F08/F11, route the preflight to authorized analytics, privacy, and accessibility owners; do not claim tracking approval or execute testing or launch.

### Operating procedure

1. Inventory required events and parameters as proposed definitions.
2. Use F08 to define one controlled campaign-parameter convention.
3. Design success, duplicate, invalid, opt-out, and system-failure paths.
4. Specify event deduplication evidence and failure handling.
5. Place privacy, accessibility, claim, and version failures behind a launch-blocking gate.
6. Route execution evidence and approval to marketing operations, analytics, privacy, and accessibility reviewers.

### Field-by-field guidance — M04-A01

| Field | What high-quality completion requires |
|---|---|
| Step or milestone | Name one ordered action or decision checkpoint. Module use: Use the plan to specify tracking behavior and launch gates before any test is run. |
| Trigger or date | Use a supplied trigger; write date not supplied when absent. Module use: Use the plan to specify tracking behavior and launch gates before any test is run. |
| Evidence and source ID | Pair the observation with its exact supplied source ID. Module use: Use the plan to specify tracking behavior and launch gates before any test is run. |
| Owner | Name the authorized operating or specialist role. Module use: Use the plan to specify tracking behavior and launch gates before any test is run. |
| Gate or threshold | State a measurable provisional gate and who must approve it. Module use: Use the plan to specify tracking behavior and launch gates before any test is run. |
| Dependency or gap | Name the evidence, owner, or prerequisite that blocks progression. Module use: Use the plan to specify tracking behavior and launch gates before any test is run. |
| Status | Use a truthful state such as draft, open—not supplied, review pending, or blocked. Module use: Use the plan to specify tracking behavior and launch gates before any test is run. |

### Completed supported example — M04-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| TRACK-01 | Before preflight execution | F08: campaign parameters are inconsistent and duplicate conversion events are not tested. | Marketing operations/analytics owner | Learner proposal: one controlled parameter convention and a duplicate-event negative test. | Approved event schema and execution evidence not supplied. | Draft — test pending |

### Completed known-gap example — M04-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| TRACK-02 | Before launch approval | F07: live page is version six with an old price; F11: legal/privacy review incomplete. | Marketing and privacy reviewers | Gate: correct version and required approvals must be evidenced. | Approval, accessibility result, and signature not supplied. | Blocked |

### Supporting artifact build sequence

1. **M04-A02 · Preflight evidence-capture checklist** — Produce a bounded, reviewable preflight evidence-capture checklist from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M04-I02 and address M04-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop launch for duplicate conversion, privacy/accessibility failure, stale asset, unsupported claim, or missing approval. |
| **Go** | Proceed to controlled test only when event/parameter definitions and evidence-capture method are approved. |
| **Escalate** | Escalate privacy, accessibility, claim, and version failures to their qualified owners. |

### Completion test

- [ ] Event and parameter conventions and five path types are specified.
- [ ] Every test has expected evidence and pending result.
- [ ] Launch-blocking gates and owners are explicit.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M04-A01 | M04-EC01 | M04-I01 (F07) | The approved design is version seven and the live page is version six with an old price. | Use the supplied condition to define one bounded step and a review gate; leave dates and execution results pending unless supplied. Cite M04-I01 (F07) in the row. | This is one evidence-backed starter entry, not a completed campaign tracking plan or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M04-A01 | M04-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the campaign tracking plan. | Without that evidence, the learner cannot truthfully satisfy M04-EC01 or represent this artifact as complete. | Marketing process owner and approval reviewer | Record the missing evidence in M04-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M04-I03:** What bounded decision can the Marketing process owner and approval reviewer make from M04-I03, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M04-A01 · Campaign tracking plan

**Purpose:** Produce a bounded, reviewable campaign tracking plan from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M04-I01, M04-I03, M04-I02

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M04-EC01:** Defines one controlled parameter convention and an event-deduplication test design
- **M04-EC03:** Treats critical privacy, accessibility, or claim failure as launch blocking and leaves authorization pending
- **M04-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 04A01R-01 |  |  |  |  |  | Not started |
| 04A01R-02 |  |  |  |  |  | Not started |
| 04A01R-03 |  |  |  |  |  | Not started |
| 04A01R-04 |  |  |  |  |  | Not started |
| 04A01R-05 |  |  |  |  |  | Not started |
| 04A01R-06 |  |  |  |  |  | Not started |
| 04A01R-07 |  |  |  |  |  | Not started |
| 04A01R-08 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M04-I01, M04-I03).
- [ ] Every mapped rubric criterion (M04-EC01, M04-EC03, M04-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M04-A02 · Preflight evidence-capture checklist

**Purpose:** Produce a bounded, reviewable preflight evidence-capture checklist from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M04-I02

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M04-EC02:** Specifies success, duplicate, invalid, opt-out, and system-failure paths without claiming those tests were run

| Check ID | Control or check | Evidence required | Source input ID | Owner | Result | Exception or gap | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 04A02R-01 |  |  |  |  |  |  | Not started |
| 04A02R-02 |  |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M04-I02).
- [ ] Every mapped rubric criterion (M04-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M04-A01 · Campaign tracking plan | 8 | M04-EC01, M04-EC03, M04-EC04 | M04-I01, M04-I03, M04-I02 |
| M04-A02 · Preflight evidence-capture checklist | 2 | M04-EC02 | M04-I02 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M04-EC01:** Defines one controlled parameter convention and an event-deduplication test design
- [ ] **M04-EC02:** Specifies success, duplicate, invalid, opt-out, and system-failure paths without claiming those tests were run
- [ ] **M04-EC03:** Treats critical privacy, accessibility, or claim failure as launch blocking and leaves authorization pending
- [ ] **M04-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 5 — Design the handoff

**Task mode:** bounded-case-starter

**Prompt:** Route registrations by audience and qualification while making service targets achievable.

**Deliverable:** A routing map, handoff record, acceptance workflow, and coverage plan.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M05-I01 | case-fact | F02 | Marketing seeks awareness, finance expects eighty qualified registrations, and sales capacity is twenty handoffs. | |
| M05-I02 | case-fact | F09 | Every form submission currently routes to sales regardless of fit or completeness. | |
| M05-I03 | case-fact | F10 | The one-hour sales target conflicts with Mountain Time business-hour coverage. | |
| M05-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M05-S01 | assignment-scope | F02, F09, F10 | Build a starter version of “A routing map, handoff record, acceptance workflow, and coverage plan.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F02, F09, F10, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm F02, F09, and F10; record that audience tags, qualification fields, consent status, staffing coverage, record-level submissions, and acceptance results are absent.
- [ ] STOP. If qualification fields, consent status, staffing coverage, or submission evidence is missing or conflicts with F02/F09/F10, route the handoff rule to authorized sales/service leadership; do not claim handoff approval or execute routing, acceptance, or a service commitment.

### Operating procedure

1. Define customer, prospect, student, vendor, and incomplete intake classes.
2. Map required qualification and consent evidence before any sales handoff.
3. Use F09 to replace route-everything behavior with fit/completeness gates.
4. Use F02 to cap proposed handoffs at observable sales capacity.
5. Use F10 to define business-hour timing and exception ownership.
6. Check every route for rejection reason, owner, evidence, and pending execution status.

### Field-by-field guidance — M05-A01

| Field | What high-quality completion requires |
|---|---|
| Element | Name the process node, asset, state, or transition. Module use: Use the map to route submissions by identity, fit, completeness, consent, and achievable service coverage. |
| From or trigger | State the observable event that activates the path. Module use: Use the map to route submissions by identity, fit, completeness, consent, and achievable service coverage. |
| To or outcome | State the proposed next state without implying execution. Module use: Use the map to route submissions by identity, fit, completeness, consent, and achievable service coverage. |
| Evidence and source ID | Pair the observation with its exact supplied source ID. Module use: Use the map to route submissions by identity, fit, completeness, consent, and achievable service coverage. |
| Owner | Name the authorized operating or specialist role. Module use: Use the map to route submissions by identity, fit, completeness, consent, and achievable service coverage. |
| Open question | Record the unanswered question that prevents a final decision. Module use: Use the map to route submissions by identity, fit, completeness, consent, and achievable service coverage. |
| Status | Use a truthful state such as draft, open—not supplied, review pending, or blocked. Module use: Use the map to route submissions by identity, fit, completeness, consent, and achievable service coverage. |

### Completed supported example — M05-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Element | From or trigger | To or outcome | Evidence and source ID | Owner | Open question | Status |
| --- | --- | --- | --- | --- | --- | --- |
| ROUTE-01 | New form submission | Qualification and consent gate before sales; incomplete or non-prospect classes route elsewhere. | F09 | Marketing operations and sales owner | Audience, qualification, and consent fields are not supplied. | Learner proposal — approval pending |

### Completed known-gap example — M05-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Element | From or trigger | To or outcome | Evidence and source ID | Owner | Open question | Status |
| --- | --- | --- | --- | --- | --- | --- |
| ROUTE-02 | Qualified prospect after business hours | Queue to approved next-business-hour owner or exception path. | F10 | Sales/service owner | Coverage schedule and approved exception target not supplied. | Blocked — coverage decision needed |

### Supporting artifact build sequence

1. **M05-A02 · Sales handoff record** — Produce a bounded, reviewable sales handoff record from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M05-I01, M05-I02 and address M05-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M05-A03 · Lead acceptance workflow** — Produce a bounded, reviewable lead acceptance workflow from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M05-I03 and address M05-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
3. **M05-A04 · Coverage plan** — Produce a bounded, reviewable coverage plan from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M05-I03 and address M05-EC04. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop sales handoff when fit, completeness, consent, owner, or achievable service target is missing. |
| **Go** | Route only after the approved evidence gate is met and capacity is available. |
| **Escalate** | Escalate capacity or after-hours exceptions to sales/service leadership. |

### Completion test

- [ ] Five submission classes and incomplete path are visible.
- [ ] Qualification, consent, capacity, timing, and rejection reasons are explicit.
- [ ] No submission is represented as actually routed.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M05-A01 | M05-EC01 | M05-I01 (F02) | Marketing seeks awareness, finance expects eighty qualified registrations, and sales capacity is twenty handoffs. | Anchor one element of the map to the supplied condition and label any inferred transition as a learner proposal. Cite M05-I01 (F02) in the row. | This is one evidence-backed starter entry, not a completed lead-routing map or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M05-A01 | M05-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the lead-routing map. | Without that evidence, the learner cannot truthfully satisfy M05-EC01 or represent this artifact as complete. | Marketing process owner and approval reviewer | Record the missing evidence in M05-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M05-I03:** What bounded decision can the Marketing process owner and approval reviewer make from M05-I03, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M05-A01 · Lead-routing map

**Purpose:** Produce a bounded, reviewable lead-routing map from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M05-I01, M05-I02, M05-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M05-EC01:** Separates customer, prospect, student, vendor, and incomplete submissions

| Element | From or trigger | To or outcome | Evidence and source ID | Owner | Open question | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 05A01R-01 |  |  |  |  |  | Not started |
| 05A01R-02 |  |  |  |  |  | Not started |
| 05A01R-03 |  |  |  |  |  | Not started |
| 05A01R-04 |  |  |  |  |  | Not started |
| 05A01R-05 |  |  |  |  |  | Not started |
| 05A01R-06 |  |  |  |  |  | Not started |
| 05A01R-07 |  |  |  |  |  | Not started |
| 05A01R-08 |  |  |  |  |  | Not started |
| 05A01R-09 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M05-I01).
- [ ] Every mapped rubric criterion (M05-EC01) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M05-A02 · Sales handoff record

**Purpose:** Produce a bounded, reviewable sales handoff record from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M05-I01, M05-I02

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M05-EC02:** Uses qualification evidence and consent status in the handoff

| Record ID | Supported facts | Source input ID | Decision or action pending | Owner or reviewer | Evidence needed | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 05A02R-01 |  |  |  |  |  | Not started |
| 05A02R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M05-I01, M05-I02).
- [ ] Every mapped rubric criterion (M05-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M05-A03 · Lead acceptance workflow

**Purpose:** Produce a bounded, reviewable lead acceptance workflow from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M05-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M05-EC03:** Defines business-hour service targets, exceptions, ownership, and rejection reasons

| Element | From or trigger | To or outcome | Evidence and source ID | Owner | Open question | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 05A03R-01 |  |  |  |  |  | Not started |
| 05A03R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M05-I03).
- [ ] Every mapped rubric criterion (M05-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M05-A04 · Coverage plan

**Purpose:** Produce a bounded, reviewable coverage plan from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M05-I03

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M05-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Step or milestone | Trigger or date | Evidence and source ID | Owner | Gate or threshold | Dependency or gap | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 05A04R-01 |  |  |  |  |  | Not started |
| 05A04R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M05-I03).
- [ ] Every mapped rubric criterion (M05-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M05-A01 · Lead-routing map | 9 | M05-EC01 | M05-I01, M05-I02, M05-I03 |
| M05-A02 · Sales handoff record | 2 | M05-EC02 | M05-I01, M05-I02 |
| M05-A03 · Lead acceptance workflow | 2 | M05-EC03 | M05-I03 |
| M05-A04 · Coverage plan | 2 | M05-EC04 | M05-I03 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M05-EC01:** Separates customer, prospect, student, vendor, and incomplete submissions
- [ ] **M05-EC02:** Uses qualification evidence and consent status in the handoff
- [ ] **M05-EC03:** Defines business-hour service targets, exceptions, ownership, and rejection reasons
- [ ] **M05-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Module 6 — Report learning honestly

**Task mode:** bounded-case-starter

**Prompt:** Create a reporting and archive design that distinguishes measurement rules from causal claims.

**Deliverable:** A metric dictionary, campaign report template, and archival index.

### Supplied-input register

| Input ID | Kind | Source record(s) | What the packet supplies | Where I used it |
|---|---|---|---|---|
| M06-I01 | case-fact | F01 | The campaign budget ceiling is $24,000. | |
| M06-I02 | case-fact | F02 | Marketing seeks awareness, finance expects eighty qualified registrations, and sales capacity is twenty handoffs. | |
| M06-I03 | case-fact | F03 | The audience file contains 9,400 business contacts. | |
| M06-I04 | case-fact | F04 | The file includes 620 opt-outs, 240 duplicates, and 85 rows with personal observations. | |
| M06-I05 | case-fact | F05 | Permission for follow-up is not documented for 730 trade-show scan records. | |
| M06-I06 | case-fact | F06 | The 35-percent delay claim uses three selected customers; the full eight-customer review ranges from a 9-percent increase to a 31-percent decrease using different definitions and periods. | |
| M06-I07 | case-fact | F07 | The approved design is version seven and the live page is version six with an old price. | |
| M06-I08 | case-fact | F08 | Campaign parameters are inconsistent and duplicate conversion events are not tested. | |
| M06-I09 | case-fact | F09 | Every form submission currently routes to sales regardless of fit or completeness. | |
| M06-I10 | case-fact | F10 | The one-hour sales target conflicts with Mountain Time business-hour coverage. | |
| M06-I11 | case-fact | F11 | Legal and privacy reviews and the speaker release remain incomplete. | |
| M06-I12 | case-fact | F12 | The license record for one proposed image cannot be found. | |
| M06-B01 | case-brief | CB01 | Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment. | |
| M06-S01 | assignment-scope | F01, F02, F03, F04, F05, F06, F07, F08, F09, F10, F11, F12 | Build a starter version of “A metric dictionary, campaign report template, and archival index.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it. | |

### Completion boundary

Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F04, F05, F06, F07, F08, F09, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

### Prerequisite check

- [ ] Confirm F01–F12; record that final campaign period, attribution window, validated outcomes, approved exclusions, and results are absent.
- [ ] STOP. If the reporting period, attribution window, outcome definition, exclusions, or validated results are missing or conflict across F01–F12, route the metric to authorized analytics/privacy/finance owners; do not claim report approval or execute publication, and do not assert causal impact or results.

### Operating procedure

1. Define each metric with population, period, source, attribution window, exclusions, and limitation.
2. Separate registration, qualified handoff, acceptance, spend, and service measures.
3. Use F03/F04/F05 to define eligible audience denominators and exclusions.
4. Use F08/F09 to expose duplicate-event and route-everything limitations.
5. Use F01/F02 to connect spend to capacity-bounded outcomes without causal claims.
6. Version the dictionary and route changes to marketing, finance, privacy, analytics, and sales owners.

### Field-by-field guidance — M06-A01

| Field | What high-quality completion requires |
|---|---|
| Term or field | Name one metric, field, category, or controlled term. Module use: Use the dictionary to make campaign measures reproducible and prevent causal overclaiming. |
| Definition | Write an operational definition with observable inclusion and exclusion rules. Module use: Use the dictionary to make campaign measures reproducible and prevent causal overclaiming. |
| Allowed values or rule | List controlled values or a provisional rule for reviewer approval. Module use: Use the dictionary to make campaign measures reproducible and prevent causal overclaiming. |
| Evidence source | Cite the packet input or mark the future operational source not supplied. Module use: Use the dictionary to make campaign measures reproducible and prevent causal overclaiming. |
| Owner | Name the authorized operating or specialist role. Module use: Use the dictionary to make campaign measures reproducible and prevent causal overclaiming. |
| Change trigger | State what evidence or approval requires the definition to change. Module use: Use the dictionary to make campaign measures reproducible and prevent causal overclaiming. |
| Status | Use a truthful state such as draft, open—not supplied, review pending, or blocked. Module use: Use the dictionary to make campaign measures reproducible and prevent causal overclaiming. |

### Completed supported example — M06-A01

**Reference only.** This row demonstrates supported evidence and truthful status; it is not a learner submission or proof of live work.

| Term or field | Definition | Allowed values or rule | Evidence source | Owner | Change trigger | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Qualified handoff | A submission meeting approved fit, completeness, and consent rules and accepted by sales. | Learner-proposed controlled values: pending / accepted / rejected with reason. | F02, F09 | Marketing analytics and sales owner | Change when qualification or acceptance rules are approved/revised. | Draft — definition approval pending |

### Completed known-gap example — M06-A01

**Reference only.** This row demonstrates how to preserve missing evidence without inventing a result.

| Term or field | Definition | Allowed values or rule | Evidence source | Owner | Change trigger | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Attribution window | Not supplied; must state population, period, source, exclusions, and limitations before reporting. | Not supplied | F06, F08 | Marketing analytics owner | Obtain approved window and validated event-deduplication evidence. | Open — reporting blocked |

### Supporting artifact build sequence

1. **M06-A02 · Campaign report template** — Produce a bounded, reviewable campaign report template from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M06-I01, M06-I07, M06-I10 and address M06-EC02. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”
2. **M06-A03 · Campaign archive index** — Produce a bounded, reviewable campaign archive index from cited packet evidence while exposing unsupported fields and required approvals. Build 2 rows from M06-I03, M06-I08, M06-I11 and address M06-EC03. Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

### Completed supporting-artifact examples

No additional completed supporting-artifact row is supplied. Use the supporting artifact instructions, scoped inputs, completion checks, and known-gap method above; keep unsupported cells marked **not supplied**.

### Stop / Go / Escalate

| Decision | Rule |
|---|---|
| **Stop** | Stop reporting when population, period, source, exclusions, attribution window, or duplicate-event handling is unknown. |
| **Go** | Proceed when every metric is reproducible and results are clearly descriptive, not causal. |
| **Escalate** | Escalate attribution, privacy, and outcome-definition disputes to analytics/privacy/finance owners. |

### Completion test

- [ ] All decision metrics have full operational definitions.
- [ ] Spend and outcomes are connected without causal language.
- [ ] Archive/version owner and change trigger are explicit.

### Secondary evidence-trace crosswalk

The authored procedure and schema-exact examples above are the main teaching method. This compact crosswalk links the legacy starter and gap controls to the original packet.

#### Legacy worked-starter trace

| Artifact | Criterion | Input | Supported value | How to use it | Boundary |
|---|---|---|---|---|---|
| M06-A01 | M06-EC01 | M06-I02 (F02) | Marketing seeks awareness, finance expects eighty qualified registrations, and sales capacity is twenty handoffs. | Use the supplied term or condition to draft one definition while marking allowed values and approval status provisional. Cite M06-I02 (F02) in the row. | This is one evidence-backed starter entry, not a completed marketing metric dictionary or an operational result. |

#### Legacy known-gap trace

| Artifact | Criterion | Missing evidence | Why it matters | Authorized owner or reviewer | Bounded next step | Status |
|---|---|---|---|---|---|---|
| M06-A01 | M06-EC01 | The packet does not supply the complete live records, approvals, or execution results needed to finish the marketing metric dictionary. | Without that evidence, the learner cannot truthfully satisfy M06-EC01 or represent this artifact as complete. | Marketing process owner and approval reviewer | Record the missing evidence in M06-A01, name the authorized reviewer, and leave the outcome pending; do not obtain or simulate the live record in this exercise. | Open — not supplied |

### Decision prompt

**M06-I10:** What bounded decision can the Marketing process owner and approval reviewer make from M06-I10, and what must remain pending until the missing evidence or approval is supplied?

### Artifact-build tables

### M06-A01 · Marketing metric dictionary

**Purpose:** Produce a bounded, reviewable marketing metric dictionary from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M06-I02, M06-I04, M06-I05, M06-I06, M06-I09, M06-I12, M06-I01, M06-I03, M06-I08, M06-I10

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M06-EC01:** States population, period, source, attribution window, exclusions, and limitations
- **M06-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

| Term or field | Definition | Allowed values or rule | Evidence source | Owner | Change trigger | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 06A01R-01 |  |  |  |  |  | Not started |
| 06A01R-02 |  |  |  |  |  | Not started |
| 06A01R-03 |  |  |  |  |  | Not started |
| 06A01R-04 |  |  |  |  |  | Not started |
| 06A01R-05 |  |  |  |  |  | Not started |
| 06A01R-06 |  |  |  |  |  | Not started |
| 06A01R-07 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M06-I02, M06-I04, M06-I05, M06-I06, M06-I09, M06-I12).
- [ ] Every mapped rubric criterion (M06-EC01, M06-EC04) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M06-A02 · Campaign report template

**Purpose:** Produce a bounded, reviewable campaign report template from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M06-I01, M06-I07, M06-I10

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M06-EC02:** Connects spend to valid outcomes without claiming attribution proves causation

| Section or field | Purpose | Supported entry | Source input ID | Gap or learner proposal | Owner or reviewer | Status |
| --- | --- | --- | --- | --- | --- | --- |
| 06A02R-01 |  |  |  |  |  | Not started |
| 06A02R-02 |  |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M06-I01, M06-I07, M06-I10).
- [ ] Every mapped rubric criterion (M06-EC02) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### M06-A03 · Campaign archive index

**Purpose:** Produce a bounded, reviewable campaign archive index from cited packet evidence while exposing unsupported fields and required approvals.

**Scoped case-fact inputs:** M06-I03, M06-I08, M06-I11

**Instructions:** Use only the scoped case-fact inputs below. Cite an input ID for each supported statement; label proposed structures “learner proposal” and unavailable evidence “not supplied.”

**Mapped evidence criteria**

- **M06-EC03:** Preserves final assets, approvals, tests, results, and lessons for reuse

| Item | Source or location | Version or date | Owner | Access or review status | Gap |
| --- | --- | --- | --- | --- | --- |
| 06A03R-01 |  |  |  |  | Not started |
| 06A03R-02 |  |  |  |  | Not started |

**Completion checks**

- [ ] Every supported entry identifies and cites at least one applicable scoped case-fact input (M06-I03, M06-I08, M06-I11).
- [ ] Every mapped rubric criterion (M06-EC03) is addressed in the artifact or a named evidence gap.
- [ ] Unsupported fields remain “not supplied” or are explicitly labeled as a learner proposal.
- [ ] The Marketing process owner and approval reviewer is named for decisions or review; no approval or execution is implied.

### Artifact coverage map

| Artifact | Expected rows | Mapped criteria | Scoped case-fact inputs |
|---|---:|---|---|
| M06-A01 · Marketing metric dictionary | 7 | M06-EC01, M06-EC04 | M06-I02, M06-I04, M06-I05, M06-I06, M06-I09, M06-I12, M06-I01, M06-I03, M06-I08, M06-I10 |
| M06-A02 · Campaign report template | 2 | M06-EC02 | M06-I01, M06-I07, M06-I10 |
| M06-A03 · Campaign archive index | 2 | M06-EC03 | M06-I03, M06-I08, M06-I11 |

### Decision and revision record

| Decision or question | Supported observations with input IDs | Contradictory evidence | Learner proposal | Alternative | Evidence that would change the recommendation |
|---|---|---|---|---|---|
| | | | | | |

### Evidence-criteria checklist

- [ ] **M06-EC01:** States population, period, source, attribution window, exclusions, and limitations
- [ ] **M06-EC02:** Connects spend to valid outcomes without claiming attribution proves causation
- [ ] **M06-EC03:** Preserves final assets, approvals, tests, results, and lessons for reuse
- [ ] **M06-EC04:** Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

### Self-review note

- What did I initially assume?
- Which input contradicted or weakened that assumption?
- What remains outside my role or authority?
- What will I revise before asking for human feedback?

## Final packet review

- [ ] Every material statement cites an input ID.
- [ ] Every omitted record is marked **not supplied**.
- [ ] Every designed control or template is marked **learner proposal**.
- [ ] Every mapped criterion is addressed in its artifact or a named gap.
- [ ] Contracted row counts and row IDs remain intact.
- [ ] Specialist and decision-owner handoffs are explicit.
- [ ] No simulated work is represented as a completed real-world action, approval, test, signature, or professional opinion.