#### Day 45 — V9: amend a message without changing the earlier knowledge horizon **Objective.** Create an immutable 11:00 main-case v1 and a distinct 11:20 V9-only v2, with separate approval requests and no invented delivery. Complete [EX045](#exercise-ex045). **Technical teaching.** An authenticated *gateway receipt* may demonstrate an event at some gateway stage, but stage definitions, source time, batch join, content, external acceptance, final recipient delivery and human reading are separate claims. In the **optional V9 branch only**, the 11:20 receipt names mail-sync-04; this may be consistent with C33's narrower internal queue status, because systems can describe different stages, retries or identifiers. The gap at 10:49–10:51 in the canonical inspected gateway remains a source limitation, not an invented event. Do not backdate the receipt to 11:00 or import it into CTN's main case. [NIST SP 800-61 Rev. 3](https://csrc.nist.gov/pubs/sp/800/61/r3/final) supplies the coordinated-response context; [NIST SP 800-84](https://csrc.nist.gov/pubs/sp/800/84/final) supports exercise evaluation. CTN's version protocol is original classroom material. **Worked example — a claim-level version diff.** | Item | v1 / canonical 11:00 | v2 / optional V9 11:20 | |---|---|---| | Supplied evidence | C31 staged, C32 referral, C33 inspected queue not-dispatched and gateway gap | Preserve v1; add the newly authenticated V9 **gateway-stage** receipt | | Defensible claim | External delivery unconfirmed; 12 tokens are not known persons | A gateway-stage record names the batch; event semantics and person delivery still require verification | | Message state | Internal note and learner holding copy: **drafts** | Proposed restricted amendment and communications/privacy review request: **draft**, no send receipt | | Invalid leap | “No other transmission happened” | “All twelve people got a message” or “v1 already knew this” | **Worked v2 excerpt, V9 simulation only:** “CTN-IR-014, internal draft v2, 11:20. Retain v1's 11:00 queue observation and gateway-source gap. V9 newly supplies an authenticated gateway-stage receipt naming mail-sync-04. Validate field semantics, batch join and recipient scope. Neither end-user delivery nor a legal notice determination is established. Privacy and communications owners must review any amended public text. Nothing in this exercise shows a sent notice.” The retained C9X classifier's **EARLY_V9** refuses future evidence at 11:00. **UNAPPROVED_EARLY_V9** flags simulated unapproved sending first; it still independently violates V9's release horizon. These are validation-order illustrations, not records of real messages. **Independent practice.** For [EX045](#exercise-ex045), freeze v1, draft V9-only v2, append a privacy/communications approval request with intended audience and source limits, and keep the 12:00 next-status checkpoint. Treat the learner message as originally unsent. **Artifacts:** version pair, source diff, approval request. **Rubric 0–2:** 2 for distinct source horizons, stage-limited interpretation and unsent status; 1 for accurate v2 without preservation/approval receipt; 0 for rewriting v1, inferring identified recipients or claiming dispatch. Compare [worked answer](#answer-ex045). **Continue studying — Day 45:** [← Day 44](#week-09-day-04) · [Course index](../SUBJECTS.md) · [Chapter 10 legacy teaching (Day 46 not yet written) →](#ch-10) ### Exercise for this lesson **EX045 — Versioned correction.** Variant `V9` supplies a later authenticated gateway receipt for `mail-sync-04` at 11:20, but does not identify recipients; this variant is **not** a main-case C card. Write a version-2 internal note and a message-approval request that correct, rather than erase, the earlier uncertainty. A 2-point result does not backdate the new finding or claim 12 people were affected. ## Worked answers **EX045 — Model V9 revision.** “Internal note v2, 11:20 in the **V9 simulation only**: a newly authenticated gateway receipt names `mail-sync-04`. This conflicts with the earlier `not-dispatched` queue view, which was accurate for its inspected source and time. Validate the receipt's event semantics, batch ID, content and recipient scope before concluding delivery to people. Preserve v1 and the new source; privacy steward owns the reconciled assessment.” The separate approval request asks communications and privacy owners whether the earlier learner-facing draft needs revision, what can now be stated and when to update. The new receipt does not backdate knowledge to 11:00, prove that the 10:49–10:51 gap contained a send, or identify 12 people. **Additional professional worked reasoning:** V9 is an optional 11:20 branch with an authenticated gateway receipt, not main-case C33 evidence. Preserve the original 11:00 message and produce a versioned proposed revision specifying what that gateway receipt proves and what recipient delivery, contact mapping and legal duty remain unknown. Communications and privacy owners separately assess the text; without an actual release receipt the revised note is UNSENT. **Week 9 weekday worked extensions (EX041–EX045).** These are additional explanations; the original five solved answers above remain intact. **Day 41 / EX041.** Correct service evidence is C29 at 10:24/10:26/10:30 and limited C30 owner acceptance at 10:45. Additional monitoring is *assigned*, not finished; recovery time from 09:04 ticket to 10:45 is 101 minutes with no RTO target. Correct data evidence is C31's 10:47 staging and 10:48 release, C32's 10:52 restricted referral and C33's 11:00 selected queue result. The gateway lacks 10:49–10:51; ask for authenticated source coverage/joins, not a global no-dispatch conclusion. Neither identified-person count nor notice duty is supplied. Each row needs its own owner and review condition. **Day 42 / EX042.** The model 100–160-word restricted note is a **draft**, not a delivered notification. Attach a manifest identifying restricted response-group audience, 11:00 cutoff, C30 service evidence versus C31–C33 possible-data evidence, pending release review and a precise proposed batch/gateway query for 10:49–10:51. Ask for source-health, identifier-namespace and custody information through queue/gateway custodians with privacy authorization. No collection receipt or token-to-contact mapping has been supplied. A next action is executable as a request only, not proof of response completion. **Day 43 / EX043.** The original learner-facing copy is limited to the 10:45 service return, continued review, whether any action is required based on that update and the 12:00 status promise. Keep the approval/dispatch record **outside** public prose: service owner pending, communications owner pending, privacy/legal review as applicable, channel proposed, no dispatch receipt, **UNSENT**. C9 prints “C9 internal release=BLOCK” and “C9 learner release=BLOCK”; C9X's sent=True/approved=False row is a contradictory fixture, not a real transport log. A boolean flag cannot substitute for authorization or recipient delivery. **Day 44 / EX044.** Ask exactly five questions: queue status meaning/scope; bounded gateway/dispatcher join and 10:49–10:51 coverage; steward-authorized purpose and minimum scope of mapping (if needed); verified source retention and authorized preservation receipt; and which privacy/legal/contract authorities determine any actual notification or formal hold. Distinguish *assessment open*, *preservation requested*, *copy collected* and *legal order* as separate states. Nothing in C31–C33 supplies a universal 72-hour clock, confirmed human recipients or an authorized bulk export. **Day 45 / EX045.** Preserve v1 as-of 11:00 under canonical C31–C33, including internal not-dispatched entries and the gateway gap. In separate V9 only, add v2 at 11:20 reporting an authenticated **gateway-stage** receipt that names mail-sync-04; verify the receipt's field meaning and batch correlation, and leave human delivery/impact unknown. Submit new privacy/communications review request; no learner-facing dispatch is supplied. EARLY_V9 rejects importing the future variant at 11:00, and UNAPPROVED_EARLY_V9 returns INVALID_SENT_UNAPPROVED for a separate contradictory simulated sent flag without erasing the future-time defect. **C9 draft-release gate — worked laboratory result.** ~~~text C9 internal release=BLOCK C9 learner release=BLOCK ~~~ Both fictional messages remain blocked: one lacks designated approval and the other lacks a reviewable release record. A local Boolean is not an authenticated CTN dispatch log. EX043 must label the learner-facing text as unsent until the relevant owner approves and a separate delivery receipt exists; C33 still cannot prove global nondelivery. **C9X adversarial clarification:** In the revised eight-line rehearsal, the original seven labels remain unchanged. An invented early V9 message with an unapproved `sent=True` flag returns `INVALID_SENT_UNAPPROVED` rather than hiding the execution inconsistency behind `FUTURE_VARIANT`. Independently, V9's actual 11:20 release is unavailable to the 11:00 main-case message. Neither result establishes dispatch or exposure; EX045's v2 remains a separate simulated correction subject to owner approval.