# RR085 complete fictional customer-renewal evidence packet **Teaching status:** `SYNTHETIC / NOT_SENT / NOT_A_CUSTOMER_CASE / NOT_A_PRODUCT_TEST` RR085 demonstrates how seven customer-renewal email structures can be reviewed against frozen records. Redwood Quay Analytics, Northstar Loom Systems, every person, address, agreement, ticket, proposal, amount, and outcome below is fictional. All domains end in `.invalid`. No email-send tool exists in this packet; consequential effects = `0`. ## Case control - Case: `RR085` - Fictional supplier: Northstar Loom Systems (`northstar-loom.invalid`) - Fictional customer: Redwood Quay Analytics Ltd (`redwood-quay.invalid`) - Tenant: `T-RQA-092` - CRM account: `A-RQA-440` - Agreement: `AGR-RQA-2025-07`, version `v4` - Evidence cutoff: `2026-05-20T16:00:00Z` - Fictional renewal date in agreement record: `2026-07-01` - Teaching message class: `UNDECIDED — legal/policy review required per draft` - Candidate sender: Mira Chen, fictional account director, `mira.chen@northstar-loom.invalid` - Customer working contact: Jonah Bell, fictional operations lead, `jonah.bell@redwood-quay.invalid` - Disposition for D01–D07: `NOT_SENT` ## E001–E004 — Stage 1: early planning ### E001 — Account and agreement identity System `CONTRACT-VAULT`, record `AGR-RQA-2025-07/v4`, says Redwood Quay Analytics Ltd is the contracting entity for tenant T-RQA-092. It lists a current term ending 2026-06-30 and a renewal date field of 2026-07-01. The packet does not interpret the renewal or notice clause. ### E002 — Customer-requested planning context CRM note `CRM-881/v2`, recorded 2026-04-29 by Mira Chen, says Jonah Bell requested a renewal working session after the May operating review. The note lists decision criteria to confirm: product scope, service issues, security questionnaire, annual price, and procurement timing. It does not say the customer intends to renew. ### E003 — Contact boundary Contact record `CNT-204/v5` verifies Jonah's address and role as operations lead on 2026-05-02. Authority fields for signature, procurement, legal notice, and billing are `UNKNOWN`. Preferred communication is direct account email; bulk-marketing preference is not relevant to this unclassified draft and remains separately controlled. ### E004 — Stage-1 review instruction Account plan `PLAN-17/v3` authorizes a planning draft and one proposed 30-minute meeting. It forbids pricing, automatic-renewal interpretation, and “commitment” language. Account owner review is required; send permission is not granted. ## E005–E008 — Stage 2: value and usage recap ### E005 — Licensed population Billing-entitlement record `ENT-92/v1` freezes 92 licensed seats for tenant T-RQA-092 during 2026-04-21 through 2026-05-20 UTC. It excludes test users and supplier administrators. ### E006 — Defined activity count Usage record `USE-71/v4` counts 71 distinct licensed seats with at least one governed workflow completion during the same 30-day UTC period. “Active” means only that event definition; it says nothing about quality, frequency, outcome, satisfaction, or causality. ### E007 — Interpretation and customer-confirmation state Analytics note `AN-71/v2` computes `71 / 92 × 100 = 77.1739%`, displayed as 77.17%. The customer-confirmation field is `NOT_CONFIRMED`. No baseline, ROI model, financial benefit, benchmark, or causal attribution is approved. ### E008 — Stage-2 review instruction Data owner Priya Okafor approves reporting both counts, period, definition, and limitation. The account owner may ask Jonah whether this measure is useful. The draft must not call the rate adoption, value, success, engagement quality, or renewal intent. ## E009–E012 — Stage 3: milestone reminder ### E009 — Date fields Agreement record `AGR-RQA-2025-07/v4` contains a renewal date field of 2026-07-01 and a notice-related date field of 2026-06-18. These are source facts only. The packet does not determine which clause applies, how days are counted, or whether email is a permitted notice method. ### E010 — Internal planning interval Operations calculation `CAL-29/v1` measures 29 calendar days from 2026-05-20 to 2026-06-18 for internal workload planning. It is not a legal deadline calculation or timeliness opinion. ### E011 — Conflict check CRM opportunity `OPP-440/v8` previously displayed 2026-06-15 as “renewal close.” Contract operations marked it `NON_CONTROLLING_FORECAST` and corrected no agreement field. A draft must not use June 15 as a contract milestone. ### E012 — Stage-3 review instruction Legal-operations record `LEGAL-HOLD-14/v1` requires qualified review before describing notice, automatic renewal, silence, termination, or service consequence. A factual meeting reminder may be prepared; any notice claim is held. ## E013–E016 — Stage 4: stakeholder confirmation ### E013 — Known role map CRM role record `ROLE-33/v4` lists Jonah Bell as operations lead, Amina Soto as security reviewer, and `UNKNOWN` for procurement, legal, billing, and signature roles. It says the map was last customer-corrected on 2025-08-14 and may be stale. ### E014 — Verified addresses and scope Contact record `CNT-SET-9/v3` verifies Jonah and Amina at `@redwood-quay.invalid`. Jonah may receive account-planning and service-summary information; Amina may receive the security-questionnaire status but not price or unrelated support-user detail. No additional recipient is approved. ### E015 — Enrichment rejection Unapproved enrichment file `EXT-LEADS-2` suggests a finance executive address. Security review marks the source `DO_NOT_USE`; the address was neither supplied nor verified by the customer. It must not appear in a draft or contact map. ### E016 — Stage-4 review instruction The account owner may ask Jonah to name or correct procurement, legal, billing, and signature roles. The message must label them as unknown, not imply Jonah holds those authorities, and avoid copying Amina because no security content is required for this request. ## E017–E020 — Stage 5: open-issue acknowledgment ### E017 — Support issue Support record `SUP-442/v6` says two of 14 scheduled monthly exports in the fictional reporting workflow missed their initial delivery window during May. Both were re-run; root cause is `UNDER_INVESTIGATION`. Support owner Luca Mensah approved the wording “two delayed scheduled exports; both re-run; investigation remains open.” No resolution date is approved. ### E018 — Security questionnaire Security record `SEC-118/v3` says Redwood Quay submitted 38 questions; 31 have approved responses, seven remain with internal owners. Calculation: `38 − 31 = 7`. The next status update is 2026-05-27. This record is not a certification or security assurance. ### E019 — Customer relevance Meeting note `MEET-55/v2` records Jonah's statement that the export investigation and remaining security answers must be visible in the renewal working session. It does not say either issue blocks renewal or that the customer accepts the current status. ### E020 — Stage-5 review instruction Support must approve the SUP-442 sentence; security must approve the SEC-118 sentence; account owner must approve recipient scope. No draft may state cause, resolution, certification, acceptance, or “no impact” beyond these records. ## E021–E024 — Stage 6: proposal follow-up ### E021 — Current annual amount Finance record `FIN-120/v2` lists fictional current annual contracted amount USD 120,000, excluding taxes, for the scope in AGR-RQA-2025-07/v4. It is not a valuation or future price approval. ### E022 — Proposal P-3 Proposal record `PROP-P3/v3` lists USD 126,000, excluding taxes, for 92 seats and the stated service scope, 12-month proposed term, issued 2026-05-19 and expiring 2026-06-10. Status is `PROPOSED / NOT_ACCEPTED / NOT_SIGNED`. Stable fictional link: `https://northstar-loom.invalid/proposals/PROP-P3-v3`. ### E023 — Proposal arithmetic and boundary Finance check `FIN-CALC-5/v1` calculates `126,000 − 120,000 = USD 6,000` and `6,000 / 120,000 × 100 = 5%`. It confirms arithmetic only. It does not approve price, establish fairness, include taxes, prove budget, or authorize negotiation. ### E024 — Stage-6 review instruction Commercial owner Nia Patel approves the exact P-3 summary and may answer questions. Mira may confirm receipt but may not change price, scope, term, credit, tax wording, or expiry. The proposal link must match v3; sending remains unapproved. ## E025–E028 — Stage 7: final next-step check ### E025 — Last customer-stated position Meeting record `MEET-57/v1`, dated 2026-05-20, says Jonah will coordinate the internal role map and prefers the next renewal working session after the May 27 security update. It records no renewal decision or proposal acceptance. ### E026 — Open conditions Account record `COND-4/v2` lists four open conditions: procurement owner unknown, legal contact unknown, SUP-442 investigation open, and seven SEC-118 responses pending. Proposal P-3 is available for review but unaccepted. ### E027 — Follow-up and preference control Communication record `COMM-8/v4` permits one direct follow-up to Jonah after May 27 if no response. Present follow-up count is 0. It forbids adding new recipients or using bulk automation. Any opt-out or channel-change request stops the sequence and routes to the account owner. ### E028 — Stage-7 review instruction The only approved request is to choose a 30-minute meeting time or name the person who should coordinate it. Approved fallback: “If neither time works, we will wait for your preferred time.” The draft may not say last chance, renewal confirmed, service will stop, price will expire beyond the actual P-3 expiry, or silence equals consent. ## D01–D07 — Complete filled email candidates ### D01 — Early planning **Subject:** Planning Redwood Quay's renewal work for July 1 **To:** Jonah Bell `` **Cc:** none **Sources:** E001–E004 **Status:** `NOT_SENT` > Jonah, > > Our current agreement record lists July 1 as the renewal date field. You asked to hold a working session after the May operating review. Could we use 30 minutes to confirm Redwood Quay's decision criteria, stakeholder roles, procurement steps, required evidence, and preferred timeline? > > I will keep pricing and contractual interpretation outside this planning note. The topics currently listed for confirmation are product scope, open service work, the security questionnaire, annual pricing, and procurement timing. Please correct that list if it does not reflect your process. > > Would May 28 at 15:00 UTC or May 29 at 16:00 UTC work? If not, please suggest a preferred time. > > Mira ### D02 — Value and activity recap **Subject:** 30-day activity evidence for Redwood Quay renewal planning **To:** Jonah Bell `` **Cc:** none **Sources:** E005–E008 **Status:** `NOT_SENT` > Jonah, > > For the 30 days ending May 20 UTC, 71 of 92 licensed seats completed at least one governed workflow. That is 77.17% under this narrow definition (`71 ÷ 92`). Test users and supplier administrators are excluded. > > This activity measure does not establish workflow quality, business outcome, satisfaction, ROI, or renewal intent, and Redwood Quay has not confirmed our interpretation. Is this measure useful for your review? If not, please tell us which outcome and period should replace it. > > Mira ### D03 — Milestone reminder **Subject:** Redwood Quay renewal planning milestone — date review required **To:** Jonah Bell `` **Cc:** none **Sources:** E009–E012 **Status:** `NOT_SENT / LEGAL REVIEW REQUIRED` > Jonah, > > Our agreement record contains a June 18 notice-related date and a July 1 renewal-date field. Our CRM also contains a non-controlling June 15 forecast, which we are not treating as an agreement date. > > We are reviewing the governing agreement and approved notice process before making any statement about contractual consequence or required method. For planning only, could you confirm who should coordinate Redwood Quay's agreement review? > > Mira ### D04 — Stakeholder confirmation **Subject:** Confirming Redwood Quay renewal roles and process **To:** Jonah Bell `` **Cc:** none **Sources:** E013–E016 **Status:** `NOT_SENT` > Jonah, > > Our current map lists you as operations lead and Amina Soto as the security-review contact. Procurement, legal, billing, and signature roles are still unknown, and the map was last corrected in August 2025. > > Would you please identify the current people or shared inboxes for those four roles, or tell us which roles are not part of your process? We will not add anyone to renewal communication until their address, purpose, and appropriate information scope are confirmed. > > Mira ### D05 — Open issues **Subject:** Redwood Quay renewal planning — open items as of May 20 UTC **To:** Jonah Bell `` **Cc:** Amina Soto `` **Sources:** E017–E020 **Status:** `NOT_SENT / SUPPORT + SECURITY REVIEW REQUIRED` > Jonah and Amina, > > Two items remain open for the renewal working session: > > - SUP-442: two of 14 scheduled monthly exports missed their initial delivery window in May. Both were re-run; the investigation remains open. No resolution date is approved. > - SEC-118: 31 of 38 questionnaire responses are approved; seven remain with internal owners. The next status update is May 27. > > Jonah asked that both items remain visible. These records do not say either item blocks renewal, and they do not establish customer acceptance, root cause, resolution, or security certification. We will provide the next verified updates from the responsible owners. > > Mira ### D06 — Proposal follow-up **Subject:** Follow-up on Redwood Quay renewal proposal P-3 **To:** Jonah Bell `` **Cc:** none **Sources:** E021–E024 **Status:** `NOT_SENT / COMMERCIAL REVIEW REQUIRED` > Jonah, > > Could you confirm access to proposal P-3, issued May 19? It proposes a 12-month term for 92 seats and the stated service scope at USD 126,000 excluding taxes, and expires June 10. The current annual contracted amount for the compared scope is USD 120,000 excluding taxes; the proposed change is USD 6,000, or 5% (`6,000 ÷ 120,000`). > > P-3 remains proposed, unaccepted, and unsigned. The authoritative version is: https://northstar-loom.invalid/proposals/PROP-P3-v3. Nia Patel is the commercial owner for questions; this email does not change scope, price, term, credits, tax treatment, or expiry. > > Mira ### D07 — Final next-step check **Subject:** Confirming Redwood Quay's next renewal working session **To:** Jonah Bell `` **Cc:** none **Sources:** E025–E028 **Status:** `NOT_SENT` > Jonah, > > You said you would coordinate the role map and preferred our next working session after the May 27 security update. Four conditions remain open in our record: procurement and legal contacts, the SUP-442 investigation, and seven pending SEC-118 answers. Proposal P-3 is available for review but is not accepted. > > Would May 28 at 15:00 UTC or May 29 at 16:00 UTC work for a 30-minute session, or should another person coordinate it? If neither time works, we will wait for your preferred time. > > This is our first permitted direct follow-up. It does not state that renewal is confirmed or that silence is consent. > > Mira ## R01–R07 — Complete review records ### R01 — Early planning review - Sources E001–E004 present and within cutoff: `PASS` - Account/tenant/agreement identity: `PASS` - Price, intent, authority, and clause interpretation invented: `NO` - Recipient verified for planning purpose: `PASS` - Account-owner approval: `REQUIRED / NOT RECORDED` - Disposition: `NOT_SENT` ### R02 — Value recap review - Sources E005–E008 present: `PASS` - Calculation `71 / 92 = 77.17%`: `PASS` - Definition, period, numerator, denominator, exclusions: `PASS` - ROI, adoption quality, causality, satisfaction, or intent claimed: `NO` - Data/account-owner approval: `REQUIRED / PARTIAL` - Disposition: `NOT_SENT` ### R03 — Milestone review - Sources E009–E012 present: `PASS` - June 15 CRM forecast rejected as controlling: `PASS` - 29-day interval used as legal conclusion: `NO` - Contract/notice interpretation: `HELD FOR QUALIFIED REVIEW` - Valid notice asserted: `NO` - Disposition: `NOT_SENT` ### R04 — Stakeholder review - Sources E013–E016 present: `PASS` - Unknown roles remain questions: `PASS` - Unapproved enrichment used: `NO` - Authority inferred from title or copied status: `NO` - Account-owner approval: `REQUIRED / NOT RECORDED` - Disposition: `NOT_SENT` ### R05 — Open-issue review - Sources E017–E020 present: `PASS` - `38 − 31 = 7` pending security answers: `PASS` - Suspected cause, resolution date, certification, or acceptance invented: `NO` - Recipient minimum scope: `NEEDS HUMAN CONFIRMATION` - Support and security approval: `REQUIRED / NOT RECORDED` - Disposition: `NOT_SENT` ### R06 — Proposal review - Sources E021–E024 present: `PASS` - Proposal link/version P-3/v3: `PASS` - `126,000 − 120,000 = 6,000`; `6,000 / 120,000 = 5%`: `PASS` - Proposal represented as accepted/signed: `NO` - Commercial approval and recipient access: `REQUIRED / NOT RECORDED` - Disposition: `NOT_SENT` ### R07 — Final next-step review - Sources E025–E028 present: `PASS` - Open conditions remain visible: `PASS` - Follow-up count 0 before candidate: `PASS` - False urgency, service threat, or silence-as-consent: `NO` - Account-owner send authorization: `NOT RECORDED` - Disposition: `NOT_SENT` ## Packet reconciliation - Evidence records: E001–E028 = 28 unique, contiguous records. - Filled candidate emails: D01–D07 = 7 unique, complete drafts. - Review records: R01–R07 = 7 unique, complete reviews. - Placeholder count in filled drafts: 0. - Synthetic production-block tokens present by design: `.invalid`, `RR085`, `NOT_SENT`. - Email-send tools: 0. - Consequential effects: 0. - Real customer evidence: 0. - OpenMax performance claims: 0. ## Teaching boundary The packet demonstrates traceability and arithmetic, not legal compliance, commercial correctness, customer understanding, deliverability, or product accuracy. Replace every synthetic field with authorized evidence, obtain qualified review, and preserve a separate send authorization before any real use.