{
  "schema_version": "1.0",
  "status": "reference_assays_not_customer_validated",
  "purpose": "Give humans and AI agents pre-shaped tests for recurring operational workflow failures without pretending a template is a customer case.",
  "canonical_reference_flow": {
    "stages": [
      "request/intake",
      "ownership/assignment",
      "approval/access",
      "execution",
      "completion evidence",
      "closeout/release/payment"
    ],
    "rule": "Map the real workflow to these stages, choose the assay for the failing transition, then test the strongest existing system or process before adding a new layer."
  },
  "assays": [
    {
      "id": "handoff_approval_loop",
      "label": "Handoff and approval loop",
      "canonical_transition": "ownership/assignment -> approval/access",
      "use_when": "Recurring work crosses people, teams or systems and loses time waiting for assignment, approval, access or the next accountable action.",
      "consequence_gate": "Use only when the repeated waiting materially affects time, cost, reliability, customer outcome, risk, cash or operational control.",
      "strongest_baseline_challenge": "Test native assignment, routing, SLA, reminder, escalation and approval capabilities in the current system or process first.",
      "reference_workflows": [
        "maintenance request -> vendor/assignee -> approval/access -> completion evidence -> invoice/closeout",
        "purchase request -> manager/budget approval -> order -> receipt",
        "customer onboarding -> sales handoff -> legal/ops approval -> activation"
      ]
    },
    {
      "id": "exception_rework_loop",
      "label": "Exception and rework loop",
      "canonical_transition": "execution/decision -> exception -> re-entry",
      "use_when": "The same kinds of cases are repeatedly reopened, corrected, chased or routed around normal process.",
      "consequence_gate": "Use only when repeated exceptions or rework create a measurable recurring burden or consequential error risk.",
      "strongest_baseline_challenge": "Test current validation rules, exception queues, required fields, checklists and configured error handling first.",
      "reference_workflows": [
        "invoice exception -> correction -> re-approval -> payment readiness",
        "order exception -> investigation -> correction -> release",
        "service job -> incomplete closeout -> reopen -> corrected evidence -> close"
      ]
    },
    {
      "id": "evidence_closeout_gap",
      "label": "Evidence-to-closeout gap",
      "canonical_transition": "execution/completion -> evidence -> closeout/release/payment",
      "use_when": "Approval, payment, release or closeout depends on evidence that is missing, late, contradictory, version-unclear or hard to trace.",
      "consequence_gate": "Use only when evidence quality changes a real decision, release, payment, compliance position or operational closeout.",
      "strongest_baseline_challenge": "Test current document, work-order and evidence requirements, version controls, mandatory fields and approval rules first.",
      "reference_workflows": [
        "field work completion -> proof/evidence -> supervisor approval -> invoice closeout",
        "inspection -> findings/evidence -> remediation decision -> closeout",
        "change request -> supporting evidence -> approval -> downstream action"
      ]
    },
    {
      "id": "duplicate_entry_reconciliation",
      "label": "Duplicate entry and reconciliation",
      "canonical_transition": "state transfer between systems/stages",
      "use_when": "People repeatedly copy, compare or reconcile the same operational state across multiple systems or files.",
      "consequence_gate": "Use only when duplicated handling creates recurring time, mismatch, correction, release or reporting consequences.",
      "strongest_baseline_challenge": "Test native integration, import/export, synchronization, API and system-of-record options before building a new intermediary.",
      "reference_workflows": [
        "CRM-approved order -> ERP re-entry -> fulfillment status reconciliation",
        "proof of delivery -> invoice reconciliation -> exception handling",
        "spreadsheet status -> operational system update -> reporting reconciliation"
      ]
    },
    {
      "id": "ownership_dispatch_stall",
      "label": "Ownership and dispatch stall",
      "canonical_transition": "request/intake -> ownership/assignment",
      "use_when": "Recurring work enters a queue but accountability, assignment or dispatch is unclear or repeatedly changes.",
      "consequence_gate": "Use only when unclear ownership causes measurable response delay, backlog, missed service, operational risk or customer impact.",
      "strongest_baseline_challenge": "Test current queue assignment, routing rules, on-call or dispatch configuration and escalation logic first.",
      "reference_workflows": [
        "service request -> triage -> assignee/technician -> completion",
        "maintenance alert -> responsible team -> work order -> closeout",
        "customer issue -> queue -> accountable owner -> resolution"
      ]
    }
  ],
  "next_actions": {
    "mcp_tool": "get_workflow_assays",
    "diagnostic_tool": "diagnose_workflow_bottleneck",
    "mcp_endpoint": "https://quietstance.com/mcp",
    "authorized_inquiry_tool": "submit_workflow_inquiry",
    "human_inquiry": "https://quietstance.com/work-with-us"
  },
  "non_claims": [
    "These templates are not customer cases.",
    "They do not prove demand, feasibility, savings, ROI or product-market fit.",
    "A real owner, real recurring instance, usable evidence and measurable consequence are still required before advancing."
  ]
}