{
  "description": "Synthetic-only PII benchmark corpus; all names and contact data are fictional or reserved test values.",
  "latency_texts": [
    {
      "length_class": "short",
      "text": "Can synthetic contact Avery Stone call me at (555) 010-1000?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user1@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 2."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Priya Vale call me at (555) 010-1003?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user4@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 5."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Omar Linden call me at (555) 010-1006?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user7@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 8."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Mira Solace call me at (555) 010-1009?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user10@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 11."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Theo North call me at (555) 010-1012?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user13@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 14."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Nadia Frost call me at (555) 010-1015?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user16@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 17."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Jonas Ember call me at (555) 010-1018?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user19@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 20."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Lena Quill call me at (555) 010-1021?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user22@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 23."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Avery Stone call me at (555) 010-1024?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user25@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 26."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Priya Vale call me at (555) 010-1027?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user28@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 29."
    },
    {
      "length_class": "short",
      "text": "Can synthetic contact Omar Linden call me at (555) 010-1030?"
    },
    {
      "length_class": "short",
      "text": "Route this sample note to user31@example.invalid."
    },
    {
      "length_class": "short",
      "text": "No private data here; summarize router health check 32."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Avery Stone can be reached at medium0@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-000."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Mira Solace can be reached at medium1@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-001."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Jonas Ember can be reached at medium2@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-002."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Priya Vale can be reached at medium3@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-003."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Theo North can be reached at medium4@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-004."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Lena Quill can be reached at medium5@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-005."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Omar Linden can be reached at medium6@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-006."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Nadia Frost can be reached at medium7@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-007."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Avery Stone can be reached at medium8@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-008."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Mira Solace can be reached at medium9@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-009."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Jonas Ember can be reached at medium10@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-010."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Priya Vale can be reached at medium11@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-011."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Theo North can be reached at medium12@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-012."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Lena Quill can be reached at medium13@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-013."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Omar Linden can be reached at medium14@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-014."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Nadia Frost can be reached at medium15@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-015."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Avery Stone can be reached at medium16@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-016."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Mira Solace can be reached at medium17@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-017."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Jonas Ember can be reached at medium18@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-018."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Priya Vale can be reached at medium19@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-019."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Theo North can be reached at medium20@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-020."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Lena Quill can be reached at medium21@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-021."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Omar Linden can be reached at medium22@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-022."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Nadia Frost can be reached at medium23@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-023."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Avery Stone can be reached at medium24@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-024."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Mira Solace can be reached at medium25@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-025."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Jonas Ember can be reached at medium26@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-026."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Priya Vale can be reached at medium27@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-027."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Theo North can be reached at medium28@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-028."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Lena Quill can be reached at medium29@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-029."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Omar Linden can be reached at medium30@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-030."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Nadia Frost can be reached at medium31@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-031."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Avery Stone can be reached at medium32@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-032."
    },
    {
      "length_class": "medium",
      "text": "This synthetic support transcript discusses a network appliance validation. Operator asks for interface status, recent packet-loss observations, and a concise action list. No production customer records are used. The fictional requester Mira Solace can be reached at medium33@example.invalid. Please separate confirmed facts from follow-up questions and avoid changing configuration. Additional synthetic context about routing metrics and service health. Additional synthetic context about routing metrics and service health. Case marker M-033."
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Avery Stone, email long0@example.invalid, phone (555) 010-2000. Reference L-000. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Mira Solace, email long1@example.invalid, phone (555) 010-2001. Reference L-001. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Jonas Ember, email long2@example.invalid, phone (555) 010-2002. Reference L-002. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Priya Vale, email long3@example.invalid, phone (555) 010-2003. Reference L-003. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Theo North, email long4@example.invalid, phone (555) 010-2004. Reference L-004. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Lena Quill, email long5@example.invalid, phone (555) 010-2005. Reference L-005. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Omar Linden, email long6@example.invalid, phone (555) 010-2006. Reference L-006. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Nadia Frost, email long7@example.invalid, phone (555) 010-2007. Reference L-007. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Avery Stone, email long8@example.invalid, phone (555) 010-2008. Reference L-008. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Mira Solace, email long9@example.invalid, phone (555) 010-2009. Reference L-009. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Jonas Ember, email long10@example.invalid, phone (555) 010-2010. Reference L-010. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Priya Vale, email long11@example.invalid, phone (555) 010-2011. Reference L-011. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Theo North, email long12@example.invalid, phone (555) 010-2012. Reference L-012. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Lena Quill, email long13@example.invalid, phone (555) 010-2013. Reference L-013. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Omar Linden, email long14@example.invalid, phone (555) 010-2014. Reference L-014. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Nadia Frost, email long15@example.invalid, phone (555) 010-2015. Reference L-015. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Avery Stone, email long16@example.invalid, phone (555) 010-2016. Reference L-016. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Mira Solace, email long17@example.invalid, phone (555) 010-2017. Reference L-017. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Jonas Ember, email long18@example.invalid, phone (555) 010-2018. Reference L-018. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Priya Vale, email long19@example.invalid, phone (555) 010-2019. Reference L-019. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Theo North, email long20@example.invalid, phone (555) 010-2020. Reference L-020. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Lena Quill, email long21@example.invalid, phone (555) 010-2021. Reference L-021. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Omar Linden, email long22@example.invalid, phone (555) 010-2022. Reference L-022. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Nadia Frost, email long23@example.invalid, phone (555) 010-2023. Reference L-023. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Avery Stone, email long24@example.invalid, phone (555) 010-2024. Reference L-024. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Mira Solace, email long25@example.invalid, phone (555) 010-2025. Reference L-025. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Jonas Ember, email long26@example.invalid, phone (555) 010-2026. Reference L-026. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Priya Vale, email long27@example.invalid, phone (555) 010-2027. Reference L-027. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Theo North, email long28@example.invalid, phone (555) 010-2028. Reference L-028. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Lena Quill, email long29@example.invalid, phone (555) 010-2029. Reference L-029. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Omar Linden, email long30@example.invalid, phone (555) 010-2030. Reference L-030. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Nadia Frost, email long31@example.invalid, phone (555) 010-2031. Reference L-031. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    },
    {
      "length_class": "long",
      "text": "Synthetic troubleshooting dialogue: engineer reviews a lab router without touching customer data. The dialogue compares interface counters, route selection, service health, and expected recovery behavior. Each observation is fictional and intended only to measure local detector latency. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. Fictional escalation contact is Avery Stone, email long32@example.invalid, phone (555) 010-2032. Reference L-032. Analyst records that test traffic remained inside the isolated lab, then asks for a structured summary covering symptoms, evidence, possible causes, and safe next checks. No configuration should be saved, no service should be restarted, and every claim should cite the supplied synthetic observation. "
    }
  ],
  "detection_samples": [
    {
      "id": "person-01",
      "text": "Avery Stone drafted the synthetic incident summary after lunch.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Avery Stone"
        }
      ]
    },
    {
      "id": "person-02",
      "text": "Please ask Mira Solace to review the lab-only routing notes.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Mira Solace"
        }
      ]
    },
    {
      "id": "person-03",
      "text": "The fictional account owner is Jonas Ember from the sample team.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Jonas Ember"
        }
      ]
    },
    {
      "id": "person-04",
      "text": "For this test transcript, Priya Vale approved the mock request.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Priya Vale"
        }
      ]
    },
    {
      "id": "person-05",
      "text": "A note says that Theo North will join the fictional meeting.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Theo North"
        }
      ]
    },
    {
      "id": "person-06",
      "text": "Synthetic coordinator Lena Quill filed this example ticket.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Lena Quill"
        }
      ]
    },
    {
      "id": "person-07",
      "text": "The person named in this invented message is Omar Linden.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Omar Linden"
        }
      ]
    },
    {
      "id": "person-08",
      "text": "Escalate this lab exercise to Nadia Frost, not a real contact.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Nadia Frost"
        }
      ]
    },
    {
      "id": "person-09",
      "text": "Yesterday Caspian Reed summarized the made-up outage timeline.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Caspian Reed"
        }
      ]
    },
    {
      "id": "person-10",
      "text": "The fictional reviewer, Elara Voss, requested another chart.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Elara Voss"
        }
      ]
    },
    {
      "id": "person-11",
      "text": "Send the synthetic compliance draft to Mateo Birch for review.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Mateo Birch"
        }
      ]
    },
    {
      "id": "person-12",
      "text": "According to the invented memo, Iris Calder owns the next step.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Iris Calder"
        }
      ]
    },
    {
      "id": "person-13",
      "text": "Could Soren Pike examine this entirely fabricated support case?",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Soren Pike"
        }
      ]
    },
    {
      "id": "person-14",
      "text": "Our sample narrative assigns Amara Wren as incident commander.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Amara Wren"
        }
      ]
    },
    {
      "id": "person-15",
      "text": "In the mock conversation Kellan Moss asks for packet counters.",
      "expected": [
        {
          "entity_type": "PERSON",
          "substring": "Kellan Moss"
        }
      ]
    },
    {
      "id": "email-01",
      "text": "Email the fictional lab result to synthetic.user0@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user0@example.invalid"
        }
      ]
    },
    {
      "id": "email-02",
      "text": "Email the fictional lab result to synthetic.user1@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user1@example.invalid"
        }
      ]
    },
    {
      "id": "email-03",
      "text": "Email the fictional lab result to synthetic.user2@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user2@example.invalid"
        }
      ]
    },
    {
      "id": "email-04",
      "text": "Email the fictional lab result to synthetic.user3@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user3@example.invalid"
        }
      ]
    },
    {
      "id": "email-05",
      "text": "Email the fictional lab result to synthetic.user4@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user4@example.invalid"
        }
      ]
    },
    {
      "id": "email-06",
      "text": "Email the fictional lab result to synthetic.user5@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user5@example.invalid"
        }
      ]
    },
    {
      "id": "email-07",
      "text": "Email the fictional lab result to synthetic.user6@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user6@example.invalid"
        }
      ]
    },
    {
      "id": "email-08",
      "text": "Email the fictional lab result to synthetic.user7@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user7@example.invalid"
        }
      ]
    },
    {
      "id": "email-09",
      "text": "Email the fictional lab result to synthetic.user8@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user8@example.invalid"
        }
      ]
    },
    {
      "id": "email-10",
      "text": "Email the fictional lab result to synthetic.user9@example.invalid after validation.",
      "expected": [
        {
          "entity_type": "EMAIL_ADDRESS",
          "substring": "synthetic.user9@example.invalid"
        }
      ]
    },
    {
      "id": "phone-01",
      "text": "The synthetic callback number in this example is (555) 010-3100.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3100"
        }
      ]
    },
    {
      "id": "phone-02",
      "text": "The synthetic callback number in this example is (555) 010-3101.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3101"
        }
      ]
    },
    {
      "id": "phone-03",
      "text": "The synthetic callback number in this example is (555) 010-3102.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3102"
        }
      ]
    },
    {
      "id": "phone-04",
      "text": "The synthetic callback number in this example is (555) 010-3103.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3103"
        }
      ]
    },
    {
      "id": "phone-05",
      "text": "The synthetic callback number in this example is (555) 010-3104.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3104"
        }
      ]
    },
    {
      "id": "phone-06",
      "text": "The synthetic callback number in this example is (555) 010-3105.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3105"
        }
      ]
    },
    {
      "id": "phone-07",
      "text": "The synthetic callback number in this example is (555) 010-3106.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3106"
        }
      ]
    },
    {
      "id": "phone-08",
      "text": "The synthetic callback number in this example is (555) 010-3107.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3107"
        }
      ]
    },
    {
      "id": "phone-09",
      "text": "The synthetic callback number in this example is (555) 010-3108.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3108"
        }
      ]
    },
    {
      "id": "phone-10",
      "text": "The synthetic callback number in this example is (555) 010-3109.",
      "expected": [
        {
          "entity_type": "PHONE_NUMBER",
          "substring": "(555) 010-3109"
        }
      ]
    },
    {
      "id": "ssn-01",
      "text": "Fictional SSN test value: 123-45-6789; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "123-45-6789"
        }
      ]
    },
    {
      "id": "ssn-02",
      "text": "Fictional SSN test value: 234-56-7890; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "234-56-7890"
        }
      ]
    },
    {
      "id": "ssn-03",
      "text": "Fictional SSN test value: 345-67-8901; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "345-67-8901"
        }
      ]
    },
    {
      "id": "ssn-04",
      "text": "Fictional SSN test value: 456-78-9012; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "456-78-9012"
        }
      ]
    },
    {
      "id": "ssn-05",
      "text": "Fictional SSN test value: 567-89-0123; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "567-89-0123"
        }
      ]
    },
    {
      "id": "ssn-06",
      "text": "Fictional SSN test value: 678-90-1234; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "678-90-1234"
        }
      ]
    },
    {
      "id": "ssn-07",
      "text": "Fictional SSN test value: 321 54 9876; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "321 54 9876"
        }
      ]
    },
    {
      "id": "ssn-08",
      "text": "Fictional SSN test value: 219_09_9999; never use as identity.",
      "expected": [
        {
          "entity_type": "US_SSN",
          "substring": "219_09_9999"
        }
      ]
    },
    {
      "id": "card-01",
      "text": "Payment sandbox card 4111 1111 1111 1111 appears in this synthetic sample.",
      "expected": [
        {
          "entity_type": "CREDIT_CARD",
          "substring": "4111 1111 1111 1111"
        }
      ]
    },
    {
      "id": "card-02",
      "text": "Payment sandbox card 5555 5555 5555 4444 appears in this synthetic sample.",
      "expected": [
        {
          "entity_type": "CREDIT_CARD",
          "substring": "5555 5555 5555 4444"
        }
      ]
    },
    {
      "id": "card-03",
      "text": "Payment sandbox card 378282246310005 appears in this synthetic sample.",
      "expected": [
        {
          "entity_type": "CREDIT_CARD",
          "substring": "378282246310005"
        }
      ]
    },
    {
      "id": "card-04",
      "text": "Payment sandbox card 6011-1111-1111-1117 appears in this synthetic sample.",
      "expected": [
        {
          "entity_type": "CREDIT_CARD",
          "substring": "6011-1111-1111-1117"
        }
      ]
    },
    {
      "id": "card-05",
      "text": "Payment sandbox card 3530 1113 3330 0000 appears in this synthetic sample.",
      "expected": [
        {
          "entity_type": "CREDIT_CARD",
          "substring": "3530 1113 3330 0000"
        }
      ]
    },
    {
      "id": "card-06",
      "text": "Payment sandbox card 4000 0000 0000 0002 appears in this synthetic sample.",
      "expected": [
        {
          "entity_type": "CREDIT_CARD",
          "substring": "4000 0000 0000 0002"
        }
      ]
    },
    {
      "id": "card-07",
      "text": "Payment sandbox card 4242424242424242 appears in this synthetic sample.",
      "expected": [
        {
          "entity_type": "CREDIT_CARD",
          "substring": "4242424242424242"
        }
      ]
    }
  ]
}