#### Day 43 — A learner-facing update needs an approval and dispatch ledger **Objective.** Write a useful 60–100-word learner-facing holding message and separately prove its actual release state. Apply the existing C9/C9X negative controls to [EX043](#exercise-ex043). **Technical teaching.** Audience-specific language is not permission to change evidence. Learners may need a verified enrollment effect, narrow service-return status, next action and update channel; they do not need internal accounts, the pseudonym batch or uncertain gateway details in a service-only update. The designated privacy/legal owner must still assess whether separate data-related messaging is legally or contractually required. [NIST Privacy Framework](https://www.nist.gov/privacy-framework) supports managing privacy risk; it determines neither the legal classification of a CTN token nor a notification deadline. Treat communication as a **state machine**: DRAFT → technically reviewed → privacy/legal reviewed where applicable → approved for a particular audience and channel → dispatch attempted → transport result recorded → superseded if necessary. Each transition needs a versioned receipt. Approval without a transport record is not dispatch. A transport attempt is not recipient delivery, and delivery does not prove reading. The retained §9.11 C9 lab has two invented unapproved message flags and prints **C9 internal release=BLOCK** and **C9 learner release=BLOCK**. Its “REVIEW” state after a hypothetical local flag change would still not be an external send. The §9.15 C9X INVALID_SENT_UNAPPROVED case rejects a contradictory *simulated* sent=True without approval, not a real CTN event. **Worked example: proposed public copy (not sent).** > A class enrollment slot was temporarily unavailable. CTN completed its selected checks and returned that slot to use at 10:45 UTC. We continue to monitor enrollment and review the event. No action is requested from learners based on this service update. We will provide another status by 12:00 UTC through the designated channel. If you encounter a new enrollment error, please contact the usual support desk so our team can investigate that specific report. Attach a **separate** process card: audience “CTN learners”; evidence “C29–C30 only for service assertion”; business reviewer “service owner, pending”; release reviewer “communications owner, pending”; privacy/legal content assessment “refer to authorized specialist if required”; delivery receipt “none”; state **DRAFT/UNSENT**. The 12:00 time obligates another *status*, not a promised conclusion. **Counterexample.** “We proved no information was disclosed” is unsupported by C33. “Notified all twelve affected people” invents recipient mapping, approval and a dispatch. Even if a draft has a correct service sentence, none of those statements can be smuggled into its release record. **Independent practice.** Write the original [EX043](#exercise-ex043) learner text (60–100 words) and a six-field process card documenting reviewer, channel, scope, cutoff, approval and actual delivery state. Interpret both C9 BLOCK outputs; name what a genuine approval and transport receipt would require. **Artifacts:** public draft and separate release record. **Rubric 0–2:** 2 for bounded useful wording, no restricted identifiers and explicitly unsent status; 1 for sound copy with incomplete release evidence; 0 for claiming breach/no breach, completed delivery or unapproved disclosure. See [worked answer](#answer-ex043). **Continue studying — Day 43:** [← Day 42](#week-09-day-02) · [Course index](../SUBJECTS.md) · [Day 44 →](#week-09-day-04) ### Exercise for this lesson **EX043 — Learner-facing draft.** Inputs: C29/C30 and the still-open C31–C33 assessment. Write a 60–100-word holding update with service effect, current status, action required, next update and approval state. A 2-point result contains no internal account or token details and is marked unsent until approved. Apply the fail-closed C9 release fixture in §9.11 and attach the approval/delivery state to your draft record. ## Worked answers **EX043 — Model learner-facing draft.** “A class enrollment slot was temporarily unavailable. CTN completed service checks and returned that slot to use at 10:45 UTC. We are continuing to monitor enrollment and review the event. Learners do not need to take action based on this update. We plan to post another status by 12:00 UTC through this channel. This is a draft for service-owner and communications review and has not been sent.” The last sentence is an *editorial status line*; a real approved message would omit that sentence when sent and retain the approval receipt separately. It does not assert either exposure or no exposure. **Additional professional worked reasoning:** A privacy assessment request should identify the C31/C33 batch ID and 10:49–10:51 gap, the custodian for gateway and queue sources, selection constraints, provenance to obtain and the intended decision. Token-to-contact mapping is separate and requires privacy-owner purpose/permission; no legal hold, notification threshold, exposure or mapping result is supplied. C9X rejects inferring twelve actual people from the token count.