{
  "meta": {
    "title": "Amanda Morse Accountability Evidence Atlas",
    "release": "V34 Forensic Evidence Atlas",
    "generated": "2026-08-18T23:59:00-04:00",
    "primaryConductAnchors": 81,
    "masterTimelineEntries": 395,
    "coreDirectExhibits": 16,
    "supplementalDirectExhibits": 8,
    "directExhibitsTotal": 24,
    "nativeMessagesRepresented": 31,
    "categories": 9,
    "evidenceClasses": 6,
    "boundary": "Categories overlap. Counts describe tagged record anchors, not adjudicated violations. The minor is not named and private contact, address, provider-location, and selected health details are omitted."
  },
  "categoryCounts": {
    "child-gatekeeper": 13,
    "communication-restriction": 21,
    "contact-scheduling": 46,
    "disparagement": 6,
    "historical-pattern": 11,
    "implementation": 1,
    "medical-records": 32,
    "school-information": 25,
    "therapy": 20
  },
  "evidenceClassCounts": {
    "Direct communication": 63,
    "Filed or party account": 6,
    "Source-navigation synthesis": 8,
    "Third-party record": 1,
    "Official record": 2,
    "Public notice / advocacy": 1
  },
  "patterns": [
    {
      "number": "01",
      "title": "Logistics request -> child discretion",
      "signal": "Contact logistics were repeatedly returned to the child instead of converted into an adult-confirmed time, platform, or fallback.",
      "sequence": [
        "March 2: contact “at his discretion”",
        "March 4: directed back to the child",
        "March 15: “if he chooses”",
        "April 13: all contact at the child’s discretion"
      ],
      "anchors": [
        "Core Ex. 01",
        "Supp. Ex. 19",
        "Core Ex. 03",
        "Supp. Ex. 22"
      ],
      "limit": "This proves the written operating position. It does not prove why the child did not respond or what level of facilitation the order legally required."
    },
    {
      "number": "02",
      "title": "Condition precedent -> private compliance filter",
      "signal": "In-person contact was stated to be unavailable until Ms. Morse personally saw proof that preconditions had been met.",
      "sequence": [
        "March 9: no visit until proof was seen",
        "July 13: no progression because no proof had been seen"
      ],
      "anchors": [
        "Core Ex. 02",
        "Core Ex. 11"
      ],
      "limit": "The messages do not decide whether the conditions were satisfied or who had authority to decide compliance."
    },
    {
      "number": "03",
      "title": "Scheduled session -> displacement -> “sole gatekeeper”",
      "signal": "A provider-confirmed therapy/contact session was displaced, then adult make-up proposals were answered through child-control language.",
      "sequence": [
        "Session confirmed",
        "Driver-education conflict arose",
        "Direct weekend time or Monday make-up proposed",
        "Timing called irrelevant; child called sole gatekeeper"
      ],
      "anchors": [
        "Event-205",
        "Core Ex. 04",
        "Core Ex. 05"
      ],
      "limit": "Driver education was legitimate. The accountability issue is the adult response to preserving or replacing the lost therapeutic/contact time."
    },
    {
      "number": "04",
      "title": "Specific parent-child request -> child refusal as final answer",
      "signal": "Holiday and ordinary contact requests were answered by reporting the child’s refusal, without a documented adult facilitation plan.",
      "sequence": [
        "June 28 holiday request",
        "Child’s stated refusal supplied",
        "No substitute date documented in the reply"
      ],
      "anchors": [
        "Core Ex. 08",
        "Core Ex. 09"
      ],
      "limit": "The record does not establish how the request was presented or why the child declined."
    },
    {
      "number": "05",
      "title": "Shared access right -> incomplete notice or restrictive interpretation",
      "signal": "Medical and dental participation required follow-up for time, location, portals, records, or a disputed PFA interpretation.",
      "sequence": [
        "Dental concern attributed to possible attendance",
        "Annual physical notice omitted time/location",
        "PFA cited as a bar to attendance",
        "Portal verification mismatch preserved"
      ],
      "anchors": [
        "Core Ex. 07",
        "Supp. Ex. 23",
        "Core Ex. 13",
        "V21-020"
      ],
      "limit": "The records prove the notices and disputes, not motive or the final legal scope of attendance rights."
    },
    {
      "number": "06",
      "title": "Substantive notice -> derision, shutoff, or referral to counsel",
      "signal": "Implementation and child-impact correspondence was repeatedly characterized as ridiculous, rambling, tantrum-like, unread, or unnecessary.",
      "sequence": [
        "“ridiculous emails”",
        "“I really don’t care” about the article / ramblings",
        "“tantrums” / “look in the mirror”",
        "“I don’t read them” / refer to counsel"
      ],
      "anchors": [
        "Core Ex. 01",
        "Core Ex. 10",
        "Core Ex. 14",
        "Supp. Ex. 24"
      ],
      "limit": "The father’s volume and sharp language are part of the same record and must remain visible."
    },
    {
      "number": "07",
      "title": "Underlying conflict -> documentation -> documentation becomes the problem",
      "signal": "As implementation failed, the record grew; the volume of the record then became a separate criticism of the person trying to preserve it.",
      "sequence": [
        "Unresolved contact/access issue",
        "Email and filing made",
        "No immediate operational cure",
        "More preservation work",
        "Volume cited as evidence of the problem"
      ],
      "anchors": [
        "108,080-page corpus metric",
        "July 7 Pierce thread",
        "Supp. Ex. 24",
        "Tyler/eFileMaine record"
      ],
      "limit": "Clinical concern about volume is real and is included. It does not erase the underlying implementation questions."
    }
  ],
  "controlMatrix": [
    {
      "domain": "Electronic contact",
      "orderExpectation": "Reasonable daily contact at reasonable times.",
      "practicalControl": "Availability, device access, response environment, and any recurring time window.",
      "recordSignal": "Repeated requests for a defined time and platform; replies placed contact at the child’s discretion.",
      "openQuestion": "What affirmative adult facilitation, if any, was required when the child did not initiate or respond?"
    },
    {
      "domain": "In-person contact",
      "orderExpectation": "A contingent minimum progression beginning no later than the stated deadline.",
      "practicalControl": "Transportation, proposed dates, adult confirmation, public location, and make-up time.",
      "recordSignal": "Contact conditioned on Ms. Morse seeing proof; later described as solely the child’s decision.",
      "openQuestion": "Who had authority to determine compliance and what was the cure if the parties disagreed?"
    },
    {
      "domain": "Therapy / reunification",
      "orderExpectation": "Regular therapeutic work and a pathway toward relationship repair.",
      "practicalControl": "Scheduling, punctual transportation, full session time, and replacement of displaced sessions.",
      "recordSignal": "A confirmed session was displaced; make-up proposals produced the “sole gatekeeper” exchange.",
      "openQuestion": "Should lost sessions have been automatically replaced, and was individual therapy ever implemented?"
    },
    {
      "domain": "Medical / dental",
      "orderExpectation": "Shared records access and ordinary parental participation except where lawfully limited.",
      "practicalControl": "Appointment notice, time/location, provider listing, portal credentials, authorizations, and on-site logistics.",
      "recordSignal": "Incomplete physical notice, disputed PFA attendance bar, dental concern, and portal mismatch.",
      "openQuestion": "What direct access was actually restored, and what neutral logistics could have protected everyone?"
    },
    {
      "domain": "School information",
      "orderExpectation": "Direct access to school records and important information.",
      "practicalControl": "Parent-portal enrollment, annual update, attendance notice, and direct school communications.",
      "recordSignal": "Repeated requests for direct access and records while attendance/tardiness issues were documented.",
      "openQuestion": "Was each parent independently listed and able to receive notices without the other parent acting as gatekeeper?"
    },
    {
      "domain": "Adult communication",
      "orderExpectation": "Prompt, respectful responses and no disparagement around the child.",
      "practicalControl": "Whether messages are read, answered, routed through counsel, or threatened with PFA reporting.",
      "recordSignal": "Replies included shutoff language, personal insults, and a threatened police/PFA route for ordinary email.",
      "openQuestion": "What narrow communication protocol would preserve necessary co-parenting without recreating an uncontrolled email war?"
    }
  ],
  "gatekeeperSequence": [
    {
      "date": "Mar. 2, 2026",
      "statement": "Contact described as the child’s discretion and comfort level.",
      "source": "Core Ex. 01"
    },
    {
      "date": "Mar. 4, 2026",
      "statement": "A requested daily call time was directed back to the child; original text contains an apparent typo.",
      "source": "Supp. Ex. 19"
    },
    {
      "date": "Mar. 9, 2026",
      "statement": "No in-person visit until Ms. Morse saw proof of compliance.",
      "source": "Core Ex. 02"
    },
    {
      "date": "Mar. 15, 2026",
      "statement": "Father could call or text “if he chooses to speak.”",
      "source": "Core Ex. 03"
    },
    {
      "date": "Apr. 13, 2026",
      "statement": "All electronic or other contact again placed at the child’s discretion.",
      "source": "Supp. Ex. 22"
    },
    {
      "date": "Apr. 23-24, 2026",
      "statement": "The child described as the “sole gatekeeper” of contact and frequency.",
      "source": "Core Ex. 04"
    },
    {
      "date": "Apr. 25, 2026",
      "statement": "In-person contact described as a decision the child could control on his own.",
      "source": "Core Ex. 05"
    },
    {
      "date": "Jun. 28, 2026",
      "statement": "A holiday request answered only with the child’s stated refusal.",
      "source": "Core Ex. 08"
    },
    {
      "date": "Jul. 12, 2026",
      "statement": "Ms. Morse stated she could not force a reply.",
      "source": "Core Ex. 09"
    },
    {
      "date": "Jul. 13, 2026",
      "statement": "No in-person progression because Ms. Morse had seen no proof of compliance.",
      "source": "Core Ex. 11"
    },
    {
      "date": "Aug. 8, 2026",
      "statement": "No affirmative adult role accepted; responsibility and blame returned to the father.",
      "source": "Core Ex. 16"
    }
  ],
  "counterRecord": [
    {
      "title": "Same-day ER update",
      "detail": "On March 31, Ms. Morse sent a substantive medical update while the evaluation was still occurring.",
      "source": "Supp. Ex. 21",
      "why": "Shows useful information sharing sometimes occurred."
    },
    {
      "title": "Number and restrictions answered",
      "detail": "On April 13, the correct contact number and absence of general phone restrictions were confirmed.",
      "source": "Supp. Ex. 22",
      "why": "Shows the same message can contain both cooperation and a disputed gatekeeper position."
    },
    {
      "title": "Provider-facing reschedule request",
      "detail": "On June 11, 2025, Ms. Morse asked the therapist for another Friday time and copied Justin.",
      "source": "Supp. Ex. 18",
      "why": "Cuts against any claim that every schedule change was unilateral obstruction."
    },
    {
      "title": "Categorical denial of exposure",
      "detail": "Ms. Morse denied discussing Justin, emails, or litigation with the child.",
      "source": "Core Ex. 09",
      "why": "The denial is part of the record; credibility cannot be resolved from hostile emails alone."
    },
    {
      "title": "Current clinician cautioned about email volume",
      "detail": "Daniel Pierce expressed concern that the volume and perceived attacks could undermine relationship repair.",
      "source": "July 7 Pierce thread",
      "why": "Adverse clinical context belongs in a credible public record."
    },
    {
      "title": "Justin used pointed language too",
      "detail": "Several threads contain sharp criticism by Justin, including “get the hell out of the way,” “shame on you,” and attacks on reading comprehension.",
      "source": "Core Exs. 14-16",
      "why": "Reciprocal tone context prevents misleading quote selection."
    },
    {
      "title": "Teen autonomy matters",
      "detail": "The child’s age, feelings, independence, and therapeutic safety were legitimate considerations.",
      "source": "Pierce recommendation / order",
      "why": "The accountability claim is about adult implementation, not erasing the child’s voice."
    },
    {
      "title": "Not every allegation is adjudicated",
      "detail": "Many anchors are direct messages, filings, or source-navigation summaries rather than contempt findings.",
      "source": "Evidence-class legend",
      "why": "The page must distinguish transmission, assertion, and official finding."
    }
  ],
  "unresolvedQuestions": [
    "What exact proof was required under paragraphs 1-3, how was it to be delivered, and who had authority to determine sufficiency?",
    "What affirmative adult facilitation does “reasonable daily electronic contact” require when the child does not initiate or respond?",
    "What remedy applies when a scheduled therapy/contact session is displaced by another legitimate activity?",
    "Did the protection order actually prohibit the father’s attendance at the medical appointment, or could neutral noncontact logistics have been used?",
    "Were both parents independently and continuously enrolled in school, medical, dental, insurance, and portal systems?",
    "Was Daniel Pierce’s recommendation for individual therapeutic support implemented, declined, or left unresolved?",
    "What testimony from Glenn Anderson and Daniel Pierce is admissible and relevant to the historical pattern, current barriers, and appropriate support?",
    "What specific, enforceable remedy can still operate before the child ages out of the court’s practical ability to repair the relationship?",
    "How should the court separate legitimate teen autonomy from adult passivity, gatekeeping, or nonimplementation?"
  ],
  "implementationStandard": [
    {
      "title": "One verified contact channel",
      "detail": "Confirm the correct number, platform, and backup method in one written order or protocol."
    },
    {
      "title": "A predictable daily window",
      "detail": "Use a reasonable recurring contact window with a documented fallback when the child is unavailable."
    },
    {
      "title": "Adult-proposed in-person options",
      "detail": "Require adults to offer concrete dates, locations, transportation, and a response deadline without making the child the scheduler."
    },
    {
      "title": "Automatic make-up protection",
      "detail": "Replace therapy or contact displaced by school, work, illness, or driver education within a defined number of days."
    },
    {
      "title": "Direct records and portal access",
      "detail": "List each parent directly with school, medical, dental, insurance, and portal systems; audit changes."
    },
    {
      "title": "No child as messenger or legal interpreter",
      "detail": "Adult disagreements about orders, PFA scope, compliance, or records should stay between adults and the court."
    },
    {
      "title": "Neutral clinical implementation",
      "detail": "Receive Pierce’s current testimony and Anderson’s historical testimony within defined scope; decide individual therapy promptly."
    },
    {
      "title": "One bounded dispute channel",
      "detail": "Use a concise weekly logistics summary for nonurgent issues, immediate notice for emergencies, and a rapid court-review path for deadlock."
    }
  ],
  "supplementalCommunications": [
    {
      "number": 17,
      "date": "June 6, 2025",
      "messageIds": [
        "19747b418d539d45"
      ],
      "threadSubject": "End of school",
      "headline": "Twice-weekly therapy/contact described as unattainable; Friday set as the only continuing schedule",
      "issues": [
        "therapy",
        "contact",
        "schedule constraint"
      ],
      "posture": "mixed",
      "reply": "Per my last email, twice a week would not be attainable at this time. Fridays have been rearranged to accommodate, so keep to that schedule.\n\n-Amanda",
      "context": "The reply followed a request to increase the frequency of reunification sessions after the school year. Work, transportation, and other obligations were part of the surrounding scheduling discussion.",
      "relevance": "Directly records a frequency limitation and a single-day schedule. It does not establish that twice-weekly sessions were clinically ordered, practically possible, or intentionally blocked.",
      "source": "Native Gmail message in the account of Justin Tahai; sender-authenticated metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_17_Twice_weekly_therapy_contact_described_as_unattainable_Friday_set_as_the_only_continu_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_17_Twice_weekly_therapy_contact_described_as_unattainable_Friday_set_as_the_only_continu_PUBLIC.pdf"
    },
    {
      "number": 18,
      "date": "June 11, 2025",
      "messageIds": [
        "19761ae596a53002"
      ],
      "threadSubject": "Appointment 6/13 at 1 p.m.",
      "headline": "A direct, provider-facing request to reschedule a conflict - counter-record showing ordinary coordination",
      "issues": [
        "therapy",
        "schedule",
        "counter-record"
      ],
      "posture": "counter-record",
      "reply": "Hi Dan,\n\nI believe Justin has scheduled an appointment this Friday, 6/13, for 1pm. Unfortunately I just became aware of a scheduling conflict for that time. Do you have any other available time slots on Friday that we may be able to switch it to, providing Justin is also available?\n\nThanks in advance,\nAmanda Morse",
      "context": "Ms. Morse wrote directly to the reunification therapist and copied Justin. The message sought an alternative time rather than simply cancelling the session.",
      "relevance": "This cuts against any claim that every scheduling communication was obstructive. It demonstrates that direct coordination sometimes occurred and belongs in a complete record.",
      "source": "Native Gmail message; sender-authenticated metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_18_A_direct_provider_facing_request_to_reschedule_a_conflict_counter_record_showing_ordi_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_18_A_direct_provider_facing_request_to_reschedule_a_conflict_counter_record_showing_ordi_PUBLIC.pdf"
    },
    {
      "number": 19,
      "date": "March 4, 2026",
      "messageIds": [
        "19cb973d3ad5e9eb"
      ],
      "threadSubject": "Daily Electronic Contact - March 4, 2026",
      "headline": "A daily-contact request was directed back to the child; the original reply contains an apparent typographical error",
      "issues": [
        "contact",
        "child gatekeeper",
        "communication tone"
      ],
      "posture": "adverse",
      "reply": "Text him and ask. I’m my forcing him.\n\n[Apparent typographical error preserved from the native message; the public record does not silently rewrite it.]",
      "context": "The reply followed a request for a confirmed call time between 6:00 and 8:00 p.m. under the February 11 order.",
      "relevance": "Directly records that the logistics request was returned to father-child communication rather than answered with an adult-confirmed time. The apparent typo prevents treating the final clause as unambiguous without the full thread.",
      "source": "Native Gmail message; sender-authenticated metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_19_A_daily_contact_request_was_directed_back_to_the_child_the_original_reply_contains_an_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_19_A_daily_contact_request_was_directed_back_to_the_child_the_original_reply_contains_an_PUBLIC.pdf"
    },
    {
      "number": 20,
      "date": "March 10, 2026",
      "messageIds": [
        "19cd8c88a97e3248"
      ],
      "threadSubject": "Question Regarding the Child",
      "headline": "A request for explanatory information received the two-sentence answer: “He’s mad at you.”",
      "issues": [
        "communication",
        "child narrative",
        "disparagement context"
      ],
      "posture": "adverse",
      "reply": "He’s mad at you.",
      "context": "Justin had asked whether something had happened because the child’s messages appeared distressed and stated that he wanted to respond supportively. Direct quotations from the child are omitted.",
      "relevance": "Proves the terse adult response. It does not prove why the child was angry, what the child had said, or whether more explanation was available elsewhere.",
      "source": "Native Gmail message; sender-authenticated metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_20_A_request_for_explanatory_information_received_the_two_sentence_answer_He_s_mad_at_yo_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_20_A_request_for_explanatory_information_received_the_two_sentence_answer_He_s_mad_at_yo_PUBLIC.pdf"
    },
    {
      "number": 21,
      "date": "March 31, 2026",
      "messageIds": [
        "19d45bf6b3188432"
      ],
      "threadSubject": "ER visit 3/31",
      "headline": "Same-day emergency medical update - counter-record showing substantive information sharing",
      "issues": [
        "medical",
        "records",
        "counter-record"
      ],
      "posture": "counter-record",
      "reply": "[The child] went to the nurse this afternoon with stomach pain. He was sent home early. ... He just got into a room at the ER after a lengthy wait and having his vitals checked. All normal. We’re now waiting to see a medical professional.\n\nThanks,\nAmanda\n\n[Selected minor health details omitted from the public derivative.]",
      "context": "Ms. Morse provided a contemporaneous update concerning a school-nurse visit, walk-in evaluation, and ER routing. Sensitive health details are not reproduced publicly.",
      "relevance": "This is material counter-evidence: it shows that useful medical information was sometimes provided promptly. It does not resolve later disputes about follow-up, portal access, records, or appointment participation.",
      "source": "Native Gmail message; sender-authenticated metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_21_Same_day_emergency_medical_update_counter_record_showing_substantive_information_shar_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_21_Same_day_emergency_medical_update_counter_record_showing_substantive_information_shar_PUBLIC.pdf"
    },
    {
      "number": 22,
      "date": "April 13, 2026, 10:11 p.m. ET",
      "messageIds": [
        "19d89c2a7f951e5c"
      ],
      "threadSubject": "Daily Electronic Contact Under February 11 Order",
      "headline": "The number and absence of phone restrictions were confirmed, but all contact was still placed at the child’s discretion",
      "issues": [
        "contact",
        "child gatekeeper",
        "mixed evidence"
      ],
      "posture": "mixed",
      "reply": "1) His number is [private number omitted]. So if that is the number you have, it is correct.\n\n2) There are no phone restrictions in place other than when he is driving with the instructor.\n\n...\n\n4) Any and all electronic, or otherwise, contact will be at [the child’s] discretion and within his comfort level. ... Respect his boundaries.\n\n-Amanda",
      "context": "The reply answered part of a four-item logistics request. It confirmed the number and stated that no general phone restriction existed, while declining to establish a daily time and again using child-discretion language.",
      "relevance": "Mixed evidence. It documents useful logistical information and the continued disputed implementation position in the same message.",
      "source": "Native Gmail message; sender-authenticated metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_22_The_number_and_absence_of_phone_restrictions_were_confirmed_but_all_contact_was_still_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_22_The_number_and_absence_of_phone_restrictions_were_confirmed_but_all_contact_was_still_PUBLIC.pdf"
    },
    {
      "number": 23,
      "date": "July 27, 2026, 9:33 a.m. ET",
      "messageIds": [
        "19fa3c7da01c8a67"
      ],
      "threadSubject": "FYI",
      "headline": "Annual-physical notice was provided without the time, office, attendance arrangement, or direct-record information",
      "issues": [
        "medical",
        "records",
        "incomplete notice"
      ],
      "posture": "adverse",
      "reply": "[The child] is having his yearly physical scheduled 8/3 with Dr. Vinograd.\nJust fyi",
      "context": "The initial notice identified a date and provider but omitted the appointment time and office. Those details and direct provider access were requested afterward.",
      "relevance": "Directly proves the limited content of the first notice. It does not establish whether the omissions were intentional or whether all details were already available from another source.",
      "source": "Native Gmail message; sender-authenticated metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_23_Annual_physical_notice_was_provided_without_the_time_office_attendance_arrangement_or_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_23_Annual_physical_notice_was_provided_without_the_time_office_attendance_arrangement_or_PUBLIC.pdf"
    },
    {
      "number": 24,
      "date": "July 31, 2026, 9:15 p.m. ET",
      "messageIds": [
        "19fbae3c06cbff86"
      ],
      "threadSubject": "This ends with our generation.",
      "headline": "Ms. Morse said she did not read the messages and redirected them to counsel - with the stated volume preserved",
      "issues": [
        "communication restriction",
        "volume context",
        "public accountability"
      ],
      "posture": "mixed",
      "reply": "Please Stop sending these to me. Seriously. I don’t read them. And they clog up my inbox. Refer them to my attorney and he can forward any deemed necessary. You’ve sent me 15 emails over a 6 hour span of of time. That’s ridiculous.",
      "context": "The reply followed a public-accountability message and stated that fifteen emails had arrived in six hours. The exact volume context is included because omitting it would make the refusal-to-read language misleading.",
      "relevance": "Proves the stated refusal, referral to counsel, and asserted message volume. It does not decide which messages were necessary, whether direct child-related communication could lawfully be refused, or whether the volume was reasonable.",
      "source": "Native Gmail message; sender-authenticated raw MIME and metadata; public-safe derivative.",
      "classification": "supplemental",
      "pdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_24_Ms_Morse_said_she_did_not_read_the_messages_and_redirected_them_to_counsel_with_the_s_PUBLIC.pdf",
      "individualPdf": "downloads/public-record/amanda-morse-direct-communications/Exhibit_24_Ms_Morse_said_she_did_not_read_the_messages_and_redirected_them_to_counsel_with_the_s_PUBLIC.pdf"
    }
  ]
}
