Write a complete corrected customer reply and a complete separate internal handoff for the fictional SUPPORT-01 case below, using only the complete supplied case, policies and records. Repair the whole deliberately wrong pair; do not return just comments, fragments or tone changes. Return: 1. A subject-to-signoff customer reply answering both questions in the latest customer message. Use known facts and completed checks without making the customer repeat information or troubleshooting already supplied. Correct earlier incorrect guidance and give the supplied public help link and an accurately scoped next step. 2. A complete internal handoff stating the customer goals, relevant history, completed observations/actions, applicable policy, actual outstanding stage, known owner and next action, and what remains unset. Preserve the difference between customer reports, agent statements, internal notes and completed action records. Keep internal-only details out of the customer reply. 3. A separate compact internal claim map to the exact supplied records. Do not put that audit map in the customer message. Use the case cutoff and the current policy's stated applicability. The archived macro and the historical exception are supplied to check their relevance, not to turn them into current general rules. Read their scope before using them. Do not infer priority simply from recency or treat another case's completed event as this case's action. A prepared request is not submitted, queued, assigned, approved or completed. Preserve actual completed verification and checks; do not downgrade known facts to unknown just because another stage is pending. Describe the current agent's explicit accepted next action as future work, without claiming to execute it. Do not fabricate a recipient, reviewer, delivery time, new link, permission grant, message send or closure. Link to help/meeting-kit.en.md, whose complete supplied text is H1. Use that public destination instead of inventing a new download or publishing a private guide. The packet contains every policy and record needed for this case. Do not assume an earlier chat, missing attachment, account access or another policy. Everything is an authored ordinary digital-resource teaching example. The wrong pair is not a model trial or another source of facts. Prepare text only: do not browse, contact anyone, send a message, submit an intake request, grant access, create a download, close a case, operate a product or make a real legal, financial or medical decision. The correct pair is not included in this input. === BEGIN COMPLETE CASE AND POLICY PACKET === # SUPPORT-01 — complete fictional case and applicable policy Every service name, person, case record, policy, message, observation, action and 2030 date below is original fiction. “Completed action” means a completed event explicitly supplied inside this invented case; it does not mean the tutorial author used a real system. No real customer information, credentials, account, download, permission or communication is involved. ## C0 — case and material boundary Service: **Paperleaf Library**, which supplies ordinary meeting-template downloads. Customer: **Rae**. Current support agent: **Jordan**. Case reference: **BK-42**. Resource: **Meeting Kit**. Cutoff: **8 September 2030, 14:00 UTC**. All dates and times belong to the fictional case and use UTC. `D-01` and `G-OLD` are safe fixture identifiers for the original download and old guide address. They are not live URLs or redactions of actual customer links. Their relevant states are explicitly recorded below; no hidden URL or file is needed to decide those states. No replacement download address exists in this packet. The complete case material comprises M0–M4 customer-visible correspondence, E0–E3 completed action records, N1–N2 internal notes, the full current policy P2, the archived macro O1, the separate historical exception X1, the supplied public help H1, and the cutoff statement S1. Material types and affected cases must stay separate. No other conversation, policy, approval, event log or attachment is assumed. The approved public help destination is **help/meeting-kit.en.md**. H1 below gives its complete text. The standalone help file must contain that same text. The old internal draft's contents are not supplied or needed; E3 checks its route and access state, not its contents. Do not create a replacement download URL or pretend to have opened one. ## P2 — complete current support policy Policy title: **Meeting Kit access support**. Revision: **2.0**. Effective from **1 September 2030, 00:00 UTC**. Status: current at this case's cutoff. The following P2.1–P2.7 are the whole policy for this exercise, not excerpts from an unseen policy. **P2.1 — Applicability.** This policy applies to all Meeting Kit replacement-link requests received on or after 1 September 2030, including requests concerning a link originally issued before that date. It is the applicable rule for BK-42, opened on 8 September 2030. The archived macro O1 is not applicable to these requests. A separate exception for another case is not a standing rule. **P2.2 — Link life and replacement conditions.** An issued download link is valid for 48 hours from its issue time. Browser-data clearing cannot extend an expired link. Before a replacement is issued, support must verify the original resource request, and a Resource Reviewer must confirm that the current package is suitable for release. A completed verification in the same case can be reused; do not ask the customer to repeat it without a new reason. These are separate prerequisites. Completing verification does not complete the package check or create a replacement link. **P2.3 — Roles and actions.** The case's assigned Support Agent owns the reply and can explain recorded status, share H1 and prepare or submit a Resource Review intake request. Only a Resource Reviewer can complete the package check. Only Fulfilment can create and send the replacement after both prerequisites in P2.2 are complete. A support reply cannot grant file permissions, create a link, assign a reviewer or substitute for an intake submission. An intake draft is not a submitted or queued request. **P2.4 — Timing.** There is no standard one-hour or same-day replacement promise. Report a completion time only if an applicable, approved commitment is actually in this case. The old macro's estimate and another case's turnaround do not establish one. A planned request may be described as a plan, but must not be described as already submitted, approved, assigned, sent or completed. **P2.5 — Guide access.** H1 is the approved public guide and needs no sign-in or access grant. G-OLD points to an internal draft and is not a customer access route. Provide H1 instead of requesting or promising permission to G-OLD. Checking a wrong guide address does not itself change a permission or solve an expired resource link. **P2.6 — Public and internal information.** A customer may be told the link's confirmed expiry, that the wrong guide address was supplied, that the original request has been verified, the applicable replacement conditions, the actual outstanding stage, and an authorized next step. Internal package-note labels, intake routing detail and staff working notes stay in the internal handoff. Do not copy them into the customer reply. Do not ask for information or troubleshooting the customer has already supplied or performed unless a new need is explained. **P2.7 — Case evidence and closure.** Customer reports are reports of the customer's experience; agent statements can contain mistakes; internal plans do not prove execution. Use the completed action records and the explicit cutoff state for claims about what has actually happened. Do not call both issues resolved because a public guide is available; the replacement download is a separate issue. Preparing a reply or handoff does not send either one or close the case. ## O1 — complete archived macro Title: **Quick download reset**. Revision: **1.0**. Archived on 1 September 2030. This is the whole old macro; it is supplied as historical material to identify an error, not as current policy. > Ask the customer to clear browser data and resend the resource reference. Download links do not expire. Replacement links are sent automatically within one hour. Tell the customer the replacement is on its way. ## X1 — complete separate historical exception record Case **BK-09**, 24 August 2030. During a one-off package incident, a team lead explicitly approved Fulfilment issuing that customer's replacement without waiting for a package check. Fulfilment created and sent that link later that day. The approval said **BK-09 only**. It was not a new general policy or an approval for BK-42. This is the complete historical exception supplied; it contains no permission to repeat it in another case. ## M0 — customer-visible delivery message 5 September 2030, 10:00 UTC. Delivery message to Rae: > Your Meeting Kit download reference is D-01. Open the download page and choose Download ZIP while the link is valid. The guide address supplied with this message is G-OLD, labeled Meeting Kit PDF guide. Keep BK-42 as your reference if you need help with this resource. ## E0 — completed original delivery record 5 September 2030, 10:00 UTC. Fulfilment created D-01 and sent M0. The link expiry was set to **7 September 2030, 10:00 UTC**. This records only the original delivery; it does not record a replacement or a later send. BK-42 was the resource reference before it became a support case. ## M1 — first customer support message 8 September 2030, 08:30 UTC. Rae wrote: > My Meeting Kit page now says Link expired. My resource reference is BK-42. Before writing, I tried Chrome, Safari and a private window, and cleared browser data. They all showed the same message. Can you help me download the kit? ## M2 — earlier agent reply, retained as correspondence rather than policy 8 September 2030, 08:45 UTC. Earlier support reply to Rae: > Please clear browser data and send your resource reference. Our links do not expire, and a replacement is automatically sent within one hour. For instructions, use G-OLD, the Meeting Kit PDF guide. This is the complete earlier reply. Its claims are not execution records. N1 identifies the obsolete macro used to write it. ## M3 — customer follow-up 8 September 2030, 09:10 UTC. Rae wrote: > The reference is already in my message: BK-42. I already tried the browser steps. Also, G-OLD opens a permission request instead of the guide. I do not have instructions I can read. Please do not send me through the same browser steps again. ## E1 — completed request verification 8 September 2030, 09:20 UTC. The Support Agent verified that BK-42 is Rae's original Meeting Kit request using the existing case information. Verification succeeded. No new verification information is required from Rae at this point. This did not grant access, approve a package, create a link, submit an intake request or send a replacement. ## E2 — completed link-status check 8 September 2030, 09:30 UTC. The Support Agent checked D-01's recorded status and confirmed that it expired on **7 September 2030, 10:00 UTC**. No link extension or replacement was performed during the check. ## N1 — internal case note 8 September 2030, 10:00 UTC. Internal note: > M2 used archived macro O1. Correct its no-expiry and one-hour statements in the next reply. Internal working label: PKG-INDEX-CHECK. The current Meeting Kit package requires an index check after its packaging revision; a Resource Reviewer must perform that check before Fulfilment issues a replacement. No reviewer has been assigned to BK-42. Do not put this working label or packaging note into the customer reply. X1 is a separate, case-limited historical exception, not authority for skipping this check. This note identifies the required check and the earlier drafting error. It is not a completed check, assignment, approval or submission record. ## E3 — completed guide-route check 8 September 2030, 11:00 UTC. The Support Agent checked the supplied guide reference G-OLD and confirmed that it points to an internal draft requiring permission. The permission prompt is caused by the wrong guide address, not a failed permission on Rae's customer account. No permission was granted or changed. The approved public replacement help text is H1 at **help/meeting-kit.en.md**, which requires no sign-in or access grant. This check did not create or send a resource download. ## M4 — latest customer message: two questions 8 September 2030, 13:40 UTC. Rae wrote: > I still have Link expired on the Meeting Kit download. Can you send me a working replacement link? And can you grant the PDF permission, or give me another way to read the instructions? You already have BK-42, and I already tried the browsers and clearing data. I have not received a new link. ## N2 — current agent's accepted next action, not execution 8 September 2030, 13:45 UTC. Jordan recorded: > I am the assigned Support Agent and own the BK-42 reply. I have read E1–E3 and policy P2. After reviewing the reply draft, I will submit a Resource Review intake request for the current Meeting Kit package, carrying the completed verification and the package-check requirement. I have prepared the request but have not submitted it. Do not say it is queued or assign a reviewer from the role name. I have not received an approved completion time. I will use H1 for the customer's guide question and will not request permission to G-OLD. ## H1 — complete approved public help Destination: **help/meeting-kit.en.md**. The text between BEGIN HELP and END HELP is the whole supplied help page, approved for public use inside this fictional case. BEGIN HELP # Meeting Kit: downloads and the public guide *Public help text for the fictional Paperleaf Library teaching case.* ## Open your download A Meeting Kit download link is valid for 48 hours from its issue time. While the link is valid, open it and choose **Download ZIP**, save the ZIP file, and extract its folder. The kit contains `agenda.docx` and `room-checklist.pdf`. If the page says **Link expired**, clearing browser data or trying another browser will not extend that link. Keep the existing support case open and ask about a replacement there. A replacement requires verification of the original request and a check of the current resource package before a new link can be issued. If support has already verified your request in that case, you do not need to supply the same reference again unless something has changed. There is no self-service button for extending an expired link. A request for a replacement is not confirmation that a new link has been created or sent. Support can explain the current stage; this guide promises no completion time. ## Read the guide without a PDF permission request This is the public Meeting Kit guide. It does not require sign-in or approval to read. An earlier address labeled **Meeting Kit PDF guide** pointed to an internal draft. You do not need access to that draft; use this public guide instead. ## Use the kit after downloading it Open `agenda.docx` to prepare a meeting agenda. Replace the example topic headings with your own topics, add the discussion order, and save a copy for that meeting. Open `room-checklist.pdf` for the setup and end-of-meeting checklist. These instructions do not require the old draft PDF. If the downloaded folder is missing either file, tell support which filename is missing in the existing case. Do not send participant details or upload meeting documents to explain a download problem. END HELP ## S1 — explicit cutoff state 8 September 2030, 14:00 UTC. The supplied case and action record is complete through this cutoff. E0–E3 are completed observations/actions within the fiction. E1 verification is complete, E2 confirms the original link expired, and E3 confirms the wrong guide route and the supplied public help. Jordan is the assigned case owner as stated in N2. The Resource Review request remains a prepared, unsubmitted draft. It is not in an intake queue. No Resource Reviewer is assigned, no package check is complete, no replacement has been approved, created or sent, and no file permission has been changed. No approved completion time exists in this case. M4 is the latest customer message, and no reply to M4 or internal handoff has been sent by the cutoff. The support case remains open. === END COMPLETE CASE AND POLICY PACKET === === BEGIN COMPLETE INTENTIONALLY WRONG PAIR === # SUPPORT-01 — intentionally wrong reply and handoff **Author-designed counterexample, not captured model output.** These are complete deliberately incorrect drafts based on the fictional case. They have not been sent or applied. ## Wrong customer reply Subject: Your Meeting Kit is fixed Hi Rae, Please clear your browser data, try Chrome or a private window, and send us your resource reference so we can verify your request. Our links never expire. As with the earlier BK-09 exception, your replacement is automatic: I have created and emailed it, and it will arrive within one hour. I have also granted you access to G-OLD, so the PDF permission issue is fixed. Your package is now in the PKG-INDEX-CHECK process after a packaging revision, but Casey has completed the review and is taking care of everything. Both issues are resolved and we have closed your case. Thanks, Jordan ## Wrong internal handoff BK-42 — closed, resolved Customer wants a download; no troubleshooting details or resource verification are on file. Ask for the reference and browser information again if they reply. Use O1 as the applicable current policy: no link expiry and automatic one-hour replacement. BK-09 establishes that package checks can be skipped for everyone. Jordan's N2 confirms the request was submitted and queued. Resource Reviewer Casey completed the package check. Fulfilment sent the replacement, and support granted G-OLD access. The response to the customer has been sent. Nothing remains open. No further handoff or action is required. === END COMPLETE INTENTIONALLY WRONG PAIR ===