[
  {
    "id": "comm-01",
    "title": "Buffer's search-led tutorial production",
    "function": "marketing/content",
    "sector": "Marketing software",
    "source_url": "https://buffer.com/resources/how-to-write-a-blog-post/",
    "source_title": "How to Write a Blog Post: A Full Breakdown of How We Do it at Buffer",
    "accessed_date": "2026-10-18",
    "source_type": "First-person practitioner walkthrough",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "conventional-workflow",
    "summary": "A writer explains how search research becomes a reviewed tutorial and distributed content.",
    "steps": [
      "Select keywords and inspect search intent and competition",
      "Build headings and gather supporting material",
      "Expand the outline with examples and visuals",
      "Proofread, request peer edits, and revise",
      "Preview in Ghost and schedule publication",
      "Adapt key points for social channels and newsletter",
      "Record pageviews and signups"
    ],
    "inputs": [
      "Topic",
      "Search data",
      "Supporting examples"
    ],
    "outputs": [
      "Published tutorial",
      "Channel adaptations",
      "Performance record"
    ],
    "decision_points": [
      "Is the keyword viable?",
      "What unique perspective can the article add?"
    ],
    "quality_checks": [
      "Peer review",
      "CMS preview",
      "SEO-focused posts receive another optimization check"
    ],
    "exceptions": [
      "The writer warns that this public peer-editing arrangement may not suit larger teams"
    ],
    "context_constraints": [
      "Small distributed content team"
    ],
    "structural_motifs": [
      "Evidence assembly",
      "Review gate",
      "Audience-specific derivatives"
    ],
    "candidate_midlevel_pattern": "Evidence-backed explanatory content with independent review",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a training team could turn recurring support questions into reviewed learning guides and channel-specific excerpts.",
    "transfer_limit": "Search-demand evidence does not establish instructional effectiveness.",
    "unknowns": [
      "Measured causal effect of individual steps",
      "Editorial rejection rates"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2024-09-05",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://buffer.com/resources/how-to-write-a-blog-post/",
      "evidence_note": "Article header near title displays Sep 5, 2024. Treated as displayed publication date; no separate update label or original publication history established.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_publication_date"
    },
    "functions": [
      "marketing/content"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P03"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Writer explains the organization’s editorial work; reference supports described steps, not a Buffer-product effectiveness claim.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Measured causal effect of individual steps",
        "Editorial rejection rates",
        "Search-demand evidence does not establish instructional effectiveness."
      ]
    },
    "eligibility_register_id": "comm-01"
  },
  {
    "id": "comm-02",
    "title": "Ahrefs page-by-page content audit",
    "function": "marketing/content",
    "sector": "Search marketing software",
    "source_url": "https://ahrefs.com/blog/content-audit/",
    "source_title": "Follow Our Content Audit Process (Template Included)",
    "accessed_date": "2026-10-18",
    "source_type": "Practitioner method with worked examples",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "The audit diagnoses content performance and identifies appropriate improvements rather than treating every low-traffic page alike.",
    "steps": [
      "Assess business and search potential",
      "Compare actual traffic with plausible potential",
      "Check overlapping pages and distinct purposes",
      "Compare topic coverage and originality",
      "Inspect on-page factors and links",
      "Consider conversion improvements",
      "Record an appropriate action"
    ],
    "inputs": [
      "Existing pages",
      "Traffic and link data",
      "Competing pages"
    ],
    "outputs": [
      "Page-level improvement decisions"
    ],
    "decision_points": [
      "Does this page merit investment?",
      "Is overlap harmful or are pages genuinely distinct?",
      "Is traffic or conversion the remaining opportunity?"
    ],
    "quality_checks": [
      "Use a comparable competitor when the top result is an unbeatable official page",
      "Avoid deletion without confidence"
    ],
    "exceptions": [
      "Necessary pages can remain useful despite weak search performance"
    ],
    "context_constraints": [
      "SEO-oriented audit; estimates are uncertain"
    ],
    "structural_motifs": [
      "Diagnose before acting",
      "Branching remediation",
      "Preserve essential exceptions"
    ],
    "candidate_midlevel_pattern": "Performance-gap diagnosis with conditional remediation",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a knowledge-base owner could distinguish stale, redundant, and essential low-use guidance before revising it.",
    "transfer_limit": "Traffic cannot substitute for mandatory access, compliance, or user usefulness.",
    "unknowns": [
      "General effect sizes",
      "Exact thresholds for each business"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2023-09-15",
      "other_date_type": "displayed_article_date_type_unspecified",
      "evidence_url": "https://ahrefs.com/blog/content-audit/",
      "evidence_note": "Article byline displays September 15, 2023, without specifying whether this is original publication or revision. Preserved as an untyped article date rather than guessing.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_date_type_unspecified"
    },
    "functions": [
      "marketing/content"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P06",
        "P07"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Method author provides a content-audit procedure with worked examples; tool-marketing context is disclosed but no customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "General effect sizes",
        "Exact thresholds for each business",
        "Traffic cannot substitute for mandatory access, compliance, or user usefulness."
      ]
    },
    "eligibility_register_id": "comm-02"
  },
  {
    "id": "comm-03",
    "title": "GOV.UK independent publishing review",
    "function": "marketing/content",
    "sector": "Public administration",
    "source_url": "https://guidance.publishing.service.gov.uk/publish-update-retire-content/standard-content-types/send-standard-review/",
    "source_title": "Send standard content types for review",
    "accessed_date": "2026-10-18",
    "source_type": "Official publishing handbook",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "A draft enters an independent editorial gate with a recorded reason for the change.",
    "steps": [
      "Preview the rendered draft",
      "Record requester and reason in an internal note",
      "Submit for second review",
      "Explicitly send the editor a draft link",
      "Receive publication or rejection outcome",
      "Revise rejected content and resubmit"
    ],
    "inputs": [
      "Draft",
      "Reason for change"
    ],
    "outputs": [
      "Reviewed publication or returned draft"
    ],
    "decision_points": [
      "Publish or reject?"
    ],
    "quality_checks": [
      "Rendered preview",
      "Second editor review"
    ],
    "exceptions": [
      "Submission does not automatically notify a reviewer",
      "Rejected content returns to draft"
    ],
    "context_constraints": [
      "Whitehall Publisher and editor permissions"
    ],
    "structural_motifs": [
      "Two-person gate",
      "Explicit handoff",
      "Rework loop"
    ],
    "candidate_midlevel_pattern": "Independent release review with traceable change rationale",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an operations team could apply this gate to employee-facing process announcements.",
    "transfer_limit": "Reviewer independence and notification behavior must be implemented in the destination system.",
    "unknowns": [
      "Reviewer turnaround time",
      "Review rubric is on a separate page"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://guidance.publishing.service.gov.uk/publish-update-retire-content/standard-content-types/send-standard-review/",
      "evidence_note": "Original publishing-handbook page was reopened; no publication or last-update label appears in retrieved text. Do not borrow dates from the retired GOV.UK URL or crawl time.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "marketing/content"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [],
      "split": "training",
      "fit": "unmapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Reviewer turnaround time",
        "Review rubric is on a separate page",
        "Reviewer independence and notification behavior must be implemented in the destination system."
      ]
    },
    "eligibility_register_id": "comm-03"
  },
  {
    "id": "comm-04",
    "title": "Mailchimp single-variable email experiment",
    "function": "marketing/content",
    "sector": "Email marketing",
    "source_url": "https://mailchimp.com/help/create-ab-tests/",
    "source_title": "Create an A/B Test",
    "accessed_date": "2026-10-18",
    "source_type": "Official product procedure",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "The procedure sends controlled message variants and determines which should reach the remaining audience.",
    "steps": [
      "Choose audience and one variable",
      "Create variations",
      "Choose test allocation, success metric, and duration",
      "Prepare and preview messages",
      "Resolve pre-delivery checklist issues",
      "Send or schedule",
      "Inspect results or apply automatic selection",
      "Send the winner to remaining recipients"
    ],
    "inputs": [
      "Audience",
      "Message variants",
      "Selection criterion"
    ],
    "outputs": [
      "Test results",
      "Selected message"
    ],
    "decision_points": [
      "Automatic or manual winner?",
      "Which metric reflects the changed element?"
    ],
    "quality_checks": [
      "For content tests, use clicks rather than opens",
      "Preview",
      "Allow response time"
    ],
    "exceptions": [
      "Send-time tests use the whole audience",
      "No interactions and ties have documented default selections"
    ],
    "context_constraints": [
      "Tool and plan constraints; small tests may provide weak evidence"
    ],
    "structural_motifs": [
      "Controlled variation",
      "Predeclared selection rule",
      "Staged rollout"
    ],
    "candidate_midlevel_pattern": "Bounded message experiment before broader distribution",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an internal enablement team could test two subject lines with consenting recipients before a larger campaign.",
    "transfer_limit": "Tool-selected winners are not necessarily statistically reliable or causally generalizable.",
    "unknowns": [
      "Sample-specific statistical power",
      "Independent evaluation of defaults"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://mailchimp.com/help/create-ab-tests/",
      "evidence_note": "Original Mailchimp help article was reopened and searched for update labels. No page publication/update date established; dates of linked resources or product changes are not page dates.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "marketing/content"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P09",
        "P03"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Product help documentation establishes how to configure an A/B test; it does not establish that A/B testing improves outcomes in a given context.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Sample-specific statistical power",
        "Independent evaluation of defaults",
        "Tool-selected winners are not necessarily statistically reliable or causally generalizable."
      ]
    },
    "eligibility_register_id": "comm-04"
  },
  {
    "id": "comm-06",
    "title": "Buffer's AI-assisted glossary construction",
    "function": "marketing/content",
    "sector": "Marketing software",
    "source_url": "https://buffer.com/resources/how-we-use-ai-in-content/",
    "source_title": "How Buffer's Content Team Uses AI",
    "accessed_date": "2026-10-18",
    "source_type": "First-party team practice report",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "reported-ai-practice",
    "summary": "The team used a reusable prompt to scaffold glossary entries and then invested in human enrichment.",
    "steps": [
      "Develop a term-outline prompt",
      "Generate basic entry outlines",
      "Use outlines as foundations",
      "Edit entries extensively",
      "Add useful resources"
    ],
    "inputs": [
      "Glossary terms",
      "Prompt"
    ],
    "outputs": [
      "Enriched glossary entries"
    ],
    "decision_points": [
      "Is the page useful enough beyond the initial AI output?"
    ],
    "quality_checks": [
      "Human accuracy review is a team-wide policy",
      "Human editing and added resources"
    ],
    "exceptions": [
      "Team policy rejects AI-only final social posts and unverified AI research"
    ],
    "context_constraints": [
      "Content-team practice as reported in 2024"
    ],
    "structural_motifs": [
      "Repeated schema",
      "Machine scaffold",
      "Human enrichment"
    ],
    "candidate_midlevel_pattern": "Template-driven scaffolding followed by evidence enrichment",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a procurement team could scaffold a supplier-terminology guide, then add verified definitions and examples.",
    "transfer_limit": "Uniform structure does not establish truth; specialized terminology needs authoritative review.",
    "unknowns": [
      "Exact production prompt",
      "Entry-level review evidence",
      "Whether practice changed later"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2024-03-14",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://buffer.com/resources/how-we-use-ai-in-content/",
      "evidence_note": "Article header near title displays Mar 14, 2024. Treated as displayed publication date; no separate update label or original publication history established.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_publication_date"
    },
    "functions": [
      "marketing/content"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P03"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Staff describe glossary outline generation and substantial human enrichment. The glossary tool is not identified as Buffer’s AI; retain only the reported process, not product or time-saving claims.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Exact production prompt",
        "Entry-level review evidence",
        "Whether practice changed later",
        "Uniform structure does not establish truth; specialized terminology needs authoritative review."
      ]
    },
    "eligibility_register_id": "comm-06"
  },
  {
    "id": "comm-07",
    "title": "Basecamp's shaped project pitch",
    "function": "product",
    "sector": "Collaboration software",
    "source_url": "https://basecamp.com/shapeup/1.5-chapter-06",
    "source_title": "Write the Pitch",
    "accessed_date": "2026-10-18",
    "source_type": "First-party operating handbook with actual pitch examples",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "conventional-workflow",
    "summary": "A bounded proposal makes a project discussable without prematurely specifying its final design.",
    "steps": [
      "Explain the problem",
      "State the time appetite",
      "Show the proposed solution with rough annotated visuals",
      "Record hazards and exclusions",
      "Post for asynchronous reading",
      "Collect missing information and challenges before the decision meeting"
    ],
    "inputs": [
      "Shaped idea",
      "Problem evidence",
      "Time appetite"
    ],
    "outputs": [
      "Decision-ready pitch"
    ],
    "decision_points": [
      "What detail is essential to understand the concept?",
      "What is excluded within the appetite?"
    ],
    "quality_checks": [
      "Annotations make rough sketches understandable",
      "Colleagues challenge holes"
    ],
    "exceptions": [
      "Live presentation remains possible when pre-reading fails"
    ],
    "context_constraints": [
      "Decision occurs later at the betting table; pitch comments are not approval"
    ],
    "structural_motifs": [
      "Bounded proposal",
      "Explicit non-goals",
      "Asynchronous critique"
    ],
    "candidate_midlevel_pattern": "Decision-ready proposal with constraints and open design latitude",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a museum could propose a new visitor program using an effort ceiling, visitor problem, rough experience, and exclusions.",
    "transfer_limit": "Roughness is useful only if critical feasibility risks have already been considered.",
    "unknowns": [
      "Pitch rejection rates",
      "Independent outcome measurement"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://basecamp.com/shapeup/1.5-chapter-06",
      "evidence_note": "Original Shape Up chapter was reopened. No chapter publication/update label established. Book publication year cannot be assigned to this living chapter without specific evidence.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "product"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P03",
        "P08"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Operating handbook provides project-pitch practice and examples; not a customer-success story.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Pitch rejection rates",
        "Independent outcome measurement",
        "Roughness is useful only if critical feasibility risks have already been considered."
      ]
    },
    "eligibility_register_id": "comm-07"
  },
  {
    "id": "comm-08",
    "title": "Intercom's RICE prioritization review",
    "function": "product",
    "sector": "Customer communication software",
    "source_url": "https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers",
    "source_title": "RICE: Simple prioritization for product managers",
    "accessed_date": "2026-10-18",
    "source_type": "Original practitioner method",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "conventional-workflow",
    "summary": "Product options are compared using explicit estimates rather than enthusiasm alone.",
    "steps": [
      "Estimate reach over a shared period",
      "Rate impact",
      "Assign confidence",
      "Estimate effort",
      "Calculate reach × impact × confidence / effort",
      "Sort options",
      "Revisit surprising estimates",
      "Document justified deviations"
    ],
    "inputs": [
      "Project options",
      "Reach, impact, confidence, effort estimates"
    ],
    "outputs": [
      "Ranked options",
      "Explicit tradeoffs"
    ],
    "decision_points": [
      "Are estimates credible?",
      "Does a dependency or essential capability override rank?"
    ],
    "quality_checks": [
      "Reconsider implausibly high or low scores"
    ],
    "exceptions": [
      "Dependencies and essential customer requirements can justify out-of-order work"
    ],
    "context_constraints": [
      "Scores depend on estimates and comparable time periods"
    ],
    "structural_motifs": [
      "Comparable evidence",
      "Uncertainty discount",
      "Override rationale"
    ],
    "candidate_midlevel_pattern": "Confidence-adjusted prioritization with explicit exceptions",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a communications team could compare campaign proposals by plausible audience benefit, confidence, and effort.",
    "transfer_limit": "Different objectives or incomparable impacts can make a single ranking misleading.",
    "unknowns": [
      "Calibration accuracy",
      "Measured superiority over alternatives"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2018-01-05",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers",
      "evidence_note": "Author byline displays Sean McBride, 5 January 2018. Recorded as displayed publication date; no separate update date found.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_publication_date"
    },
    "functions": [
      "product"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P07"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Calibration accuracy",
        "Measured superiority over alternatives",
        "Different objectives or incomparable impacts can make a single ranking misleading."
      ]
    },
    "eligibility_register_id": "comm-08"
  },
  {
    "id": "comm-09",
    "title": "GitLab's shared-responsibility issue routing",
    "function": "product",
    "sector": "Developer software",
    "source_url": "https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/",
    "source_title": "Issue Triage",
    "accessed_date": "2026-10-18",
    "source_type": "Public operating handbook",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Cross-cutting issues receive a tentative owner followed by negotiated ownership rather than repeated silent reassignment.",
    "steps": [
      "Understand the issue and request clarification if necessary",
      "Assign the best-fit group",
      "Have that group assess fit and priority",
      "Ask another group to accept ownership when appropriate",
      "Coordinate shared work or justify closure",
      "Escalate unresolved disagreements"
    ],
    "inputs": [
      "Issue report",
      "Ownership categories",
      "Relevant expertise"
    ],
    "outputs": [
      "Owned issue or reasoned closure"
    ],
    "decision_points": [
      "Which group can address it?",
      "Is shared work worth pursuing?",
      "When is escalation needed?"
    ],
    "quality_checks": [
      "Explain reassignment reasoning",
      "Receiving team agrees before relabeling"
    ],
    "exceptions": [
      "Shared-responsibility work may need collaboration",
      "Peers may disagree on value, severity, or ownership"
    ],
    "context_constraints": [
      "Distributed product and engineering ownership"
    ],
    "structural_motifs": [
      "Provisional routing",
      "Negotiated handoff",
      "Escalation path"
    ],
    "candidate_midlevel_pattern": "Ambiguous-request routing with ownership acceptance",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a university service desk could route cross-department inquiries without leaving the requester between teams.",
    "transfer_limit": "Ownership labels alone cannot resolve contested budgets or responsibility.",
    "unknowns": [
      "Resolution-rate improvement",
      "Time spent in disputed ownership"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": "2026-07-31",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/product-development/how-we-work/issue-triage/",
      "evidence_note": "Page footer explicitly says Last modified July 31, 2026 and links commit 5d615813. Original publication not established.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_update_only"
    },
    "functions": [
      "product"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Resolution-rate improvement",
        "Time spent in disputed ownership",
        "Ownership labels alone cannot resolve contested budgets or responsibility."
      ]
    },
    "eligibility_register_id": "comm-09"
  },
  {
    "id": "comm-10",
    "title": "GOV.UK service-retirement transition",
    "function": "product",
    "sector": "Public administration",
    "source_url": "https://www.gov.uk/service-manual/agile-delivery/retiring-your-service",
    "source_title": "Retiring your service",
    "accessed_date": "2026-10-18",
    "source_type": "Official service handbook",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Retirement is planned around continuing user needs and alternate access paths.",
    "steps": [
      "Determine whether and where the need persists",
      "Coordinate with successor teams",
      "Explain changes and next steps to users",
      "Notify API users early",
      "Reach assisted-digital users through their channels",
      "Plan redirects",
      "Maintain information-protection arrangements"
    ],
    "inputs": [
      "Retirement decision",
      "User journeys",
      "Successor-service knowledge"
    ],
    "outputs": [
      "Transition communications",
      "Redirect plan",
      "Information-retention arrangements"
    ],
    "decision_points": [
      "Does the need disappear, move, or cease to be served by government?"
    ],
    "quality_checks": [
      "Account for direct, API, and assisted access"
    ],
    "exceptions": [
      "Some users will still visit the old address",
      "API clients may need substantial lead time"
    ],
    "context_constraints": [
      "Government-service context; data handling follows applicable organizational policy"
    ],
    "structural_motifs": [
      "Continuity planning",
      "Audience-specific transition",
      "Long-tail maintenance"
    ],
    "candidate_midlevel_pattern": "Retiring an offering without abandoning its users",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a software team could retire an internal reporting tool after mapping replacement workflows and notifying every access channel.",
    "transfer_limit": "Legal data duties and mandated-service obligations vary; this is not legal advice.",
    "unknowns": [
      "Actual retirement outcomes",
      "Successor readiness assessment details"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2016-08-04",
      "updated": "2025-08-26",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.gov.uk/service-manual/agile-delivery/retiring-your-service",
      "evidence_note": "Updates to this page explicitly labels Published 4 August 2016 and Last updated 26 August 2025; history confirms first publication.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_explicit_publication_and_update"
    },
    "functions": [
      "product"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P11",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual retirement outcomes",
        "Successor readiness assessment details",
        "Legal data duties and mandated-service obligations vary; this is not legal advice."
      ]
    },
    "eligibility_register_id": "comm-10"
  },
  {
    "id": "comm-12",
    "title": "Product Talk opportunity-to-assumption discovery",
    "function": "product",
    "sector": "Product discovery practice",
    "source_url": "https://www.producttalk.org/2016/08/opportunity-solution-tree/",
    "source_title": "Opportunity Solution Trees: Visualize Your Discovery to Stay Aligned and Drive Outcomes",
    "accessed_date": "2026-10-18",
    "source_type": "Original method author guidance",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "A team links an intended outcome to observed needs, alternative solutions, and tests of their risky assumptions.",
    "steps": [
      "Establish customer hypothesis, outcome, and initial interviews",
      "Map observed opportunities",
      "Select a target opportunity",
      "Generate solutions",
      "Choose three alternatives",
      "Identify and prioritize assumptions",
      "Test risky assumptions across alternatives",
      "Refine, replace, or abandon options"
    ],
    "inputs": [
      "Outcome",
      "Customer interview stories"
    ],
    "outputs": [
      "Opportunity map",
      "Assumption-test evidence",
      "Next decision"
    ],
    "decision_points": [
      "Which opportunity matters?",
      "Which assumption is riskiest?",
      "Refine, generate new options, or switch opportunity?"
    ],
    "quality_checks": [
      "Do not invent opportunities without interviews",
      "Keep revising the map as interviews continue"
    ],
    "exceptions": [
      "Evidence may justify abandoning an entire target opportunity"
    ],
    "context_constraints": [
      "Continuous discovery; several initial interviews are prerequisites, not a sufficient final sample"
    ],
    "structural_motifs": [
      "Outcome-to-evidence chain",
      "Compare alternatives",
      "Falsification loop"
    ],
    "candidate_midlevel_pattern": "Comparative assumption testing before committing to a solution",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a library could compare approaches to reducing catalogue-search frustration by testing their distinct assumptions.",
    "transfer_limit": "Qualitative discovery does not by itself estimate population prevalence or prove business impact.",
    "unknowns": [
      "Observed outcomes in a specific implementation",
      "Test-selection details"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2023-12-06",
      "other_date_type": "displayed_article_date_type_unspecified",
      "evidence_url": "https://www.producttalk.org/opportunity-solution-trees/",
      "evidence_note": "Requested /2016/08/opportunity-solution-tree/ URL redirects to /opportunity-solution-trees/. Current article header shows 06 Dec 2023; it does not label this as original publication or revision. URL-embedded 2016 is not used as date evidence.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_date_type_unspecified"
    },
    "functions": [
      "product"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P01",
        "P07",
        "P09"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Observed outcomes in a specific implementation",
        "Test-selection details",
        "Qualitative discovery does not by itself estimate population prevalence or prove business impact."
      ]
    },
    "eligibility_register_id": "comm-12"
  },
  {
    "id": "comm-13",
    "title": "GDS collaborative research analysis",
    "function": "design/research",
    "sector": "Public administration",
    "source_url": "https://www.gov.uk/service-manual/user-research/analyse-a-research-session",
    "source_title": "Analyse a research session",
    "accessed_date": "2026-10-18",
    "source_type": "Official research handbook",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Researchers and observers separate observations, interpretations, and actions while building shared findings.",
    "steps": [
      "Bring observers together soon after research",
      "Extract one observed event or statement per note",
      "Check recordings where needed",
      "Cluster related observations",
      "Name and refine groups",
      "Record findings separately",
      "Agree actions",
      "Share the results"
    ],
    "inputs": [
      "Session notes",
      "Recordings",
      "Observer recollections"
    ],
    "outputs": [
      "Grouped evidence",
      "Findings",
      "Proposed actions"
    ],
    "decision_points": [
      "What do observations jointly imply?",
      "What should change or be researched next?"
    ],
    "quality_checks": [
      "Capture what happened before interpreting",
      "Use separate note colors for findings and actions"
    ],
    "exceptions": [
      "Capturing useful sticky notes during sessions is recommended only for experienced lab teams"
    ],
    "context_constraints": [
      "Collaborative analysis; guidance suggests one hour per two hours of research"
    ],
    "structural_motifs": [
      "Evidence/interpretation separation",
      "Inductive grouping",
      "Action derivation"
    ],
    "candidate_midlevel_pattern": "Traceable synthesis from observations to decisions",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an operations team could synthesize service-desk observations while preserving which statements are facts versus interpretations.",
    "transfer_limit": "Discarding isolated observations can hide rare but important failures; the transfer needs explicit minority-evidence handling.",
    "unknowns": [
      "Inter-rater agreement",
      "Treatment of contradictory observations",
      "Downstream implementation rate"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2016-05-24",
      "updated": "2016-05-24",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.gov.uk/service-manual/user-research/analyse-a-research-session",
      "evidence_note": "Updates to this page explicitly labels both publication and last update 24 May 2016; first-publication history matches.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_explicit_publication_and_update"
    },
    "functions": [
      "design/research"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Inter-rater agreement",
        "Treatment of contradictory observations",
        "Downstream implementation rate",
        "Discarding isolated observations can hide rare but important failures; the transfer needs explicit minority-evidence handling."
      ]
    },
    "eligibility_register_id": "comm-13"
  },
  {
    "id": "comm-14",
    "title": "GDS moderated usability session",
    "function": "design/research",
    "sector": "Public administration",
    "source_url": "https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing",
    "source_title": "Using moderated usability testing",
    "accessed_date": "2026-10-18",
    "source_type": "Official research handbook",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "A moderator observes users attempting realistic tasks without revealing the intended path.",
    "steps": [
      "Agree questions, users, and service scope",
      "Prepare accessible sessions and note-taking",
      "Design realistic tasks without answer clues",
      "Pilot the discussion guide",
      "Introduce the session and tasks neutrally",
      "Observe and invite thinking aloud",
      "Clarify uncertainty and ask closing questions",
      "Secure research material"
    ],
    "inputs": [
      "Research questions",
      "Service or prototype",
      "Task guide"
    ],
    "outputs": [
      "Task observations",
      "Usability issues"
    ],
    "decision_points": [
      "Which tasks fit the participant?",
      "When should a stuck participant receive help?"
    ],
    "quality_checks": [
      "Pilot instructions",
      "Consistent task delivery",
      "Neutral prompts"
    ],
    "exceptions": [
      "Dummy data is an option where real-data use is unsuitable",
      "Assistive-technology users may need their own setup"
    ],
    "context_constraints": [
      "Method requires actual or likely users; personal-data safeguards apply"
    ],
    "structural_motifs": [
      "Observed behavior",
      "Controlled elicitation",
      "Moderator restraint"
    ],
    "candidate_midlevel_pattern": "Task-based observation to expose usability failures",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a logistics team could test whether a new dispatch checklist is understandable using fictional orders.",
    "transfer_limit": "Artificial tasks and dummy data may miss real contextual problems.",
    "unknowns": [
      "Task-specific success thresholds",
      "Results from any particular service"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2017-02-21",
      "updated": "2017-10-03",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing",
      "evidence_note": "Updates to this page explicitly labels Published 21 February 2017 and Last updated 3 October 2017; update history explains the change.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_explicit_publication_and_update"
    },
    "functions": [
      "design/research"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P01",
        "P09"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Task-specific success thresholds",
        "Results from any particular service",
        "Artificial tasks and dummy data may miss real contextual problems."
      ]
    },
    "eligibility_register_id": "comm-14"
  },
  {
    "id": "comm-15",
    "title": "IDEO.org field-learning download",
    "function": "design/research",
    "sector": "Social innovation and nonprofit design",
    "source_url": "https://www.designkit.org/methods/download-your-learnings.html",
    "source_title": "Download Your Learnings",
    "accessed_date": "2026-10-18",
    "source_type": "Original organization method guide",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Team members externalize fresh field experiences so individual knowledge becomes shared material.",
    "steps": [
      "Remove distractions and take turns",
      "Put key facts, experiences, and impressions on notes",
      "Tell the associated stories",
      "Cluster notes as the discussion proceeds",
      "Ask clarifying questions"
    ],
    "inputs": [
      "Field notes",
      "Photos",
      "Quotes",
      "Impressions"
    ],
    "outputs": [
      "Shared record of learning"
    ],
    "decision_points": [
      "What needs clarification before the team moves on?"
    ],
    "quality_checks": [
      "Listen attentively",
      "Download while experiences remain fresh"
    ],
    "exceptions": [
      "No exception route specified"
    ],
    "context_constraints": [
      "Team method, preferably on the same day as fieldwork"
    ],
    "structural_motifs": [
      "Memory externalization",
      "Collective sense-making",
      "Clarification"
    ],
    "candidate_midlevel_pattern": "Immediate debrief that converts individual observations into shared evidence",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an exhibition team could combine separate venue visits into a shared planning record.",
    "transfer_limit": "Impressions must remain distinguishable from observations if the output will support consequential decisions.",
    "unknowns": [
      "Formal validation rules",
      "Later synthesis and decision procedure"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.designkit.org/methods/download-your-learnings.html",
      "evidence_note": "Original Design Kit method page reopened. No publication/update label established in retrieved text.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "design/research"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P01"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Formal validation rules",
        "Later synthesis and decision procedure",
        "Impressions must remain distinguishable from observations if the output will support consequential decisions."
      ]
    },
    "eligibility_register_id": "comm-15"
  },
  {
    "id": "comm-16",
    "title": "NN/g open card sorting",
    "function": "design/research",
    "sector": "UX research practice",
    "source_url": "https://www.nngroup.com/articles/card-sorting-definition/",
    "source_title": "Card Sorting: Uncover Users' Mental Models",
    "accessed_date": "2026-10-18",
    "source_type": "Expert-authored method procedure",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Participants group content items to reveal how they organize a domain.",
    "steps": [
      "Prepare understandable content cards",
      "Pilot the set",
      "Recruit appropriate participants",
      "Explain sorting rules",
      "Let participants group cards and explain choices",
      "Name groups after forming them",
      "Compare patterns"
    ],
    "inputs": [
      "Content labels",
      "Participant explanations"
    ],
    "outputs": [
      "Groupings",
      "Candidate category labels"
    ],
    "decision_points": [
      "Open, closed, or hybrid approach?",
      "Qualitative reasoning or quantitative grouping evidence?"
    ],
    "quality_checks": [
      "Avoid shared wording that mechanically cues grouping",
      "Pilot clarity"
    ],
    "exceptions": [
      "Unknown cards can remain aside",
      "Participants may revise groups"
    ],
    "context_constraints": [
      "Card sorting explores mental organization; guide prefers tree testing for validating navigation"
    ],
    "structural_motifs": [
      "User-generated categories",
      "Delayed labeling",
      "Ambiguity preservation"
    ],
    "candidate_midlevel_pattern": "Discovering a usable taxonomy from participant grouping",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a support team could learn how customers group help topics before redesigning a help centre.",
    "transfer_limit": "A plausible taxonomy is not proof that users can find items within a finished navigation interface.",
    "unknowns": [
      "Specific dataset and resulting taxonomy",
      "Implementation effects"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2024-02-02",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.nngroup.com/articles/card-sorting-definition/",
      "evidence_note": "Author/title block displays February 2, 2024 and 2024-02-02. Recorded as displayed publication date; no separate update date found.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_publication_date"
    },
    "functions": [
      "design/research"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P01"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Specific dataset and resulting taxonomy",
        "Implementation effects",
        "A plausible taxonomy is not proof that users can find items within a finished navigation interface."
      ]
    },
    "eligibility_register_id": "comm-16"
  },
  {
    "id": "comm-17",
    "title": "IBM user-journey playback",
    "function": "design/research",
    "sector": "Enterprise technology",
    "source_url": "https://www.ibm.com/training/enterprise-design-thinking/framework",
    "source_title": "Enterprise Design Thinking Framework",
    "accessed_date": "2026-10-18",
    "source_type": "Original organization framework and procedure",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Stakeholders review an end-to-end user story rather than disconnected feature progress.",
    "steps": [
      "Invite affected stakeholders",
      "Tell the user's experience through the solution",
      "Capture feedback without judgment",
      "Identify misalignment",
      "Iterate and replay as needed",
      "At delivery milestones review the working experience",
      "Discuss readiness to release"
    ],
    "inputs": [
      "User outcomes",
      "Prototype or working solution"
    ],
    "outputs": [
      "Feedback",
      "Alignment or identified gaps"
    ],
    "decision_points": [
      "Do stakeholders agree on the intended outcome and proposed experience?",
      "Is the solution ready?"
    ],
    "quality_checks": [
      "Review the complete journey",
      "Give participants a voice"
    ],
    "exceptions": [
      "Disagreement triggers another iteration",
      "Confidential client playbacks require suitable agreements"
    ],
    "context_constraints": [
      "Different milestones use different fidelity; sponsor users do not replace formal research"
    ],
    "structural_motifs": [
      "Experience-centered review",
      "Milestone gate",
      "Misalignment loop"
    ],
    "candidate_midlevel_pattern": "End-to-end experience review before commitment or release",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a visitor-services team could walk partners through an entire arrival-to-exit journey before opening a new venue.",
    "transfer_limit": "A compelling story can conceal operational faults unless reviewers inspect realistic evidence.",
    "unknowns": [
      "Formal acceptance thresholds",
      "Observed release outcomes"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.ibm.com/training/enterprise-design-thinking/framework",
      "evidence_note": "Original IBM framework page reopened. No page publication/update label established; dates from separate downloadable toolkit assets are not assigned to this page.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "design/research"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P01"
      ],
      "split": "held-out",
      "fit": "qualified",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Formal acceptance thresholds",
        "Observed release outcomes",
        "A compelling story can conceal operational faults unless reviewers inspect realistic evidence."
      ]
    },
    "eligibility_register_id": "comm-17"
  },
  {
    "id": "comm-19",
    "title": "Atlassian DACI decision record",
    "function": "leadership/strategy",
    "sector": "Cross-functional team management",
    "source_url": "https://www.atlassian.com/team-playbook/plays/daci",
    "source_title": "DACI Decision-Making Framework",
    "accessed_date": "2026-10-18",
    "source_type": "Official facilitation procedure",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "A decision has an explicit coordinator, decision-maker, contributors, and affected audience.",
    "steps": [
      "Create a question-centered shared document",
      "Assign a driver and one approver",
      "Identify contributors and informed parties",
      "Record context, evidence, criteria, and options",
      "Gather input",
      "Assign remaining information tasks",
      "Have the approver decide",
      "Record and share the outcome"
    ],
    "inputs": [
      "Decision question",
      "Evidence",
      "Options and constraints"
    ],
    "outputs": [
      "Decision and rationale",
      "Follow-up tasks"
    ],
    "decision_points": [
      "Who has authority?",
      "What information is still missing?",
      "Which option should be chosen?"
    ],
    "quality_checks": [
      "Separate contributor input from final authority",
      "Record reasons for future reference"
    ],
    "exceptions": [
      "Contributors can be consulted together or individually"
    ],
    "context_constraints": [
      "Requires a person with legitimate decision authority"
    ],
    "structural_motifs": [
      "Role separation",
      "Evidence assembly",
      "Decision provenance"
    ],
    "candidate_midlevel_pattern": "Accountable decision-making with a reusable rationale",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a festival team could select a venue using a named decider, explicit criteria, and a record of rejected alternatives.",
    "transfer_limit": "Assigning roles cannot create authority absent from the organization.",
    "unknowns": [
      "Whether listed benefits hold in practice",
      "Escalation when approver is unavailable"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.atlassian.com/team-playbook/plays/daci",
      "evidence_note": "Original DACI play reopened. No publication/update label established. Footer copyright 2025 is not a publication date.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "leadership/strategy",
      "administration/project coordination"
    ],
    "aliases": [
      "svc-21"
    ],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P07",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Whether listed benefits hold in practice",
        "Escalation when approver is unavailable",
        "Assigning roles cannot create authority absent from the organization."
      ]
    },
    "eligibility_register_id": "comm-19"
  },
  {
    "id": "comm-20",
    "title": "Atlassian project premortem",
    "function": "leadership/strategy",
    "sector": "Cross-functional project management",
    "source_url": "https://www.atlassian.com/team-playbook/plays/pre-mortem",
    "source_title": "Pre-mortem project management strategy",
    "accessed_date": "2026-10-18",
    "source_type": "Official facilitation procedure with illustrated team examples",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Participants anticipate project threats and enabling conditions, then convert selected concerns into commitments.",
    "steps": [
      "Prepare project-specific prompts",
      "Silently generate possible failures and successes",
      "Group similar contributions",
      "Vote on threats",
      "Vote on success factors",
      "Discuss leading topics and mitigations",
      "Assign owners and dates",
      "Save and recap commitments"
    ],
    "inputs": [
      "Project context",
      "Participant concerns",
      "Past lessons"
    ],
    "outputs": [
      "Prioritized risks",
      "Mitigation actions"
    ],
    "decision_points": [
      "Which issues deserve limited discussion time?",
      "What action mitigates each risk?"
    ],
    "quality_checks": [
      "Quantify time or cost where available",
      "Every commitment gets an owner and deadline"
    ],
    "exceptions": [
      "Prompts can be customized",
      "Remote and in-person variants"
    ],
    "context_constraints": [
      "Small-group workshop before or during a project"
    ],
    "structural_motifs": [
      "Independent generation",
      "Group prioritization",
      "Owned mitigation"
    ],
    "candidate_midlevel_pattern": "Prospective failure analysis converted into accountable actions",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a publishing team could anticipate why an issue might miss its release date and assign early safeguards.",
    "transfer_limit": "Voting reflects the group's knowledge, not calibrated risk probability; rare severe risks can be outvoted.",
    "unknowns": [
      "Mitigation follow-through",
      "Measured predictive accuracy"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.atlassian.com/team-playbook/plays/pre-mortem",
      "evidence_note": "Original premortem play reopened. No publication/update label established; timing estimates refer to the workshop, not publication.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "leadership/strategy"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P08",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Mitigation follow-through",
        "Measured predictive accuracy",
        "Voting reflects the group's knowledge, not calibrated risk probability; rare severe risks can be outvoted."
      ]
    },
    "eligibility_register_id": "comm-20"
  },
  {
    "id": "comm-21",
    "title": "Nesta theory-of-change construction",
    "function": "leadership/strategy",
    "sector": "Social innovation",
    "source_url": "https://www.nesta.org.uk/toolkit/theory-change/",
    "source_title": "Understanding the theory of change model",
    "accessed_date": "2026-10-18",
    "source_type": "Original foundation toolkit",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "A team articulates how activities are expected to produce a desired change.",
    "steps": [
      "Describe the problem and audience",
      "Identify an engagement entry point",
      "Sequence practical activities",
      "State measurable near-term effects",
      "Connect effects to wider benefits and long-term goals",
      "Expose assumptions behind the links"
    ],
    "inputs": [
      "Problem context",
      "Intended audience",
      "Long-term goal"
    ],
    "outputs": [
      "Explicit change model"
    ],
    "decision_points": [
      "How will the audience be reached?",
      "Why should these activities lead to these outcomes?"
    ],
    "quality_checks": [
      "Make effects specific and evidence-based",
      "Surface assumptions for testing"
    ],
    "exceptions": [
      "No explicit exception branch described"
    ],
    "context_constraints": [
      "Charity, public-service, and innovation planning"
    ],
    "structural_motifs": [
      "Causal hypothesis",
      "Backward/forward linkage",
      "Assumption visibility"
    ],
    "candidate_midlevel_pattern": "Making an intervention's causal logic inspectable",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a training team could map learning activities to observable behavior changes before measuring impact.",
    "transfer_limit": "The model is a hypothesis, not evidence that activities caused results.",
    "unknowns": [
      "Source-specific implementation outcomes",
      "Detailed falsification procedure"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.nesta.org.uk/toolkit/theory-change/",
      "evidence_note": "Original Nesta toolkit page reopened and checked for date labels. No publication/update date established; footer copyright year is excluded.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "not_stated_in_retrieved_page"
    },
    "functions": [
      "leadership/strategy"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [],
      "split": "training",
      "fit": "unmapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Source-specific implementation outcomes",
        "Detailed falsification procedure",
        "The model is a hypothesis, not evidence that activities caused results."
      ]
    },
    "eligibility_register_id": "comm-21"
  },
  {
    "id": "comm-22",
    "title": "Outcome Harvesting for strategic learning",
    "function": "leadership/strategy",
    "sector": "Program evaluation and international development",
    "source_url": "https://www.betterevaluation.org/methods-approaches/approaches/outcome-harvesting",
    "source_title": "Outcome harvesting",
    "accessed_date": "2026-10-18",
    "source_type": "Method-developer-contributed evaluation guide",
    "evidence_status": "documented-procedure",
    "workflow_mode": "conventional-workflow",
    "summary": "Evaluators work backwards from observed changes to investigate plausible program contributions.",
    "steps": [
      "Agree intended uses and questions",
      "Review documents and draft outcome descriptions",
      "Engage knowledgeable informants to correct and extend descriptions",
      "Independently substantiate selected outcomes",
      "Classify and interpret the evidence",
      "Discuss use with intended users"
    ],
    "inputs": [
      "Documents",
      "Reported changes",
      "Informant accounts"
    ],
    "outputs": [
      "Substantiated outcome descriptions",
      "Evidence-based answers"
    ],
    "decision_points": [
      "What is useful to learn?",
      "Which outcomes require independent checking?",
      "How credible is the contribution?"
    ],
    "quality_checks": [
      "Observable changes",
      "Independent knowledgeable sources",
      "Open questions beyond planned outcomes"
    ],
    "exceptions": [
      "Emergent and unintended outcomes are included",
      "Sampling varies with the harvest"
    ],
    "context_constraints": [
      "Participatory and context-adapted method; contribution is investigated rather than assumed"
    ],
    "structural_motifs": [
      "Backward causal inquiry",
      "Independent substantiation",
      "Use-oriented synthesis"
    ],
    "candidate_midlevel_pattern": "Outcome-first investigation with contribution checks",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an ecosystem partnership team could investigate unexpected changes in partner behavior and assess its own plausible contribution.",
    "transfer_limit": "This is not experimental causal identification; competing explanations must remain visible.",
    "unknowns": [
      "Application-specific sampling",
      "Strength of causal inference in a particular harvest"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.betterevaluation.org/methods-approaches/approaches/outcome-harvesting",
      "evidence_note": "Direct original-page opens returned an internal retrieval error in this pass; search returned original-page text but no page publication/update label. Dates 2012 and 2013 describe a cited external guide, not this page. Date remains unavailable.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "unavailable_retrieval_limited"
    },
    "functions": [
      "leadership/strategy"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P05"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Application-specific sampling",
        "Strength of causal inference in a particular harvest",
        "This is not experimental causal identification; competing explanations must remain visible."
      ]
    },
    "eligibility_register_id": "comm-22"
  },
  {
    "id": "comm-23",
    "title": "Zapier's AI proposal pressure-test",
    "function": "leadership/strategy",
    "sector": "Workflow automation software",
    "source_url": "https://www.chatprd.ai/how-i-ai/ea-ai-workflows-for-meetings-culture-and-strategy",
    "source_title": "How I AI: Zapier EA Cortney Hickey's 4 AI Workflows for Meeting Prep, Culture Reinforcement, and Strategy",
    "accessed_date": "2026-10-18",
    "source_type": "Original interview and published demonstration walkthrough",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "reported-ai-practice",
    "summary": "An executive assistant's custom GPT gives proposal authors a first review.",
    "steps": [
      "Supply strategy, strong examples, and decision norms",
      "Submit a draft",
      "Flag gaps and tradeoffs",
      "Return prioritized edits and a coaching question"
    ],
    "inputs": [
      "Draft",
      "Internal reference material"
    ],
    "outputs": [
      "Structured critique"
    ],
    "decision_points": [
      "What needs clarification?"
    ],
    "quality_checks": [
      "Context-based comparison"
    ],
    "exceptions": [
      "Human coaching remains available"
    ],
    "context_constraints": [
      "Internal Zapier practice"
    ],
    "structural_motifs": [
      "Contextual critique",
      "Expert rubric",
      "Author revision"
    ],
    "candidate_midlevel_pattern": "Reviewing a proposal against organizational decision criteria",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a research institute could help project leads pressure-test grant concepts against published program criteria before committee review.",
    "transfer_limit": "An executive's preferences are not objective merit; a reviewer must avoid suppressing legitimate dissent.",
    "unknowns": [
      "Full prompt",
      "False-positive critiques",
      "Independent assessment",
      "No video or system was run by this researcher"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2025-12-15",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.chatprd.ai/how-i-ai/ea-ai-workflows-for-meetings-culture-and-strategy",
      "evidence_note": "Original How I AI article header displays December 15, 2025 beside reading time. Article date is not independently verified recording or video-upload date; no separate update label found.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_publication_date"
    },
    "functions": [
      "leadership/strategy"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P03",
        "P08"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Firsthand Zapier EA account of a custom GPT process. Brex and WorkOS sponsor the episode; neither is the evaluated GPT/workflow vendor. ChatPRD hosts the interview but this is not a ChatPRD customer-success case.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Full prompt",
        "False-positive critiques",
        "Independent assessment",
        "No video or system was run by this researcher",
        "An executive's preferences are not objective merit; a reviewer must avoid suppressing legitimate dissent."
      ]
    },
    "eligibility_register_id": "comm-23"
  },
  {
    "id": "comm-24",
    "title": "Zapier's source-grounded strategy companion",
    "function": "leadership/strategy",
    "sector": "Workflow automation software",
    "source_url": "https://www.chatprd.ai/how-i-ai/ea-ai-workflows-for-meetings-culture-and-strategy",
    "source_title": "How I AI: Zapier EA Cortney Hickey's 4 AI Workflows for Meeting Prep, Culture Reinforcement, and Strategy",
    "accessed_date": "2026-10-18",
    "source_type": "Original interview and published demonstration walkthrough",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "reported-ai-practice",
    "summary": "Employees query a curated strategy notebook.",
    "steps": [
      "Collect strategy documents, transcripts, and team plans",
      "Ask role-specific questions",
      "Receive cited synthesis",
      "Maintain the source collection"
    ],
    "inputs": [
      "Strategy sources",
      "Employee question"
    ],
    "outputs": [
      "Source-linked answer"
    ],
    "decision_points": [
      "What does strategy imply for this role?"
    ],
    "quality_checks": [
      "Inspect citations and consequential interpretations"
    ],
    "exceptions": [
      "Stale documents require removal"
    ],
    "context_constraints": [
      "NotebookLM-based internal access"
    ],
    "structural_motifs": [
      "Curated corpus",
      "Question-guided synthesis",
      "Source maintenance"
    ],
    "candidate_midlevel_pattern": "Translating shared strategy into role-relevant understanding",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a conservation organization could let local teams query how an approved regional plan applies to their projects.",
    "transfer_limit": "Citations establish inspectability, not correctness; access control and version precedence must be designed.",
    "unknowns": [
      "Retrieval accuracy",
      "Access design",
      "Update ownership",
      "No video or system was run by this researcher"
    ],
    "provenance_note": "Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.",
    "source_dates": {
      "published": "2025-12-15",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.chatprd.ai/how-i-ai/ea-ai-workflows-for-meetings-culture-and-strategy",
      "evidence_note": "Same original How I AI article as comm-23: header displays December 15, 2025. Article date is not independently verified recording or video-upload date; no separate update label found.",
      "checked_at": "2026-10-18T03:01:00Z",
      "status": "verified_displayed_publication_date"
    },
    "functions": [
      "leadership/strategy"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Firsthand Zapier EA account of NotebookLM practice. Episode sponsors Brex and WorkOS are unrelated to the evaluated tool; disclose commercial host context without inferring effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Retrieval accuracy",
        "Access design",
        "Update ownership",
        "No video or system was run by this researcher",
        "Citations establish inspectability, not correctness; access control and version precedence must be designed."
      ]
    },
    "eligibility_register_id": "comm-24"
  },
  {
    "id": "OP-FIN-01",
    "source_dates": {
      "published": null,
      "updated": "2026-03-18",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/finance/accounting/",
      "evidence_note": "Page footer explicitly says Last modified March 18, 2026. This is page-level modification, not a verified change date for the reconciliation subsection. No publication date displayed.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_publication_or_update"
    },
    "title": "GitLab balance-sheet reconciliation",
    "function": "finance",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/finance/accounting/",
    "source_title": "Accounting and Reporting — Account Reconciliation Policy",
    "accessed_date": "2026-10-18",
    "source_type": "Organizational handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Assigned preparers substantiate balances; separate reviewers certify them.",
    "steps": [
      "Assign accounts and separate reviewers",
      "Sync period-end NetSuite balances",
      "Inspect activity and identify differences",
      "Attach support and sign off",
      "Review completeness and accuracy",
      "Repeat preparation and review if balances change"
    ],
    "inputs": [
      "Ledger balances",
      "Supporting schedules"
    ],
    "outputs": [
      "Approved reconciliation"
    ],
    "decision_points": [
      "Risk determines review depth"
    ],
    "quality_checks": [
      "Preparer differs from reviewer"
    ],
    "exceptions": [
      "Zero balances may auto-sign",
      "Changed balances invalidate sign-off"
    ],
    "context_constraints": [
      "US GAAP; monthly or quarterly cadence"
    ],
    "structural_motifs": [
      "evidence matching",
      "independent certification",
      "invalidation on change"
    ],
    "candidate_midlevel_pattern": "Reconcile an authoritative balance with supporting evidence",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Reconcile software-license entitlements with assigned seats and reopen certification after inventory changes.",
    "transfer_limit": "Balance definitions and accounting judgments do not transfer automatically.",
    "unknowns": [
      "Actual compliance and error rates",
      "Page mixes FloQast and BlackLine references; tool transition unresolved"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "finance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P05"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual compliance and error rates",
        "Page mixes FloQast and BlackLine references; tool transition unresolved",
        "Balance definitions and accounting judgments do not transfer automatically."
      ]
    },
    "eligibility_register_id": "OP-FIN-01"
  },
  {
    "id": "OP-FIN-02",
    "source_dates": {
      "published": null,
      "updated": "2026-09-15",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/finance/accounts-payable/",
      "evidence_note": "Page footer explicitly says Last modified September 15, 2026. No publication date displayed.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_publication_or_update"
    },
    "title": "GitLab supplier-invoice intake",
    "function": "finance",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/finance/accounts-payable/",
    "source_title": "Accounts Payable",
    "accessed_date": "2026-10-18",
    "source_type": "Organizational handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Invoice processing depends on vendor setup, complete evidence and an appropriate purchase-order route.",
    "steps": [
      "Confirm ZIP vendor onboarding",
      "Check invoice fields and approved PO",
      "Resolve missing PO with internal owner",
      "Route eligible non-PO request separately",
      "Obtain approvals before payment run"
    ],
    "inputs": [
      "Supplier invoice",
      "Purchase order",
      "Vendor record"
    ],
    "outputs": [
      "Processable invoice or correction request"
    ],
    "decision_points": [
      "PO exception eligibility",
      "Overage approval versus PO amendment"
    ],
    "quality_checks": [
      "Invoice required; quotation insufficient",
      "PO balance check"
    ],
    "exceptions": [
      "Over-tolerance amounts may need FP&A approval or PO change"
    ],
    "context_constraints": [
      "ZIP and NetSuite; scheduled payment runs"
    ],
    "structural_motifs": [
      "intake validation",
      "exception routing",
      "authorization gate"
    ],
    "candidate_midlevel_pattern": "Validate a claim against its prior authorization",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Match a reimbursement request to approved travel before reimbursement review.",
    "transfer_limit": "Approval thresholds, authority and payment rules are organization-specific.",
    "unknowns": [
      "Observed cycle time",
      "Duplicate-detection implementation"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "finance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04",
        "P05"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Observed cycle time",
        "Duplicate-detection implementation",
        "Approval thresholds, authority and payment rules are organization-specific."
      ]
    },
    "eligibility_register_id": "OP-FIN-02"
  },
  {
    "id": "OP-FIN-03",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2022-01-10",
      "other_date_type": "policy_last_reviewed_or_revised",
      "evidence_url": "https://www.uhsystem.edu/resources/compliance-ethics/uhs-policies/sams/03-fiscal-affairs/03g06/index.php",
      "evidence_note": "Policy footer labels 01/10/2022 Last Reviewed/Revised; also labels 03/08/2002 Issued. US date ordering used. These are policy dates, not verified webpage publication or update dates.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_other_date_only"
    },
    "title": "Houston bank-to-ledger reconciliation",
    "function": "finance",
    "sector": "Higher education",
    "source_url": "https://www.uhsystem.edu/resources/compliance-ethics/uhs-policies/sams/03-fiscal-affairs/03g06/index.php",
    "source_title": "03.G.06 — Bank Account Reconciliation Procedures",
    "accessed_date": "2026-10-18",
    "source_type": "Institutional procedure",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Bank differences are classified before correction requests and certification.",
    "steps": [
      "Obtain monthly statements",
      "Compare bank, financial and departmental records",
      "Separate timing differences from adjustment items",
      "Request bank corrections or accounting entries",
      "Prepare and review formal reconciliation",
      "Retain the report"
    ],
    "inputs": [
      "Bank statements",
      "Financial records",
      "Department records"
    ],
    "outputs": [
      "Certified reconciliation",
      "Correction requests"
    ],
    "decision_points": [
      "Timing difference or error requiring adjustment"
    ],
    "quality_checks": [
      "Dated preparer and management certification"
    ],
    "exceptions": [
      "Outstanding items remain tracked to resolution"
    ],
    "context_constraints": [
      "Institutional bank accounts; monthly close"
    ],
    "structural_motifs": [
      "cross-source comparison",
      "discrepancy taxonomy",
      "correction ownership"
    ],
    "candidate_midlevel_pattern": "Classify and resolve discrepancies between independent records",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Compare a warehouse ledger with a carrier delivery ledger before correcting either.",
    "transfer_limit": "Accounting timing and correction authority need local equivalents.",
    "unknowns": [
      "Matching algorithms",
      "Materiality thresholds"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "finance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P05"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Matching algorithms",
        "Materiality thresholds",
        "Accounting timing and correction authority need local equivalents."
      ]
    },
    "eligibility_register_id": "OP-FIN-03"
  },
  {
    "id": "OP-FIN-04",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2025-10-22",
      "other_date_type": "policy_effective_and_approval",
      "evidence_url": "https://statetechmo.edu/journal-entry-preparation-and-approval-policy/",
      "evidence_note": "Policy explicitly labels October 22, 2025 as both effective date and presidential approval date. Webpage publication/update dates not displayed.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_other_date_only"
    },
    "title": "State Tech journal-entry approval",
    "function": "finance",
    "sector": "Higher education",
    "source_url": "https://statetechmo.edu/journal-entry-preparation-and-approval-policy/",
    "source_title": "Journal Entry Preparation and Approval Policy",
    "accessed_date": "2026-10-18",
    "source_type": "Institutional policy with procedure",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "An accounting adjustment is supported and checked by a second person.",
    "steps": [
      "Prepare entry and description",
      "Print and initial",
      "Attach purpose-supporting evidence",
      "Submit to separate approver",
      "Approver checks support, amounts, accounts and debit-credit treatment",
      "Approver initials"
    ],
    "inputs": [
      "Entry proposal",
      "Supporting documentation"
    ],
    "outputs": [
      "Initialed journal entry"
    ],
    "decision_points": [
      "Whether evidence supports the proposed entry"
    ],
    "quality_checks": [
      "Separate preparer and approver",
      "Amounts tie to support"
    ],
    "exceptions": [],
    "context_constraints": [
      "Business office; knowledgeable reviewers"
    ],
    "structural_motifs": [
      "evidence packet",
      "maker-checker",
      "semantic validation"
    ],
    "candidate_midlevel_pattern": "Approve a structured change against its evidentiary basis",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Require an independent reviewer for a master-data correction and its supporting documents.",
    "transfer_limit": "Accounting correctness requires domain expertise beyond balanced fields.",
    "unknowns": [
      "Rejection/rework procedure",
      "Posting step",
      "Audit results"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "finance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P05"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Rejection/rework procedure",
        "Posting step",
        "Audit results",
        "Accounting correctness requires domain expertise beyond balanced fields."
      ]
    },
    "eligibility_register_id": "OP-FIN-04"
  },
  {
    "id": "OP-FIN-05",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.finops.org/framework/capabilities/anomaly-management/",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "FinOps cost-anomaly investigation",
    "function": "finance",
    "sector": "Cross-industry cloud operations",
    "source_url": "https://www.finops.org/framework/capabilities/anomaly-management/",
    "source_title": "Anomaly Management — FinOps Framework",
    "accessed_date": "2026-10-18",
    "source_type": "Practitioner foundation operating guidance",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Unexpected spend is investigated using granular usage and ownership data.",
    "steps": [
      "Compare current usage with expectations",
      "Create and route alerts",
      "Analyze and categorize anomalies",
      "Investigate responsible scope",
      "Adjust usage, revise expectations or acknowledge explanation",
      "Document resolution"
    ],
    "inputs": [
      "Cost and usage data",
      "Allocation metadata",
      "Expected spend"
    ],
    "outputs": [
      "Owner alert",
      "Documented resolution"
    ],
    "decision_points": [
      "Unexpected waste versus anticipated increase"
    ],
    "quality_checks": [
      "Inspect subcategories rather than aggregates alone"
    ],
    "exceptions": [
      "Planned launches can produce false positives"
    ],
    "context_constraints": [
      "Requires usable allocation and accountability metadata"
    ],
    "structural_motifs": [
      "baseline comparison",
      "owner routing",
      "explanation or intervention"
    ],
    "candidate_midlevel_pattern": "Investigate deviations against an explainable operational baseline",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Investigate support-ticket surges by product and owner before changing staffing.",
    "transfer_limit": "Spend, user demand and service value must be interpreted together.",
    "unknowns": [
      "Specific adopting organization",
      "Alert thresholds",
      "Measured effectiveness"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "finance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P06",
        "P04"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Specific adopting organization",
        "Alert thresholds",
        "Measured effectiveness",
        "Spend, user demand and service value must be interpreted together."
      ]
    },
    "eligibility_register_id": "OP-FIN-05"
  },
  {
    "id": "OP-ENG-01",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2017-10-06",
      "other_date_type": "reported_incident_date",
      "evidence_url": "https://sre.google/workbook/incident-response/",
      "evidence_note": "Case text dates the PagerDuty incident October 6, 2017. Footer gives book copyright 2018, which is not treated as webpage publication. Chapter publication and update dates not established.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_other_date_only"
    },
    "title": "PagerDuty NTP incident recovery",
    "function": "engineering/IT",
    "sector": "SaaS incident management",
    "source_url": "https://sre.google/workbook/incident-response/",
    "source_title": "SRE Workbook — Incident Response, PagerDuty case",
    "accessed_date": "2026-10-18",
    "source_type": "Original practitioner incident account",
    "evidence_status": "practitioner-reported",
    "implementation_type": "conventional documented workflow",
    "summary": "A clock-drift incident escalated after runbook recovery did not resolve it.",
    "steps": [
      "Validate automated recovery and runbooks",
      "Declare major incident",
      "Assemble dependent-service owners",
      "Try recovery options methodically",
      "Rotate responders",
      "Change NTP configuration",
      "Verify recovery with every service owner",
      "Assign postmortem before closing"
    ],
    "inputs": [
      "Clock-drift alerts",
      "Runbooks",
      "Service ownership"
    ],
    "outputs": [
      "Restored services",
      "Postmortem assignment"
    ],
    "decision_points": [
      "Runbook exhausted; escalate"
    ],
    "quality_checks": [
      "Service-owner recovery confirmation"
    ],
    "exceptions": [
      "Novel recovery needed beyond runbooks"
    ],
    "context_constraints": [
      "Incident dated 2017-10-06; multi-team response"
    ],
    "structural_motifs": [
      "escalation",
      "parallel diagnosis",
      "verified recovery"
    ],
    "candidate_midlevel_pattern": "Coordinate exception recovery with explicit ownership and closure checks",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Coordinate recovery from a failed payroll batch across upstream owners and downstream consumers.",
    "transfer_limit": "Technical restoration is not equivalent to reversing financial transactions.",
    "unknowns": [
      "Exact configuration change",
      "Controlled comparison of response effectiveness"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "engineering/IT"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P06",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Exact configuration change",
        "Controlled comparison of response effectiveness",
        "Technical restoration is not equivalent to reversing financial transactions."
      ]
    },
    "eligibility_register_id": "OP-ENG-01"
  },
  {
    "id": "OP-ENG-02",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://response.pagerduty.com/after/post_mortem_process/",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "PagerDuty evidence-linked postmortem",
    "function": "engineering/IT",
    "sector": "SaaS incident management",
    "source_url": "https://response.pagerduty.com/after/post_mortem_process/",
    "source_title": "Postmortem Process",
    "accessed_date": "2026-10-18",
    "source_type": "Organizational operating handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "A named owner constructs an evidence-linked account and reviewed follow-up actions.",
    "steps": [
      "Assign owner and schedule review",
      "Reconstruct timeline from incident records",
      "Link timeline items to evidence",
      "Analyze cause and customer impact",
      "Review draft with participants",
      "Discuss disagreements and actions",
      "Create prioritized tickets",
      "Communicate findings and close document"
    ],
    "inputs": [
      "Logs",
      "Chat history",
      "Metrics",
      "Call recording"
    ],
    "outputs": [
      "Reviewed postmortem",
      "Action tickets"
    ],
    "decision_points": [
      "Whether external message is needed",
      "Which actions justify priority"
    ],
    "quality_checks": [
      "Evidence for timeline assertions",
      "Participant review"
    ],
    "exceptions": [
      "Document closure does not mean action tickets are resolved"
    ],
    "context_constraints": [
      "Major SEV-1/2 incidents"
    ],
    "structural_motifs": [
      "causal reconstruction",
      "evidence lineage",
      "separate closure states"
    ],
    "candidate_midlevel_pattern": "Reconstruct an event into evidence-backed lessons and owned actions",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Analyze a failed procurement exercise using correspondence and decision records.",
    "transfer_limit": "Root-cause certainty may remain limited; legal accountability differs.",
    "unknowns": [
      "Follow-up ticket completion rate",
      "Measured recurrence reduction"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "engineering/IT"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P06",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Follow-up ticket completion rate",
        "Measured recurrence reduction",
        "Root-cause certainty may remain limited; legal accountability differs."
      ]
    },
    "eligibility_register_id": "OP-ENG-02"
  },
  {
    "id": "OP-ENG-03",
    "source_dates": {
      "published": "2019-12-05",
      "updated": "2019-12-05",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://builder.aws.com/content/3F04j2yRAAMBuPSPs50xwXZqg01/ensuring-rollback-safety-during-deployments",
      "evidence_note": "Article heading explicitly displays Published Dec 5, 2019 and Last modified Dec 5, 2019.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_publication_or_update"
    },
    "title": "Amazon two-phase protocol rollout",
    "function": "engineering/IT",
    "sector": "Cloud infrastructure",
    "source_url": "https://builder.aws.com/content/3F04j2yRAAMBuPSPs50xwXZqg01/ensuring-rollback-safety-during-deployments",
    "source_title": "Ensuring rollback safety during deployments",
    "accessed_date": "2026-10-18",
    "source_type": "Original engineer walkthrough",
    "evidence_status": "practitioner-reported",
    "implementation_type": "conventional documented workflow",
    "summary": "Predeployment compatibility tests precede a prepare-then-activate production transition.",
    "steps": [
      "Prerequisite: verify mixed-version upgrade and rollback in a production-representative test environment before rollout",
      "Prepare readers for both formats",
      "Verify every server received preparation",
      "Allow a bake period",
      "Activate new-format writing",
      "Retain old-format reading until backfill completes"
    ],
    "inputs": [
      "Old/new protocol",
      "Fleet inventory",
      "Representative tests"
    ],
    "outputs": [
      "Compatibility-preserving rollout"
    ],
    "decision_points": [
      "Ready to activate only after complete preparation"
    ],
    "quality_checks": [
      "Every-host verification",
      "Predeployment mixed-version and downgrade tests in a representative test environment"
    ],
    "exceptions": [
      "Cannot safely roll back both phases after new writes"
    ],
    "context_constraints": [
      "Distributed persistent state; source includes hypothetical XML/JSON illustration and actual DynamoDB coordination"
    ],
    "structural_motifs": [
      "prepare before activate",
      "compatibility boundary",
      "rollback proof"
    ],
    "candidate_midlevel_pattern": "Stage a transition while preserving interoperability with prior state",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Prepare all reporting consumers for new taxonomy before producers begin using it.",
    "transfer_limit": "Legal agreements and physical actions may be irreversible in ways software is not.",
    "unknowns": [
      "Actual rollout metrics",
      "Universal bake duration"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "engineering/IT"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P11",
        "P09"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual rollout metrics",
        "Universal bake duration",
        "Legal agreements and physical actions may be irreversible in ways software is not."
      ]
    },
    "eligibility_register_id": "OP-ENG-03"
  },
  {
    "id": "OP-ENG-04",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "Mozilla defect triage",
    "function": "engineering/IT",
    "sector": "Open-source browser development",
    "source_url": "https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html",
    "source_title": "Triage for Bugzilla",
    "accessed_date": "2026-10-18",
    "source_type": "Project operating policy",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Incoming defects acquire severity and ownership without losing unresolved information requests.",
    "steps": [
      "Review incoming component bugs",
      "Request reproduction details when missing",
      "Assign valid severity",
      "Route to the responsible component",
      "Escalate severe misrouted defects",
      "Revisit unanswered information requests and stalled bugs"
    ],
    "inputs": [
      "Bug report",
      "Reproduction details",
      "Component ownership"
    ],
    "outputs": [
      "Triaged defect or information request"
    ],
    "decision_points": [
      "Defect versus enhancement/task",
      "Enough information to decide"
    ],
    "quality_checks": [
      "Severity-change rationale",
      "Defects cannot use N/A severity"
    ],
    "exceptions": [
      "Unanswered minor reports can close incomplete",
      "Stalled cases remain separately marked"
    ],
    "context_constraints": [
      "Firefox Bugzilla; daily assessment and weekly triage expectations"
    ],
    "structural_motifs": [
      "intake enrichment",
      "risk classification",
      "routing",
      "aging queues"
    ],
    "candidate_midlevel_pattern": "Enrich and route incomplete reports while preserving high-risk visibility",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Triage supplier defects using evidence completeness and service impact.",
    "transfer_limit": "Severity definitions and release consequences are product-specific.",
    "unknowns": [
      "Actual triage adherence",
      "Classifier accuracy"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "engineering/IT"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual triage adherence",
        "Classifier accuracy",
        "Severity definitions and release consequences are product-specific."
      ]
    },
    "eligibility_register_id": "OP-ENG-04"
  },
  {
    "id": "OP-ENG-05",
    "source_dates": {
      "published": null,
      "updated": "2026-09-15",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/eta/corporate-it/end-user-services/access-requests/frequently-asked-questions/",
      "evidence_note": "Page footer explicitly says Last modified September 15, 2026. Original publication date not displayed.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_publication_or_update"
    },
    "title": "GitLab scoped access request",
    "function": "engineering/IT",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/eta/corporate-it/end-user-services/access-requests/frequently-asked-questions/",
    "source_title": "Access Requests (AR) in Compass FAQs",
    "accessed_date": "2026-10-18",
    "source_type": "Organizational handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "A ticket captures access scope, approvals and provisioning ownership.",
    "steps": [
      "Check baseline entitlement",
      "Submit system and requested permissions in Compass",
      "Capture required approvals in ticket",
      "Route to provisioning team",
      "Check ticket status and follow up with owner"
    ],
    "inputs": [
      "System/group identifier",
      "Requested role"
    ],
    "outputs": [
      "Provisioning ticket",
      "Approval record"
    ],
    "decision_points": [
      "Manager approval required or exempt"
    ],
    "quality_checks": [
      "Explicit permission scope",
      "Approval captured in same record"
    ],
    "exceptions": [
      "Baseline access and some groups are exempt",
      "Production consoles use temporary-access route"
    ],
    "context_constraints": [
      "Compass; source warns stale-ticket auto-close details are evolving"
    ],
    "structural_motifs": [
      "scoped request",
      "policy gate",
      "owner handoff"
    ],
    "candidate_midlevel_pattern": "Authorize a precisely scoped entitlement before fulfillment",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Route permission to use restricted research datasets through a scoped approval ticket.",
    "transfer_limit": "Permission granting remains security-sensitive; no universal approval exemption.",
    "unknowns": [
      "Provisioning verification detail",
      "Actual auto-close behavior"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "engineering/IT"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Provisioning verification detail",
        "Actual auto-close behavior",
        "Permission granting remains security-sensitive; no universal approval exemption."
      ]
    },
    "eligibility_register_id": "OP-ENG-05"
  },
  {
    "id": "OP-LEG-01",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://ico.org.uk/for-organisations/advice-for-small-organisations/subject-access-requests-sar/how-to-deal-with-a-request-for-information-a-step-by-step-guide/",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "ICO subject-access response preparation",
    "function": "legal/compliance",
    "sector": "Cross-sector privacy regulation",
    "source_url": "https://ico.org.uk/for-organisations/advice-for-small-organisations/subject-access-requests-sar/how-to-deal-with-a-request-for-information-a-step-by-step-guide/",
    "source_title": "How to deal with a request for information: a step-by-step guide",
    "accessed_date": "2026-10-18",
    "source_type": "Regulator procedural guidance",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Requested records are scoped, searched and checked before secure disclosure.",
    "steps": [
      "Clarify requested scope",
      "Search relevant storage locations",
      "Assess third-party information and redactions",
      "Document withholding reasons",
      "Prepare response in suitable format",
      "Perform final check",
      "Send securely and retain dated record"
    ],
    "inputs": [
      "Access request",
      "Located records"
    ],
    "outputs": [
      "Reviewed disclosure package",
      "Disclosure record"
    ],
    "decision_points": [
      "Redact, disclose or withhold third-party material"
    ],
    "quality_checks": [
      "Check redactions cannot reveal hidden text"
    ],
    "exceptions": [
      "Linked third-party information requires judgment"
    ],
    "context_constraints": [
      "UK privacy context; page explicitly under review after legislative change"
    ],
    "structural_motifs": [
      "scoped retrieval",
      "selective disclosure",
      "release audit"
    ],
    "candidate_midlevel_pattern": "Assemble a disclosure package with item-level release controls",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Prepare an audit evidence pack while excluding unrelated confidential material.",
    "transfer_limit": "Legal disclosure rules must be reassessed; this is descriptive research, not current compliance advice.",
    "unknowns": [
      "Current applicability of every detail",
      "Search completeness",
      "Empirical success rate"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "legal/compliance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P03"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Current applicability of every detail",
        "Search completeness",
        "Empirical success rate",
        "Legal disclosure rules must be reassessed; this is descriptive research, not current compliance advice."
      ]
    },
    "eligibility_register_id": "OP-LEG-01"
  },
  {
    "id": "OP-LEG-02",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/data-protection-impact-assessments-dpias/how-do-we-do-a-dpia/",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "ICO data-protection impact assessment",
    "function": "legal/compliance",
    "sector": "Cross-sector privacy regulation",
    "source_url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/data-protection-impact-assessments-dpias/how-do-we-do-a-dpia/",
    "source_title": "How do we do a DPIA?",
    "accessed_date": "2026-10-18",
    "source_type": "Regulator procedural guidance",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Risk analysis feeds mitigation decisions back into project planning.",
    "steps": [
      "Identify assessment need",
      "Describe processing",
      "Consult relevant stakeholders",
      "Assess necessity and proportionality",
      "Assess risks",
      "Identify mitigations",
      "Record and sign off outcomes",
      "Integrate into plan and keep under review"
    ],
    "inputs": [
      "Proposed processing",
      "Stakeholder views"
    ],
    "outputs": [
      "Assessment",
      "Mitigations in project plan"
    ],
    "decision_points": [
      "Whether assessment needed",
      "Which measures reduce risk"
    ],
    "quality_checks": [
      "Documented outcomes and sign-off"
    ],
    "exceptions": [
      "Process scales with project"
    ],
    "context_constraints": [
      "Begins before processing; guidance under review after legislative change"
    ],
    "structural_motifs": [
      "risk decomposition",
      "mitigation design",
      "planning feedback"
    ],
    "candidate_midlevel_pattern": "Convert a proposed activity into a reviewable risk-and-mitigation plan",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Assess operational risks of a new supplier onboarding process before launch.",
    "transfer_limit": "Privacy risk criteria and regulatory escalation do not transfer wholesale.",
    "unknowns": [
      "Actual implementation evidence",
      "Review cadence",
      "Risk acceptance in a specific organization"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "legal/compliance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P08"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual implementation evidence",
        "Review cadence",
        "Risk acceptance in a specific organization",
        "Privacy risk criteria and regulatory escalation do not transfer wholesale."
      ]
    },
    "eligibility_register_id": "OP-LEG-02"
  },
  {
    "id": "OP-LEG-03",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.queensu.ca/secretariat/legal-counsel/contract-review",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "Queen's contract-review intake and completion",
    "function": "legal/compliance",
    "sector": "Higher education",
    "source_url": "https://www.queensu.ca/secretariat/legal-counsel/contract-review",
    "source_title": "Contract Review",
    "accessed_date": "2026-10-18",
    "source_type": "Institutional procedure",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Legal review starts with a complete contextual packet and ends with an executed copy.",
    "steps": [
      "Complete required request fields",
      "Provide context and contract attachments",
      "Receive submission confirmation",
      "Respond to legal questions or revisions",
      "Receive readiness-for-signature approval",
      "Submit fully executed contract copy"
    ],
    "inputs": [
      "Contract draft",
      "Background",
      "Related documents"
    ],
    "outputs": [
      "Reviewed contract",
      "Executed contract record"
    ],
    "decision_points": [
      "Need for additional information or revisions"
    ],
    "quality_checks": [
      "Required fields block incomplete submissions"
    ],
    "exceptions": [
      "Urgent requests use direct contact"
    ],
    "context_constraints": [
      "Replacement intake form; signature process separate"
    ],
    "structural_motifs": [
      "completeness gate",
      "specialist review",
      "record closure"
    ],
    "candidate_midlevel_pattern": "Prepare a specialist-review packet and track it through final artifact capture",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Submit a security architecture review with context and retain the approved implementation record.",
    "transfer_limit": "Legal review scope and signature authority cannot be replaced by generic approval.",
    "unknowns": [
      "Substantive review checklist",
      "Negotiation steps",
      "Observed turnaround"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "legal/compliance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Substantive review checklist",
        "Negotiation steps",
        "Observed turnaround",
        "Legal review scope and signature authority cannot be replaced by generic approval."
      ]
    },
    "eligibility_register_id": "OP-LEG-03"
  },
  {
    "id": "OP-LEG-04",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.tc.columbia.edu/vpa/coi/management-procedures/",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "Teachers College conflict-management plan",
    "function": "legal/compliance",
    "sector": "Higher education",
    "source_url": "https://www.tc.columbia.edu/vpa/coi/management-procedures/",
    "source_title": "Management Procedures — Conflict of Interest",
    "accessed_date": "2026-10-18",
    "source_type": "Institutional procedure",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Disclosed conflicts trigger layered review and a recorded management plan.",
    "steps": [
      "Receive disclosure",
      "Area designee reviews",
      "Escalate identified conflict to compliance and committee",
      "Committee drafts management plan",
      "Compliance reviews; designee and disclosee sign",
      "Vice President approves",
      "Upload signed plan to Cayuse"
    ],
    "inputs": [
      "Disclosure"
    ],
    "outputs": [
      "Approved management plan",
      "COI status record"
    ],
    "decision_points": [
      "No outside interest versus potential conflict"
    ],
    "quality_checks": [
      "Multiple designated reviews and signatures"
    ],
    "exceptions": [
      "No-interest disclosures close automatically"
    ],
    "context_constraints": [
      "College governance; committee-based risk management"
    ],
    "structural_motifs": [
      "conditional escalation",
      "negotiated controls",
      "recorded acceptance"
    ],
    "candidate_midlevel_pattern": "Turn a disclosed conflict into an accountable management arrangement",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Manage a procurement evaluator's potential conflict through a reviewed recusal plan.",
    "transfer_limit": "Do not infer that all conflicts are manageable or that screening proves absence.",
    "unknowns": [
      "Enforcement results",
      "Specific mitigation options",
      "False-negative rate"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "legal/compliance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04",
        "P08"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Enforcement results",
        "Specific mitigation options",
        "False-negative rate",
        "Do not infer that all conflicts are manageable or that screening proves absence."
      ]
    },
    "eligibility_register_id": "OP-LEG-04"
  },
  {
    "id": "OP-LEG-05",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2026-06-15",
      "other_date_type": "standard_effective_and_review",
      "evidence_url": "https://www.cwu.edu/about/offices/information-services/policy-management/standards-procedures/litigation-hold-standard.php",
      "evidence_note": "Standard header says Effective June 15, 2026; history says Review/Effective Date 06/15/26. Scheduled review year 2030 is not a past update. Webpage publication/update dates not established.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_other_date_only"
    },
    "title": "CWU litigation-hold preservation",
    "function": "legal/compliance",
    "sector": "Higher education",
    "source_url": "https://www.cwu.edu/about/offices/information-services/policy-management/standards-procedures/litigation-hold-standard.php",
    "source_title": "InfoSec-Standard-009 — Litigation Hold Standard",
    "accessed_date": "2026-10-18",
    "source_type": "Institutional standard and procedure",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Counsel-scoped preservation overrides routine record disposal until a scoped release.",
    "steps": [
      "Notify counsel of anticipated litigation",
      "Assess risk with coordinator",
      "Issue hold if appropriate",
      "Identify custodians and preservation actions",
      "Distribute notice and track acknowledgments",
      "Implement preservation plan",
      "Circulate counsel's lift notice when concluded"
    ],
    "inputs": [
      "Litigation notice",
      "Record locations",
      "Custodian list"
    ],
    "outputs": [
      "Hold register",
      "Preservation plan",
      "Lift notice"
    ],
    "decision_points": [
      "Issue, modify or release hold"
    ],
    "quality_checks": [
      "Evidence checklist",
      "Follow-up compliance actions"
    ],
    "exceptions": [
      "Other holds and retention duties survive release",
      "Data loss escalates to IT/coordinator"
    ],
    "context_constraints": [
      "Only designated counsel controls hold scope; some source sentences are truncated"
    ],
    "structural_motifs": [
      "policy override",
      "scoped preservation",
      "authorized release"
    ],
    "candidate_midlevel_pattern": "Suspend normal lifecycle actions for a scoped evidence obligation",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Freeze selected procurement records during an internal audit and release only the relevant freeze.",
    "transfer_limit": "Retention obligations and privilege require qualified legal oversight.",
    "unknowns": [
      "Missing words in published text",
      "Actual preservation verification",
      "Implementation coverage"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "legal/compliance"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P10"
      ],
      "split": "training",
      "fit": "partial",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Missing words in published text",
        "Actual preservation verification",
        "Implementation coverage",
        "Retention obligations and privilege require qualified legal oversight."
      ]
    },
    "eligibility_register_id": "OP-LEG-05"
  },
  {
    "id": "OP-PROC-01",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://procurementjourney.scot/index.php/route-3/evaluation/technical-evaluation",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "Scottish technical-tender moderation",
    "function": "procurement/operations",
    "sector": "Public procurement",
    "source_url": "https://procurementjourney.scot/index.php/route-3/evaluation/technical-evaluation",
    "source_title": "Technical Evaluation — Route 3",
    "accessed_date": "2026-10-18",
    "source_type": "Government procurement operating guidance",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Independent technical judgments are reconciled into documented final scores.",
    "steps": [
      "Establish capable conflict-free panel",
      "Read bids against published criteria",
      "Score independently with justification",
      "Record unclear points for clarification",
      "Collate scores",
      "Moderate differences and agree final scores",
      "Document agreement"
    ],
    "inputs": [
      "Bid submissions",
      "Published criteria and weights"
    ],
    "outputs": [
      "Justified final technical scores"
    ],
    "decision_points": [
      "Clarification needed",
      "Final score agreement"
    ],
    "quality_checks": [
      "No invented bidder details",
      "Criteria cannot change during evaluation"
    ],
    "exceptions": [
      "Commercial assessment handled separately"
    ],
    "context_constraints": [
      "Scottish public procurement; panel at least two"
    ],
    "structural_motifs": [
      "independent assessment",
      "criterion grounding",
      "moderated consensus"
    ],
    "candidate_midlevel_pattern": "Combine independent rubric judgments into a traceable decision",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Evaluate grant proposals independently before a documented consensus meeting.",
    "transfer_limit": "Procurement fairness and communication rules are jurisdiction-specific.",
    "unknowns": [
      "Inter-rater reliability",
      "Resolution method when consensus fails"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "procurement/operations"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P07"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Inter-rater reliability",
        "Resolution method when consensus fails",
        "Procurement fairness and communication rules are jurisdiction-specific."
      ]
    },
    "eligibility_register_id": "OP-PROC-01"
  },
  {
    "id": "OP-PROC-02",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2026-03-13",
      "other_date_type": "displayed_FAC_edition_effective_date",
      "evidence_url": "https://www.acquisition.gov/far/15.404-1",
      "evidence_note": "Page header identifies FAC 2026-01, Effective Date 03/13/2026. This is the displayed FAR compilation edition, not proof this section changed on that date, and not webpage publication/update.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_other_date_only"
    },
    "title": "Federal proposed-price analysis",
    "function": "procurement/operations",
    "sector": "US federal acquisition",
    "source_url": "https://www.acquisition.gov/far/15.404-1",
    "source_title": "FAR 15.404-1 — Proposal analysis techniques",
    "accessed_date": "2026-10-18",
    "source_type": "Government acquisition operating rule",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Proposed prices are tested against comparable evidence with contextual adjustments.",
    "steps": [
      "Select analysis depth appropriate to acquisition",
      "Obtain competing or historical price evidence",
      "Check comparability",
      "Adjust for terms, quantity and market differences",
      "Seek technical help for item differences",
      "Escalate insufficient price evidence to other analysis"
    ],
    "inputs": [
      "Proposal",
      "Comparable prices",
      "Terms and market context"
    ],
    "outputs": [
      "Price-reasonableness analysis"
    ],
    "decision_points": [
      "Price analysis sufficient or cost analysis required"
    ],
    "quality_checks": [
      "Historical price must be a valid comparator"
    ],
    "exceptions": [
      "Old or uncertain comparators may be unsuitable"
    ],
    "context_constraints": [
      "Contracting-officer authority; not a universal ordered algorithm"
    ],
    "structural_motifs": [
      "comparability assessment",
      "normalization",
      "evidence sufficiency"
    ],
    "candidate_midlevel_pattern": "Normalize comparison evidence before judging a proposed value",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Compare software-benchmark claims only after aligning workloads and measurement conditions.",
    "transfer_limit": "Statutory pricing requirements and procurement discretion remain domain-specific.",
    "unknowns": [
      "Actual decision trace",
      "Practitioner error rates",
      "Current rule-version date"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "procurement/operations"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02"
      ],
      "split": "held-out",
      "fit": "qualified",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual decision trace",
        "Practitioner error rates",
        "Current rule-version date",
        "Statutory pricing requirements and procurement discretion remain domain-specific."
      ]
    },
    "eligibility_register_id": "OP-PROC-02"
  },
  {
    "id": "OP-PROC-03",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://log.logcluster.org/en/monitoring-and-counting",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "Logistics Cluster blind stock spot-check",
    "function": "procurement/operations",
    "sector": "Humanitarian logistics",
    "source_url": "https://log.logcluster.org/en/monitoring-and-counting",
    "source_title": "Monitoring and Counting — Logistics Operational Guide",
    "accessed_date": "2026-10-18",
    "source_type": "Humanitarian operating guide",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Independent physical counts are reconciled before comparison with the ledger.",
    "steps": [
      "Choose a small random set of stock lines",
      "Halt movement of selected items",
      "Locate items",
      "Conduct two independent counts",
      "Reconcile count differences",
      "Compare agreed count with ledger",
      "Record discrepancies"
    ],
    "inputs": [
      "Warehouse ledger",
      "Physical stock"
    ],
    "outputs": [
      "Count results",
      "Discrepancy record"
    ],
    "decision_points": [
      "Disagreement between counts or ledger"
    ],
    "quality_checks": [
      "Blind count",
      "Independent second counter"
    ],
    "exceptions": [
      "Ask warehouse staff when items cannot be located"
    ],
    "context_constraints": [
      "Limited-access inspections; selected stock held stationary"
    ],
    "structural_motifs": [
      "independent measurement",
      "measurement reconciliation",
      "ledger check"
    ],
    "candidate_midlevel_pattern": "Verify a recorded state using independent observations",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Independently count active software deployments before reconciling an asset register.",
    "transfer_limit": "Physical movement controls differ from continuously changing digital state.",
    "unknowns": [
      "Downstream correction approval",
      "Observed loss reduction"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "procurement/operations"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P05"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Downstream correction approval",
        "Observed loss reduction",
        "Physical movement controls differ from continuously changing digital state."
      ]
    },
    "eligibility_register_id": "OP-PROC-03"
  },
  {
    "id": "OP-PROC-04",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2024-08-30",
      "other_date_type": "procedure_effective",
      "evidence_url": "https://policy.tennessee.edu/procedure/procedure-for-fi0405-procurement-receiving-materials/",
      "evidence_note": "Procedure footer explicitly says Version 1, Effective 08/30/2024. No separate webpage publication/update date displayed.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "verified_other_date_only"
    },
    "title": "Tennessee receipt-to-invoice match",
    "function": "procurement/operations",
    "sector": "Higher education",
    "source_url": "https://policy.tennessee.edu/procedure/procedure-for-fi0405-procurement-receiving-materials/",
    "source_title": "Procedure for FI0405: Procurement — Receiving Materials",
    "accessed_date": "2026-10-18",
    "source_type": "Institutional procedure",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Actual receipt is recorded and matched against both order and invoice.",
    "steps": [
      "Inspect delivery",
      "Document damage and notify vendor when accepted",
      "Report missing materials",
      "Record only actual quantity received",
      "Compare order, receipt and invoice",
      "Resolve mismatch with vendor"
    ],
    "inputs": [
      "Purchase order",
      "Delivered materials",
      "Invoice"
    ],
    "outputs": [
      "Receipt record",
      "Discrepancy evidence"
    ],
    "decision_points": [
      "Refuse damaged delivery or document accepted damage"
    ],
    "quality_checks": [
      "Three-way match",
      "Partial receipts reflect actual quantities"
    ],
    "exceptions": [
      "Shipments may be split",
      "Concealed damage requires photos"
    ],
    "context_constraints": [
      "Marketplace receipt within three business days; local central-receiving procedures may apply"
    ],
    "structural_motifs": [
      "three-source matching",
      "partial fulfillment",
      "exception documentation"
    ],
    "candidate_midlevel_pattern": "Verify fulfillment before validating a claim for payment",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Match a contracted training session, attendance evidence and supplier invoice.",
    "transfer_limit": "Service acceptance may require qualitative criteria beyond quantities.",
    "unknowns": [
      "How disputes ultimately close",
      "System enforcement detail"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "procurement/operations"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P05",
        "P06"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "How disputes ultimately close",
        "System enforcement detail",
        "Service acceptance may require qualitative criteria beyond quantities."
      ]
    },
    "eligibility_register_id": "OP-PROC-04"
  },
  {
    "id": "OP-PROC-05",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.procurementjourney.scot/route-2/contract-and-supplier-management/contract-and-supplier-management-guidance-non-procurement",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "Scottish supplier-performance correction",
    "function": "procurement/operations",
    "sector": "Public procurement",
    "source_url": "https://www.procurementjourney.scot/route-2/contract-and-supplier-management/contract-and-supplier-management-guidance-non-procurement",
    "source_title": "Contract and Supplier Management Guidance for Non-Procurement Staff — Route 2",
    "accessed_date": "2026-10-18",
    "source_type": "Government procurement operating guidance",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Service issues are checked against agreed terms, corrected and escalated if persistent.",
    "steps": [
      "Check contract expectations",
      "Raise performance issue with supplier",
      "Agree corrective actions and timescales",
      "Record issue and actions",
      "Escalate if performance fails to improve"
    ],
    "inputs": [
      "Contract",
      "Performance issue"
    ],
    "outputs": [
      "Corrective action record"
    ],
    "decision_points": [
      "Minor fix or persistent issue requiring escalation"
    ],
    "quality_checks": [
      "Check what contract permits"
    ],
    "exceptions": [
      "Scope or cost changes require formal variation"
    ],
    "context_constraints": [
      "Non-procurement users; procurement handles material concerns"
    ],
    "structural_motifs": [
      "expectation comparison",
      "corrective agreement",
      "escalation threshold"
    ],
    "candidate_midlevel_pattern": "Turn an unmet service expectation into a tracked correction",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Address recurring internal data-delivery failures with an owner, due date and escalation route.",
    "transfer_limit": "Contract remedies and supplier negotiations do not map directly to internal work.",
    "unknowns": [
      "Outcome metrics",
      "Evidence needed to verify correction",
      "Detailed escalation ladder"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "procurement/operations"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P06",
        "P10"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Outcome metrics",
        "Evidence needed to verify correction",
        "Detailed escalation ladder",
        "Contract remedies and supplier negotiations do not map directly to internal work."
      ]
    },
    "eligibility_register_id": "OP-PROC-05"
  },
  {
    "id": "OP-PROC-06",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.procurementjourney.scot/index.php/route-3/contract-and-supplier-management/variations-extensions-amendments",
      "evidence_note": "Original page reopened and accessible page text checked. No explicit publication or last-update date found. Access/crawl dates and generic copyright notices are not publication dates; hidden metadata or complete version history not verified.",
      "checked_at": "2026-10-18T03:00:44Z",
      "status": "not_found_in_accessible_source"
    },
    "title": "Scottish contract-variation control",
    "function": "procurement/operations",
    "sector": "Public procurement",
    "source_url": "https://www.procurementjourney.scot/index.php/route-3/contract-and-supplier-management/variations-extensions-amendments",
    "source_title": "Variations / Extensions / Amendments — Route 3",
    "accessed_date": "2026-10-18",
    "source_type": "Government procurement operating guidance",
    "evidence_status": "documented-procedure",
    "implementation_type": "conventional documented workflow",
    "summary": "Proposed changes pass impact and authority checks before negotiation and record updates.",
    "steps": [
      "Describe proposed change and impacts",
      "Obtain procurement and legal review",
      "Secure required governance approvals",
      "Engage supplier after internal approval",
      "Document agreed variation and signatures",
      "Update registers, risks, KPIs and budgets"
    ],
    "inputs": [
      "Change request",
      "Existing contract",
      "Impact analysis"
    ],
    "outputs": [
      "Approved variation",
      "Updated operational records"
    ],
    "decision_points": [
      "Permissible variation or new procurement",
      "High-risk governance escalation"
    ],
    "quality_checks": [
      "Approval before supplier negotiations",
      "Retain signed change evidence"
    ],
    "exceptions": [
      "Significant scope, value or duration change needs specialist review"
    ],
    "context_constraints": [
      "Scottish public contracts; source presents example governance process"
    ],
    "structural_motifs": [
      "impact propagation",
      "authority gate",
      "versioned agreement"
    ],
    "candidate_midlevel_pattern": "Assess and authorize a baseline change before propagating it",
    "transfer_example_explicitly_hypothetical": "Hypothetical: Review a changed data definition for downstream impacts before updating reports and owners.",
    "transfer_limit": "Negotiation rights and statutory modification tests cannot be generalized.",
    "unknowns": [
      "Actual organizational implementation",
      "Time to approval",
      "Validated effect on scope creep"
    ],
    "evidence_notes": "Mechanics paraphrased from the cited source. Motifs, candidate pattern and transfer fields are analyst interpretation; not claims made by the source.",
    "functions": [
      "procurement/operations"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P08",
        "P11"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual organizational implementation",
        "Time to approval",
        "Validated effect on scope creep",
        "Negotiation rights and statutory modification tests cannot be generalized."
      ]
    },
    "eligibility_register_id": "OP-PROC-06"
  },
  {
    "id": "svc-01",
    "title": "Prepare and iterate a discovery conversation",
    "function": "sales",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/sales/playbook/discovery/",
    "source_title": "Effective Discovery",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "Qualify an opportunity, then develop the evidence needed for a customer-specific value proposition.",
    "steps": [
      "Review existing prospecting information.",
      "Check authority, initiative, fit and timing.",
      "Prepare desired outcomes and sequenced questions.",
      "Probe underlying needs and business impact.",
      "Identify the buying process and stakeholders.",
      "Continue discovery across conversations."
    ],
    "inputs": [
      "Prospecting notes",
      "Customer responses"
    ],
    "outputs": [
      "Pre-call plan",
      "Better understood needs and buying process"
    ],
    "decision_points": [
      "Is further pursuit justified?"
    ],
    "quality_checks": [
      "Avoid premature product positioning."
    ],
    "exceptions": [
      "Discovery can require multiple meetings."
    ],
    "context_constraints": [
      "Enterprise sales methodology"
    ],
    "structural_motifs": [
      "Iterative questioning",
      "Gap-directed evidence collection"
    ],
    "candidate_midlevel_pattern": "Build a decision-relevant understanding through iterative inquiry",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A service designer could use sequential interviews to clarify a service request.",
    "transfer_limit": "Transfer the inquiry loop, not sales qualification criteria.",
    "unknowns": [
      "Actual conversion effects",
      "Question selection algorithm"
    ],
    "evidence_locator": "Qualification; Understand Value Points; Identify the Buying Process",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "answering questions"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-09-24",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/sales/playbook/discovery/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-09-24. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "sales"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P01"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Actual conversion effects",
        "Question selection algorithm",
        "Transfer the inquiry loop, not sales qualification criteria."
      ]
    },
    "eligibility_register_id": "svc-01"
  },
  {
    "id": "svc-02",
    "title": "Maintain a reviewed opportunity plan",
    "function": "sales",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/sales/command-of-the-message/command-plan/",
    "source_title": "Command Plan",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "An account executive maintains an opportunity record linking business rationale, closing risks and agreed next actions.",
    "steps": [
      "Record customer problem, urgency and solution rationale.",
      "Add qualification and close-plan details when thresholds apply.",
      "Keep the plan current.",
      "Move obsolete but useful history into activity records.",
      "Manager records dated gaps and assigned next steps."
    ],
    "inputs": [
      "Customer discovery",
      "Opportunity stage and value"
    ],
    "outputs": [
      "Living opportunity plan",
      "Dated review actions"
    ],
    "decision_points": [
      "Which sections are required for this deal?"
    ],
    "quality_checks": [
      "Manager review identifies prioritized gaps and owners."
    ],
    "exceptions": [
      "Requirements vary with deal size and segment."
    ],
    "context_constraints": [
      "Salesforce plan length is capped."
    ],
    "structural_motifs": [
      "Living evidence packet",
      "Threshold-based review",
      "Action ownership"
    ],
    "candidate_midlevel_pattern": "Maintain a concise decision packet with explicit gaps and commitments",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A project sponsor could maintain a funding decision packet with unresolved assumptions.",
    "transfer_limit": "Deal thresholds and forecast cadence do not generalize.",
    "unknowns": [
      "Review effectiveness",
      "Actual plan examples"
    ],
    "evidence_locator": "Command Plan Requirements; Close Plan Details; Manager Review",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "content generation",
      "data analysis"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-09-24",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/sales/command-of-the-message/command-plan/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-09-24. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "sales"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Review effectiveness",
        "Actual plan examples",
        "Deal thresholds and forecast cadence do not generalize."
      ]
    },
    "eligibility_register_id": "svc-02"
  },
  {
    "id": "svc-03",
    "title": "Hand off a qualified opportunity",
    "function": "sales",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/sales/sales-development/",
    "source_title": "Sales Development",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "Sales development transfers a qualified opportunity to an account executive with scheduling and acceptance expectations.",
    "steps": [
      "Establish qualification or agree a mutual plan with the account executive.",
      "Book the initial qualifying meeting with advance notice.",
      "Provide the handoff context.",
      "Account executive accepts the opportunity and records feedback.",
      "Account executive takes ownership of subsequent scheduling."
    ],
    "inputs": [
      "Qualification evidence",
      "Meeting details"
    ],
    "outputs": [
      "Accepted handoff",
      "Qualification feedback"
    ],
    "decision_points": [
      "Does the lead meet the handoff standard?"
    ],
    "quality_checks": [
      "Acceptance and feedback are time-bounded."
    ],
    "exceptions": [
      "A mutual command plan can address incomplete qualification."
    ],
    "context_constraints": [
      "Business-hour notice and response windows"
    ],
    "structural_motifs": [
      "Acceptance gate",
      "Context transfer",
      "Ownership change"
    ],
    "candidate_midlevel_pattern": "Transfer responsibility through a qualified, acknowledged handoff",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A research team could hand off an implementation request with evidence and acceptance criteria.",
    "transfer_limit": "Do not import prospect criteria into operational requests.",
    "unknowns": [
      "Observed handoff failures",
      "Exact contents for every handoff type"
    ],
    "evidence_locator": "Handoff Meetings and Passing Opportunities to AEs",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "meeting distillation/action items"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-09-29",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/sales/sales-development/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-09-29. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "sales"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Observed handoff failures",
        "Exact contents for every handoff type",
        "Do not import prospect criteria into operational requests."
      ]
    },
    "eligibility_register_id": "svc-03"
  },
  {
    "id": "svc-07",
    "title": "Triage a support request to the right route",
    "function": "customer service/success",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/support/workflows/ticket_triage/",
    "source_title": "Triaging Tickets",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "Support checks request type and entitlement before correcting routing and collecting missing diagnostic context.",
    "steps": [
      "Check the ticket form.",
      "Route incorrectly submitted requests through the prescribed macro.",
      "Check free-user eligibility.",
      "Redirect ineligible requests or select the correct account/billing route.",
      "Set category and obtain missing installation/version information."
    ],
    "inputs": [
      "Ticket",
      "Account status",
      "Product environment"
    ],
    "outputs": [
      "Routed or redirected ticket",
      "Diagnostic context"
    ],
    "decision_points": [
      "Eligible support request?",
      "Which form and team?"
    ],
    "quality_checks": [
      "Accurate category and environment fields."
    ],
    "exceptions": [
      "Security inquiries have a separate macro.",
      "Free-user billing cases differ from technical support."
    ],
    "context_constraints": [
      "Zendesk forms and support entitlement policy"
    ],
    "structural_motifs": [
      "Classification",
      "Entitlement gate",
      "Missing-information repair"
    ],
    "candidate_midlevel_pattern": "Route an intake request using eligibility and context checks",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A facilities desk could separate covered repairs from external responsibilities.",
    "transfer_limit": "Eligibility errors can deny service; transfer needs local policy and review.",
    "unknowns": [
      "Routing accuracy",
      "Ambiguous entitlement resolution"
    ],
    "evidence_locator": "Applying the Correct Form; Handling Free User tickets",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "answering questions",
      "data analysis"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-07-29",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/support/workflows/ticket_triage/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-07-29. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "customer service/success"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Routing accuracy",
        "Ambiguous entitlement resolution",
        "Eligibility errors can deny service; transfer needs local policy and review."
      ]
    },
    "eligibility_register_id": "svc-07"
  },
  {
    "id": "svc-08",
    "title": "Coordinate an account escalation through agreed closure",
    "function": "customer service/success",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/customer-experience/csm/escalations/",
    "source_title": "Customer Success Escalations Process",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "A designated owner coordinates a cross-team account problem with explicit exit criteria.",
    "steps": [
      "Choose the escalation owner.",
      "Create or review the escalation case and communication channel.",
      "Specify immediate needs and exit criteria.",
      "Set an internal update cadence.",
      "Maintain next steps, owners and customer updates.",
      "Obtain documented customer and internal agreement before closure."
    ],
    "inputs": [
      "Account problem",
      "Customer impact"
    ],
    "outputs": [
      "Escalation case",
      "Owned actions",
      "Closure record"
    ],
    "decision_points": [
      "Account escalation or ticket-priority request?"
    ],
    "quality_checks": [
      "Exit criteria and owners stay current.",
      "Both parties agree on resolution."
    ],
    "exceptions": [
      "Separate simultaneous issues may require separate escalations."
    ],
    "context_constraints": [
      "Cadence depends on severity; public-sector updates have manual exceptions."
    ],
    "structural_motifs": [
      "Cross-team orchestration",
      "Exit criteria",
      "Bilateral closure"
    ],
    "candidate_midlevel_pattern": "Coordinate a multi-owner exception until stakeholders accept resolution",
    "transfer_example_explicitly_hypothetical": "Hypothetical: An administrator could coordinate a delayed onboarding spanning several departments.",
    "transfer_limit": "Urgency and communication rights must be adapted.",
    "unknowns": [
      "Real resolution duration",
      "Effect of cadence"
    ],
    "evidence_locator": "Initiating, Managing and Closing an Escalation",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "meeting distillation/action items",
      "content generation"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-09-24",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/customer-experience/csm/escalations/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-09-24. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "customer service/success"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Real resolution duration",
        "Effect of cadence",
        "Urgency and communication rights must be adapted."
      ]
    },
    "eligibility_register_id": "svc-08"
  },
  {
    "id": "svc-09",
    "title": "Respond to a customer emergency",
    "function": "customer service/success",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/support/workflows/customer_emergencies_workflows/",
    "source_title": "How to Perform Customer Emergencies Duties",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "On-call support validates an emergency, engages the customer and chooses a recovery path.",
    "steps": [
      "Acknowledge the page.",
      "Check entitlement and business impact.",
      "Contact the customer and communicate the next update.",
      "Collect logs, configuration and recent changes.",
      "Find a recovery or workaround path.",
      "Close, reconvene or seek help according to progress."
    ],
    "inputs": [
      "Emergency ticket",
      "Operational evidence"
    ],
    "outputs": [
      "Recovery path",
      "Customer updates"
    ],
    "decision_points": [
      "Emergency, exception, more information or downgrade?"
    ],
    "quality_checks": [
      "Contact customer before resolving the alert."
    ],
    "exceptions": [
      "No customer response can lead to downgrade.",
      "Public incidents may not warrant a call."
    ],
    "context_constraints": [
      "On-call ownership and response obligations"
    ],
    "structural_motifs": [
      "Time-critical triage",
      "Diagnostic branching",
      "Explicit fallback"
    ],
    "candidate_midlevel_pattern": "Stabilize an urgent exception through impact-led diagnosis and communication",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A venue coordinator could apply the communication structure to a last-minute operational failure.",
    "transfer_limit": "Software recovery actions and entitlement rules do not transfer.",
    "unknowns": [
      "Outcome rates",
      "Detailed technical diagnosis for individual incidents"
    ],
    "evidence_locator": "Stages 1–5; Triage the emergency request",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "answering questions"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-09-24",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/support/workflows/customer_emergencies_workflows/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-09-24. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "customer service/success"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P06",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Outcome rates",
        "Detailed technical diagnosis for individual incidents",
        "Software recovery actions and entitlement rules do not transfer."
      ]
    },
    "eligibility_register_id": "svc-09"
  },
  {
    "id": "svc-10",
    "title": "Turn customer feedback into prioritized improvements",
    "function": "customer service/success",
    "organization": "Cars Commerce",
    "sector": "Automotive marketplace services",
    "source_url": "https://www.helpscout.com/blog/customer-feedback/",
    "source_title": "How To Collect and Act on Customer Service Feedback",
    "accessed_date": "2026-10-18",
    "source_type": "First-party practitioner account",
    "evidence_status": "practitioner-reported",
    "implementation_type": "Human-led procedure",
    "summary": "A support leader describes linking feedback to cases and combining it with sales observations to prioritize fixes.",
    "steps": [
      "Associate CSAT feedback with CRM case context.",
      "Group feedback by issue and customer segment.",
      "Assess recurrence, urgency and responsible department.",
      "Review recurring pain points with sales directors.",
      "Collaborate on fixes and communicate changes."
    ],
    "inputs": [
      "CSAT comments",
      "Support case metadata",
      "Sales observations"
    ],
    "outputs": [
      "Prioritized improvements",
      "Coaching context"
    ],
    "decision_points": [
      "Support fix or cross-functional issue?",
      "Pattern or isolated noise?"
    ],
    "quality_checks": [
      "Interpret scores alongside comments and case context."
    ],
    "exceptions": [
      "Some feedback is not actionable."
    ],
    "context_constraints": [
      "Monthly cross-functional review described"
    ],
    "structural_motifs": [
      "Evidence aggregation",
      "Segmentation",
      "Feedback closure"
    ],
    "candidate_midlevel_pattern": "Turn repeated experience signals into owned improvement priorities",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A university administration team could aggregate service-desk feedback to improve enrollment guidance.",
    "transfer_limit": "Self-reported process; no causal evidence that the method produced a particular improvement.",
    "unknowns": [
      "Full prioritization rubric",
      "Implementation lead time"
    ],
    "evidence_locator": "Categorize and prioritize; Identify cross-functional opportunities; close the loop",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "data analysis"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": "2025-10-20",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.helpscout.com/blog/customer-feedback/",
      "evidence_note": "Original page's article header/byline displays 2025-10-20; treated as the displayed article publication date. No distinct last-updated date found in retrieved text.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_published_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "customer service/success"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P07",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Cars Commerce practitioner describes support-feedback practices on Help Scout’s blog; distinguish these from adjacent Help Scout product recommendations.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Full prioritization rubric",
        "Implementation lead time",
        "Self-reported process; no causal evidence that the method produced a particular improvement."
      ]
    },
    "eligibility_register_id": "svc-10"
  },
  {
    "id": "svc-12",
    "title": "Investigate a service complaint and communicate findings",
    "function": "customer service/success",
    "organization": "Parliamentary and Health Service Ombudsman",
    "sector": "Public healthcare complaint administration",
    "source_url": "https://www.ombudsman.org.uk/sites/default/files/MCHP_NHS_CS_Dec_2022.pdf",
    "source_title": "Model complaint handling procedure: NHS Complaint Standards",
    "accessed_date": "2026-10-18",
    "source_type": "Public ombudsman model procedure",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "A model procedure links investigation evidence, response to affected parties and possible remedies.",
    "steps": [
      "Investigate the complaint.",
      "Discuss findings and proposed action with key parties.",
      "Consider their comments.",
      "Assess impact where something went wrong.",
      "Determine a suitable remedy.",
      "Coordinate a signed written response explaining evidence and outcome."
    ],
    "inputs": [
      "Complaint",
      "Investigation evidence",
      "Party comments"
    ],
    "outputs": [
      "Reasoned response",
      "Remedy where warranted"
    ],
    "decision_points": [
      "Did something go wrong?",
      "Can the impact be put right?"
    ],
    "quality_checks": [
      "Consider comments before final response.",
      "Responsible person or delegate signs."
    ],
    "exceptions": [
      "Remedies vary when direct restoration is impossible."
    ],
    "context_constraints": [
      "Model procedure for NHS organisations; not proof of local implementation"
    ],
    "structural_motifs": [
      "Evidence-to-finding",
      "Right of response",
      "Authorized release"
    ],
    "candidate_midlevel_pattern": "Produce a reviewable finding and remedy from a contested service record",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A membership organisation could use a similar evidence-and-response structure for complaints.",
    "transfer_limit": "Healthcare law, confidentiality and remedy authority cannot be copied into another context.",
    "unknowns": [
      "Local adoption",
      "Actual case outcomes",
      "Current superseding procedure",
      "Publication date independently verified from document text or official listing"
    ],
    "evidence_locator": "Sections 8.25–8.28",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "content generation",
      "data analysis"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_date_indicated": "2022-12",
    "source_date_provenance": "Month and year encoded in the PDF filename MCHP_NHS_CS_Dec_2022.pdf; no publication date verified in extracted document text.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2022-12",
      "other_date_type": "filename_indicated_month",
      "evidence_url": "https://www.ombudsman.org.uk/sites/default/files/MCHP_NHS_CS_Dec_2022.pdf",
      "evidence_note": "Original PDF reopened; filename MCHP_NHS_CS_Dec_2022.pdf indicates December 2022. No publication or revision date verified in extracted PDF text; text search for 2022 returns no match. The filename hint is not a verified publication date.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "filename_hint_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "customer service/success"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P06",
        "P03"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Local adoption",
        "Actual case outcomes",
        "Current superseding procedure",
        "Publication date independently verified from document text or official listing",
        "Healthcare law, confidentiality and remedy authority cannot be copied into another context."
      ]
    },
    "eligibility_register_id": "svc-12"
  },
  {
    "id": "svc-13",
    "title": "Define a role before assessing applicants",
    "function": "people/HR",
    "organization": "Buffer",
    "sector": "Social media software",
    "source_url": "https://buffer.com/resources/hiring-process/",
    "source_title": "How We Hire: A Look Inside Our Hiring Process",
    "accessed_date": "2026-10-18",
    "source_type": "First-party practitioner account",
    "evidence_status": "practitioner-reported",
    "implementation_type": "Human-led procedure",
    "summary": "A hiring team writes goals and assessment criteria before opening the role.",
    "steps": [
      "Discuss business need, outcomes and skills asynchronously.",
      "Record early and longer-term success expectations.",
      "Identify hiring participants and commitments.",
      "Hold a kickoff meeting.",
      "Use the shared criteria to prepare the job description and evaluations."
    ],
    "inputs": [
      "Business need",
      "Team input"
    ],
    "outputs": [
      "Role definition",
      "Assessment criteria"
    ],
    "decision_points": [
      "What would successful performance look like?"
    ],
    "quality_checks": [
      "Common criteria support consistent evaluation."
    ],
    "exceptions": [],
    "context_constraints": [
      "Historical account, explicitly presented as evolving"
    ],
    "structural_motifs": [
      "Criteria before evaluation",
      "Shared specification"
    ],
    "candidate_midlevel_pattern": "Agree outcome-based criteria before collecting comparative evidence",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A procurement team could define vendor success criteria before reviewing bids.",
    "transfer_limit": "Hiring fairness and lawful criteria need specialist judgment.",
    "unknowns": [
      "Current process",
      "Actual bias reduction"
    ],
    "evidence_locator": "Step 1: Think and write",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "content generation"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": "2018-03-14",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://buffer.com/resources/hiring-process/",
      "evidence_note": "Original page's article header/byline displays 2018-03-14; treated as the displayed article publication date. No distinct last-updated date found in retrieved text.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_published_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "people/HR"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P03",
        "P10"
      ],
      "split": "held-out",
      "fit": "qualified",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Current process",
        "Actual bias reduction",
        "Hiring fairness and lawful criteria need specialist judgment."
      ]
    },
    "eligibility_register_id": "svc-13"
  },
  {
    "id": "svc-14",
    "title": "Prepare a candidate-facing question guide",
    "function": "people/HR",
    "organization": "Buffer",
    "sector": "Social media software",
    "source_url": "https://buffer.com/resources/buffer-q-a-doc/",
    "source_title": "We Send A Q&A Doc To Candidates Before We Meet Them: Here’s Why and How",
    "accessed_date": "2026-10-18",
    "source_type": "First-party practitioner account",
    "evidence_status": "practitioner-reported",
    "implementation_type": "Human-led procedure",
    "summary": "A hiring manager prepares a role-specific question-and-answer document before first interviews.",
    "steps": [
      "Identify common questions and likely unspoken concerns.",
      "Dictate explanations in a conversational style.",
      "Shape them into a role-specific document.",
      "Send the document with the first-interview invitation.",
      "Use interview transcripts to incorporate useful candidate questions and the answers given into the guide."
    ],
    "inputs": [
      "Recurring candidate questions",
      "Role and team details",
      "Interview transcripts containing new candidate questions and answers"
    ],
    "outputs": [
      "Pre-interview Q&A document"
    ],
    "decision_points": [
      "What is distinctive about this role?"
    ],
    "quality_checks": [],
    "exceptions": [],
    "context_constraints": [
      "First-interview preparation; adoption began in engineering"
    ],
    "structural_motifs": [
      "Anticipatory explanation",
      "Reusable context"
    ],
    "candidate_midlevel_pattern": "Answer recurring contextual questions before a high-value conversation",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A project coordinator could send stakeholders an orientation brief before kickoff.",
    "transfer_limit": "No formal approval process or fixed maintenance cadence is established.",
    "unknowns": [
      "Fixed maintenance cadence",
      "Formal factual approval process",
      "Measured interview impact"
    ],
    "evidence_locator": "How this works; How I put it together, including transcript-based updates",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "answering questions",
      "content generation"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": "2026-07-28",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://buffer.com/resources/buffer-q-a-doc/",
      "evidence_note": "Original page's article header/byline displays 2026-07-28; treated as the displayed article publication date. No distinct last-updated date found in retrieved text.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_published_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "maintenance_claim_type": "Practitioner-reported implementation; no fixed schedule stated",
    "functions": [
      "people/HR"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P03"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Fixed maintenance cadence",
        "Formal factual approval process",
        "Measured interview impact",
        "No formal approval process or fixed maintenance cadence is established."
      ]
    },
    "eligibility_register_id": "svc-14"
  },
  {
    "id": "svc-15",
    "title": "Reconcile independent performance reviews",
    "function": "people/HR",
    "organization": "Buffer",
    "sector": "Social media software",
    "source_url": "https://buffer.com/resources/performance-reviews-mixed-feelings/",
    "source_title": "How We Run Performance Reviews At Buffer And Why I Have Mixed Feelings About Them",
    "accessed_date": "2026-10-18",
    "source_type": "First-party practitioner account",
    "evidence_status": "practitioner-reported",
    "implementation_type": "Human-led procedure",
    "summary": "Teammates and managers write separate reviews, then discuss them and calibrate promotion recommendations.",
    "steps": [
      "Teammate completes a self-review.",
      "Manager writes before reading the self-review.",
      "Manager checks the self-review for omissions.",
      "Larger teams calibrate evaluations and promotions.",
      "Department head makes the final promotion decision.",
      "Manager and teammate discuss the review live.",
      "Send promotion decisions to Finance."
    ],
    "inputs": [
      "Role expectations",
      "Self-review",
      "Manager evidence"
    ],
    "outputs": [
      "Discussed review",
      "Promotion recommendation or decision"
    ],
    "decision_points": [
      "Is a promotion warranted?",
      "Department head retains final promotion authority."
    ],
    "quality_checks": [
      "The author describes independent manager drafting as intended to avoid influence from the self-review; no measured effect is established.",
      "The author describes cross-manager calibration as aiming for consistency; no measured fairness or consistency gain is established."
    ],
    "exceptions": [
      "New starters are excluded; leave is handled case by case."
    ],
    "context_constraints": [
      "Twice-yearly process described in 2023"
    ],
    "structural_motifs": [
      "Independent assessments",
      "Reconciliation",
      "Calibration"
    ],
    "candidate_midlevel_pattern": "Reconcile independent judgments against common criteria",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A review panel could independently score project proposals before discussing differences.",
    "transfer_limit": "Employment consequences and private personnel data require stronger safeguards than ordinary document synthesis.",
    "unknowns": [
      "Measured fairness",
      "Current process",
      "All calibration details"
    ],
    "evidence_locator": "Logistics; How long performance reviews take",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "data analysis",
      "meeting distillation/action items"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "quality_checks_claim_type": "Practitioner-reported process and intended benefits; not measured effectiveness",
    "source_dates": {
      "published": "2023-08-10",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://buffer.com/resources/performance-reviews-mixed-feelings/",
      "evidence_note": "Original page's article header/byline displays 2023-08-10; treated as the displayed article publication date. No distinct last-updated date found in retrieved text.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_published_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "people/HR"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P07"
      ],
      "split": "held-out",
      "fit": "qualified",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Measured fairness",
        "Current process",
        "All calibration details",
        "Employment consequences and private personnel data require stronger safeguards than ordinary document synthesis."
      ]
    },
    "eligibility_register_id": "svc-15"
  },
  {
    "id": "svc-16",
    "title": "Track onboarding obligations to closure",
    "function": "people/HR",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/people-group/general-onboarding/",
    "source_title": "GitLab Onboarding",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "A shared issue distributes general and role-specific onboarding work and supports compliance follow-up.",
    "steps": [
      "Create the onboarding issue before the start date.",
      "Assign manager and People Operations tasks.",
      "New starter completes general and role-specific tasks.",
      "Use buddy or team support where needed.",
      "Audit open issues monthly.",
      "Follow up on outstanding tasks and close the issue."
    ],
    "inputs": [
      "Onboarding template",
      "Role and start date"
    ],
    "outputs": [
      "Completed checklist",
      "Follow-up requests"
    ],
    "decision_points": [
      "Completed or not applicable?"
    ],
    "quality_checks": [
      "Monthly audit checks tasks and compliance obligations."
    ],
    "exceptions": [
      "Temporary service-provider onboarding belongs to Procurement."
    ],
    "context_constraints": [
      "General tasks have a 30-day due date; bot closes issues after 60 days."
    ],
    "structural_motifs": [
      "Role-specific checklist",
      "Distributed ownership",
      "Completion audit"
    ],
    "candidate_midlevel_pattern": "Coordinate a time-bounded transition with auditable obligations",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A membership service could track new-member setup across departments.",
    "transfer_limit": "Automatic closure is not evidence of actual completion.",
    "unknowns": [
      "Audit exception outcomes",
      "Completion quality"
    ],
    "evidence_locator": "Managers; Compliance; Completing Onboarding Issue",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "meeting distillation/action items"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-09-13",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/people-group/general-onboarding/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-09-13. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "people/HR"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P10"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Audit exception outcomes",
        "Completion quality",
        "Automatic closure is not evidence of actual completion."
      ]
    },
    "eligibility_register_id": "svc-16"
  },
  {
    "id": "svc-17",
    "title": "Coordinate a voluntary departure and access closure",
    "function": "people/HR",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/people-group/offboarding/",
    "source_title": "GitLab Offboarding",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "The voluntary departure workflow separates employment records, communication planning and access deprovisioning.",
    "steps": [
      "Discuss handover and communication with the manager.",
      "Submit resignation in Workday.",
      "Manager completes termination details.",
      "People partner reviews dates and details.",
      "Provide the offboarding packet.",
      "Open the offboarding issue at the end of work.",
      "Audit completion of deprovisioning tasks."
    ],
    "inputs": [
      "Resignation",
      "Last working date",
      "System access inventory"
    ],
    "outputs": [
      "Employment record",
      "Offboarding checklist"
    ],
    "decision_points": [
      "Are termination details ready for approval?"
    ],
    "quality_checks": [
      "Weekly audit; checklist records revocation or non-applicability."
    ],
    "exceptions": [
      "Country-specific requirements differ.",
      "Date changes require record updates."
    ],
    "context_constraints": [
      "Workday termination alone does not revoke access."
    ],
    "structural_motifs": [
      "State transition",
      "Cross-system synchronization",
      "Audit trail"
    ],
    "candidate_midlevel_pattern": "Synchronize a status change across records, people and access obligations",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A project closeout could coordinate archive, ownership transfer and access removal.",
    "transfer_limit": "Employment decisions and access revocation require authorized human control.",
    "unknowns": [
      "Current jurisdictional requirements",
      "Actual audit compliance"
    ],
    "evidence_locator": "Voluntary resignation; Termination; Offboarding Compliance",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "meeting distillation/action items"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-09-13",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/people-group/offboarding/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-09-13. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "people/HR"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P10",
        "P11"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Current jurisdictional requirements",
        "Actual audit compliance",
        "Employment decisions and access revocation require authorized human control."
      ]
    },
    "eligibility_register_id": "svc-17"
  },
  {
    "id": "svc-18",
    "title": "Evaluate a realistic work sample with feedback",
    "function": "people/HR",
    "organization": "Automattic",
    "sector": "Publishing and commerce software",
    "source_url": "https://automattic.com/work-with-us/",
    "source_title": "Work With Us",
    "accessed_date": "2026-10-18",
    "source_type": "First-party hiring process documentation",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "Some candidates complete a practical test or work trial before a final hiring recommendation.",
    "steps": [
      "Select the role-appropriate test or trial.",
      "Candidate completes realistic work with hiring-team feedback.",
      "Assess problem solving, design and communication.",
      "Prepare a recommendation including feedback and work summary.",
      "Seek final approval."
    ],
    "inputs": [
      "Candidate work sample",
      "Hiring-team feedback"
    ],
    "outputs": [
      "Evaluation packet",
      "Hiring recommendation"
    ],
    "decision_points": [
      "Test or longer trial for this role?"
    ],
    "quality_checks": [
      "Evaluation emphasizes working approach rather than platform trivia."
    ],
    "exceptions": [
      "Hiring steps differ by role."
    ],
    "context_constraints": [
      "Trials can involve up to 20 hours of work."
    ],
    "structural_motifs": [
      "Situated assessment",
      "Feedback loop",
      "Evidence packet"
    ],
    "candidate_midlevel_pattern": "Evaluate capability through a bounded work sample",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A vendor pilot could evaluate working practices before a broader engagement.",
    "transfer_limit": "Employment selection needs fair access, accommodations and lawful review.",
    "unknowns": [
      "Scoring rubric",
      "Inter-rater reliability",
      "Compensation terms for each test"
    ],
    "evidence_locator": "Practical test or trial; Final review and offer",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "data analysis"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://automattic.com/work-with-us/",
      "evidence_note": "Original source page retrieved and inspected for article-level publication/update dates. No publication or last-updated date established from rendered text. Copyright years, linked article dates, relative search dates and crawl dates are excluded.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "not_found"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "people/HR"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P09",
        "P07"
      ],
      "split": "held-out",
      "fit": "direct",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Scoring rubric",
        "Inter-rater reliability",
        "Compensation terms for each test",
        "Employment selection needs fair access, accommodations and lawful review."
      ]
    },
    "eligibility_register_id": "svc-18"
  },
  {
    "id": "svc-19",
    "title": "Turn a retrospective into assigned improvements",
    "function": "administration/project coordination",
    "organization": "UK Government Digital Service",
    "sector": "Public digital services",
    "source_url": "https://www.gov.uk/service-manual/agile-delivery/agile-tools-techniques",
    "source_title": "Agile tools and techniques",
    "accessed_date": "2026-10-18",
    "source_type": "Government service manual",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "A facilitated retrospective elicits team experience and assigns fixes before the next cycle.",
    "steps": [
      "Choose broad discussion questions.",
      "Each person records responses.",
      "Discuss issues together.",
      "Choose improvement actions.",
      "Assign actions to team members.",
      "Aim to complete them before the next retrospective."
    ],
    "inputs": [
      "Recent work experience",
      "Team observations"
    ],
    "outputs": [
      "Assigned improvement list"
    ],
    "decision_points": [
      "Which problems should be addressed?"
    ],
    "quality_checks": [
      "Open atmosphere lets all participants contribute."
    ],
    "exceptions": [
      "End-of-phase reviews may include external disciplines."
    ],
    "context_constraints": [
      "Regular iteration-based meetings"
    ],
    "structural_motifs": [
      "Independent input",
      "Collective interpretation",
      "Commitment extraction"
    ],
    "candidate_midlevel_pattern": "Convert collective reflection into owned improvement commitments",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A sales team could review a campaign and assign process changes.",
    "transfer_limit": "An action list without follow-through is not evidence of improvement.",
    "unknowns": [
      "Action completion rate",
      "Specific facilitation conflicts"
    ],
    "evidence_locator": "Retrospective meetings; Make a list of actions",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "meeting distillation/action items"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": "2016-02-16",
      "updated": "2026-03-31",
      "other_date": "2016-01-05",
      "other_date_type": "conflicting_first_publication_history_entry",
      "evidence_url": "https://www.gov.uk/service-manual/agile-delivery/agile-tools-techniques",
      "evidence_note": "Original GOV.UK Updates to this page labels Published: 16 February 2016 and Last updated: 31 March 2026. The same history lists 5 January 2016 as Guidance first published. Both indicators are preserved; original publication conflict remains unresolved.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_dates_with_publication_conflict"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "administration/project coordination"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P01",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Action completion rate",
        "Specific facilitation conflicts",
        "An action list without follow-through is not evidence of improvement."
      ]
    },
    "eligibility_register_id": "svc-19"
  },
  {
    "id": "svc-20",
    "title": "Maintain an evidence-informed roadmap",
    "function": "administration/project coordination",
    "organization": "UK Government Digital Service",
    "sector": "Public digital services",
    "source_url": "https://www.gov.uk/service-manual/agile-delivery/developing-a-roadmap",
    "source_title": "Developing a roadmap",
    "accessed_date": "2026-10-18",
    "source_type": "Government service manual",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "Teams collaboratively update a roadmap that connects a service vision to measurable iterations.",
    "steps": [
      "Start with the service vision.",
      "Use research and performance evidence with stakeholders.",
      "Define iteration objectives and progress measures.",
      "Order work using a transparent prioritization method.",
      "Maintain a master version.",
      "Review and update regularly."
    ],
    "inputs": [
      "Vision",
      "User research",
      "Performance analysis"
    ],
    "outputs": [
      "Prioritized roadmap"
    ],
    "decision_points": [
      "Which iterations deliver value next?"
    ],
    "quality_checks": [
      "Keep alternate versions synchronized.",
      "Use clear language."
    ],
    "exceptions": [
      "Security or political sensitivity can restrict publication."
    ],
    "context_constraints": [
      "GDS describes at least quarterly iteration."
    ],
    "structural_motifs": [
      "Evidence-informed sequencing",
      "Version authority"
    ],
    "candidate_midlevel_pattern": "Translate a strategic objective into a revisable sequence of outcomes",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A nonprofit could map service improvements against observed beneficiary needs.",
    "transfer_limit": "Do not treat provisional roadmap dates as delivery guarantees.",
    "unknowns": [
      "Specific prioritization method",
      "Outcome results"
    ],
    "evidence_locator": "Roadmap principles",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "data analysis",
      "content generation"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": "2017-11-16",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.gov.uk/service-manual/agile-delivery/developing-a-roadmap",
      "evidence_note": "Original GOV.UK page explicitly labels Published: 16 November 2017. No last-updated field appears in retrieved text.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_published_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "administration/project coordination"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P07",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Specific prioritization method",
        "Outcome results",
        "Do not treat provisional roadmap dates as delivery guarantees."
      ]
    },
    "eligibility_register_id": "svc-20"
  },
  {
    "id": "svc-22",
    "title": "Map dependencies and assign review loops",
    "function": "administration/project coordination",
    "organization": "Atlassian",
    "sector": "Collaboration software",
    "source_url": "https://www.atlassian.com/team-playbook/plays/dependency-mapping",
    "source_title": "Dependency Mapping",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public team playbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "A project team identifies affected systems, risks and recurring stakeholder feedback.",
    "steps": [
      "List upstream and downstream systems.",
      "Record owners and impacts.",
      "Independently brainstorm risks, then discuss.",
      "Agree impact levels and mitigations.",
      "Assign owners and stakeholder review cadence.",
      "Share the map for corrections and revisit it."
    ],
    "inputs": [
      "Project scope",
      "Team knowledge"
    ],
    "outputs": [
      "Dependency map",
      "Risk actions"
    ],
    "decision_points": [
      "Which risks need mitigation or more research?"
    ],
    "quality_checks": [
      "Stakeholders can correct omissions.",
      "Every risk has an owner."
    ],
    "exceptions": [
      "Expand documentation when the worksheet is insufficient."
    ],
    "context_constraints": [
      "Time-boxed collaborative workshop"
    ],
    "structural_motifs": [
      "Relationship mapping",
      "Risk ownership",
      "Recurring verification"
    ],
    "candidate_midlevel_pattern": "Map interdependencies into owned risks and feedback commitments",
    "transfer_example_explicitly_hypothetical": "Hypothetical: An HR team could map dependencies for a relocation program.",
    "transfer_limit": "A diagram does not verify that counterpart teams have accepted obligations.",
    "unknowns": [
      "Observed dependency failures",
      "Acceptance protocol"
    ],
    "evidence_locator": "Instructions; Follow-up",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "data analysis",
      "meeting distillation/action items"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.atlassian.com/team-playbook/plays/dependency-mapping",
      "evidence_note": "Original source page retrieved and inspected for article-level publication/update dates. No publication or last-updated date established from rendered text. Copyright years, linked article dates, relative search dates and crawl dates are excluded.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "not_found"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "administration/project coordination"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P08",
        "P10"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Observed dependency failures",
        "Acceptance protocol",
        "A diagram does not verify that counterpart teams have accepted obligations."
      ]
    },
    "eligibility_register_id": "svc-22"
  },
  {
    "id": "svc-23",
    "title": "Review a purchase request through an approval queue",
    "function": "administration/project coordination",
    "organization": "GitLab",
    "sector": "Enterprise software",
    "source_url": "https://handbook.gitlab.com/handbook/business-technology/enterprise-applications/guides/zip-guide/",
    "source_title": "Zip End Users Guide",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public handbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human-led procedure",
    "summary": "Assigned reviewers examine their part of a purchase request and either decide or ask for missing context.",
    "steps": [
      "Open the assigned request.",
      "Review the relevant approval node.",
      "Complete required subtasks.",
      "Ask stakeholders for additional context when needed.",
      "Approve, reject or request more information."
    ],
    "inputs": [
      "Purchase request",
      "Supporting documents"
    ],
    "outputs": [
      "Approval outcome",
      "Information request"
    ],
    "decision_points": [
      "Is there enough evidence to decide?"
    ],
    "quality_checks": [
      "Complete node-specific checks before approval."
    ],
    "exceptions": [
      "Pending approvals can be reassigned.",
      "Out-of-office delegation can route work temporarily."
    ],
    "context_constraints": [
      "Only designated approval roles have decision rights."
    ],
    "structural_motifs": [
      "Queue-based review",
      "Scoped authority",
      "Missing-evidence loop"
    ],
    "candidate_midlevel_pattern": "Review a request at a scoped approval gate",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A grant administrator could organize eligibility and budget reviews into separate gates.",
    "transfer_limit": "Approval authority, financial limits and segregation of duties remain local.",
    "unknowns": [
      "Full approval matrix",
      "Actual compliance"
    ],
    "evidence_locator": "Zip - Approval Process",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "data analysis"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": "2026-05-27",
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://handbook.gitlab.com/handbook/business-technology/enterprise-applications/guides/zip-guide/",
      "evidence_note": "Original handbook footer explicitly states Last modified 2026-05-27. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "verified_updated_only"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "administration/project coordination"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P04"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Full approval matrix",
        "Actual compliance",
        "Approval authority, financial limits and segregation of duties remain local."
      ]
    },
    "eligibility_register_id": "svc-23"
  },
  {
    "id": "svc-24",
    "title": "Audit recent decisions to reduce avoidable delay",
    "function": "administration/project coordination",
    "organization": "Atlassian",
    "sector": "Collaboration software",
    "source_url": "https://www.atlassian.com/team-playbook/plays/decision-making-retro",
    "source_title": "Decision-Making Retro",
    "accessed_date": "2026-10-18",
    "source_type": "First-party public team playbook",
    "evidence_status": "documented-procedure",
    "implementation_type": "Human reflection with optional AI-assisted retrieval",
    "summary": "A person reviews recent decisions and clarifies where uncertainty, information or approval habits slowed progress.",
    "steps": [
      "List recent decisions and deferred decisions.",
      "Optionally use AI to scan a bounded work history and draft the table.",
      "Reflect on the source of uncertainty.",
      "Identify repeatable strengths and changes.",
      "Summarize reminders.",
      "Discuss with a manager to clarify future decision rights."
    ],
    "inputs": [
      "Recent work records",
      "Personal reflection"
    ],
    "outputs": [
      "Decision audit",
      "Future reminders"
    ],
    "decision_points": [
      "Was uncertainty about knowledge, consensus or authority?"
    ],
    "quality_checks": [
      "Review AI output against remembered friction."
    ],
    "exceptions": [
      "Useful after reorganizations or changes in management."
    ],
    "context_constraints": [
      "AI is optional and requires access to work context."
    ],
    "structural_motifs": [
      "Process reflection",
      "Authority clarification",
      "AI-assisted evidence gathering"
    ],
    "candidate_midlevel_pattern": "Audit decisions to distinguish missing evidence from unclear authority",
    "transfer_example_explicitly_hypothetical": "Hypothetical: A customer-service lead could review delayed exceptions to clarify escalation thresholds.",
    "transfer_limit": "Self-reflection cannot by itself grant permission or establish causal improvement.",
    "unknowns": [
      "Model and retrieval setup",
      "Independent effect of AI",
      "Actual adoption"
    ],
    "evidence_locator": "List recent decisions; Reflect on uncertainty; Reflect or share",
    "interpretation_boundary": "Summary, steps, inputs, outputs, decision points, quality checks, exceptions and context constraints summarize the cited source. Structural motifs, candidate pattern and transfer fields are analyst interpretations, not demonstrated transfer.",
    "tested_by_researcher": false,
    "entry_points": [
      "data analysis",
      "meeting distillation/action items"
    ],
    "entry_points_status": "Analyst navigation tags; nonexclusive and not a claim that AI is used.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.atlassian.com/team-playbook/plays/decision-making-retro",
      "evidence_note": "Original source page retrieved and inspected for article-level publication/update dates. No publication or last-updated date established from rendered text. Copyright years, linked article dates, relative search dates and crawl dates are excluded.",
      "checked_at": "2026-10-18T03:00:27Z",
      "status": "not_found"
    },
    "source_date_if_verified_note": "Legacy single date; use source_dates for publication versus update meaning, precision and provenance.",
    "functions": [
      "administration/project coordination"
    ],
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P06"
      ],
      "split": "training",
      "fit": "mapped",
      "coding_basis": "Exploratory analyst coding of collected source summaries; not independently tested"
    },
    "original_evidence_status": "documented-procedure",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "ordinary_documented_operating_procedure",
      "reason": "Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Model and retrieval setup",
        "Independent effect of AI",
        "Actual adoption",
        "Self-reflection cannot by itself grant permission or establish causal improvement."
      ]
    },
    "eligibility_register_id": "svc-24"
  },
  {
    "id": "XOPS-01",
    "title": "Toyota turns mail-arrival polling into shared ownership",
    "organization": "Toyota",
    "geography": "Japan",
    "function": "operations/coordination",
    "functions": [
      "operations/coordination"
    ],
    "sector": "Manufacturing",
    "source_url": "https://toyotatimes.jp/en/series/Imaginative_and_creative/003.html",
    "source_title": "Transforming Administrative Tasks--Digital Notifications for Internal Mail",
    "accessed_date": "2026-10-18",
    "source_type": "First-party staff interview",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "reported-rules-based-automation",
    "summary": "An operations employee replaced repeated cabinet checks with arrival notifications and voluntary collection.",
    "steps": [
      "Delivery staff lower a sensor-equipped sign when depositing mail",
      "A Teams notification announces arrival",
      "An available colleague claims collection through the message",
      "The system identifies the collector; the sign is reset after pickup"
    ],
    "inputs": [
      "Mail-arrival signal",
      "Collector response"
    ],
    "outputs": [
      "Shared arrival notice",
      "Visible collection ownership"
    ],
    "decision_points": [
      "Who is available to collect?"
    ],
    "quality_checks": [
      "Low-battery notification"
    ],
    "exceptions": [
      "Rechargeable prototype required office visits; a button was difficult to confirm"
    ],
    "context_constraints": [
      "Battery-powered setup; physical reset remains necessary"
    ],
    "structural_motifs": [
      "Replace polling with events",
      "Self-assigned ownership",
      "Visible acknowledgment"
    ],
    "candidate_midlevel_pattern": "Event-triggered shared-service coordination",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an office equipment team could replace repeated availability checks with arrival notices and visible voluntary claims.",
    "transfer_limit": "A claim is not proof of delivery; escalation for unclaimed work remains a design question.",
    "unknowns": [
      "Missed notification rate",
      "Reliability of completion status versus claim",
      "Measured time savings"
    ],
    "knowledge_work_boundary": "Arrival awareness and ownership allocation are included; sensor assembly and carrying mail are excluded.",
    "provenance_note": "Operational fields paraphrase the cited report, not independent observation or a recommended procedure. Unknown or unspecified controls are not filled in. Structural motifs, candidate pattern, transfer example, transfer limit, knowledge-work boundary and codebook challenge are analyst interpretations. Reported outcomes are not independently verified.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2025-03-04",
      "other_date_type": "displayed_article_date_type_unspecified",
      "evidence_url": "https://toyotatimes.jp/en/series/Imaginative_and_creative/003.html",
      "evidence_note": "Page displays 2025-03-04 without separately labeling publication versus update.",
      "checked_at": "2026-10-18T03:15:00Z",
      "status": "verified_displayed_date_type_unspecified"
    },
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P10"
      ],
      "partial_candidate_pattern_ids": [],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "codebook_challenge": "P10 partly fits, but replacing a task with an event and distributing previously invisible labor is more than tracking commitments.",
    "outcome_evidence_status": "Self-report only; no causal or independent validation established.",
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Missed notification rate",
        "Reliability of completion status versus claim",
        "Measured time savings",
        "A claim is not proof of delivery; escalation for unclaimed work remains a design question."
      ]
    },
    "eligibility_register_id": "XOPS-01",
    "expansion_classification": {
      "id": "XOPS-01",
      "record_kind": "new_case",
      "source_url": "https://toyotatimes.jp/en/series/Imaginative_and_creative/003.html",
      "fit": "partial",
      "matched_existing_pattern_ids": [
        "P10"
      ],
      "partial_candidate_pattern_ids": [],
      "not_supported_pattern_ids": [],
      "rationale": "Ownership notification and pickup/reset support coordination, but event replacement and redistribution of invisible labor exceed commitment tracking. A button claim is not independently verified completion.",
      "newly_needed_dimensions": [
        "event_visibility",
        "labor_ownership",
        "physical_execution"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "documented workflow",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source account gives a coherent workflow with explicit stages, dependencies or checkpoints; documented means documented in the source, not independently observed or validated.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "dataset_role": "qualified_workflow_or_practice"
  },
  {
    "id": "XOPS-04",
    "title": "DHL turns booking correspondence into shipment records",
    "organization": "DHL Global Forwarding, Freight",
    "geography": "Global operation; Germany-headquartered",
    "function": "operations/booking administration",
    "functions": [
      "operations/booking administration"
    ],
    "sector": "Logistics",
    "source_url": "https://group.dhl.com/content/dam/deutschepostdhl/de/media-center/investors/documents/capital-markets-days/DHL-Group-DGFF-Capital-Market-Briefing-London-March-2026.pdf",
    "source_title": "Capital Market Briefing: Update Oscar de Bok, slide 13",
    "accessed_date": "2026-10-18",
    "source_type": "First-party investor presentation",
    "evidence_status": "organization-reported",
    "workflow_mode": "reported-ai-practice",
    "summary": "DHL reports extracting and structuring booking information before validation and shipment-record creation.",
    "steps": [
      "Extract fields from emails, documents and attachments",
      "Structure data for entry",
      "Validate with a human in the loop",
      "Push data into CW1 to create or enrich shipment records"
    ],
    "inputs": [
      "Booking correspondence",
      "Customer-specific CW1 rules"
    ],
    "outputs": [
      "Structured booking fields",
      "Created or enriched shipment record"
    ],
    "decision_points": [
      "Is extracted information valid for entry?"
    ],
    "quality_checks": [
      "Human-in-loop validation"
    ],
    "exceptions": [
      "Exception routing not described"
    ],
    "context_constraints": [
      "Air and ocean freight; investor presentation reports 40% productivity gain without study details"
    ],
    "structural_motifs": [
      "Unstructured-to-structured conversion",
      "System-of-record update"
    ],
    "candidate_midlevel_pattern": "Convert correspondence into validated operational records",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an events team could extract registration correspondence into a staging record before staff validation.",
    "transfer_limit": "Parsing accuracy and permission to write to the destination system must be separately established.",
    "unknowns": [
      "Validation coverage",
      "Error rates",
      "Production scope",
      "Customer-rule implementation"
    ],
    "knowledge_work_boundary": "Administrative booking-data preparation is included; freight movement and pricing authority are excluded.",
    "provenance_note": "Operational fields paraphrase the cited report, not independent observation or a recommended procedure. Unknown or unspecified controls are not filled in. Structural motifs, candidate pattern, transfer example, transfer limit, knowledge-work boundary and codebook challenge are analyst interpretations. Reported outcomes are not independently verified.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2026-03-31",
      "other_date_type": "presentation_event_date",
      "evidence_url": "https://group.dhl.com/content/dam/deutschepostdhl/de/media-center/investors/documents/capital-markets-days/DHL-Group-DGFF-Capital-Market-Briefing-London-March-2026.pdf",
      "evidence_note": "Cover and slide 13 identify Capital Market Briefing, London, 31 March 2026. This is the presentation date; upload/publication date not established.",
      "checked_at": "2026-10-18T03:15:00Z",
      "status": "verified_event_date_only"
    },
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [],
      "split": "expansion_not_validation",
      "fit": "fit",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "codebook_challenge": "P03 fits transformation; P05 is only partial because independent reference checks are not specified.",
    "outcome_evidence_status": "Self-report only; no causal or independent validation established.",
    "original_evidence_status": "organization-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Validation coverage",
        "Error rates",
        "Production scope",
        "Customer-rule implementation",
        "Parsing accuracy and permission to write to the destination system must be separately established."
      ]
    },
    "eligibility_register_id": "XOPS-04",
    "expansion_classification": {
      "id": "XOPS-04",
      "record_kind": "new_case",
      "source_url": "https://group.dhl.com/content/dam/deutschepostdhl/de/media-center/investors/documents/capital-markets-days/DHL-Group-DGFF-Capital-Market-Briefing-London-March-2026.pdf",
      "fit": "fit",
      "matched_existing_pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [],
      "not_supported_pattern_ids": [
        "P05"
      ],
      "rationale": "Extracting booking fields into shipment records is artifact transformation. Human validation alone does not prove independent-reference reconciliation.",
      "newly_needed_dimensions": [
        "data_preparation",
        "authority_boundary"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "documented workflow",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source account gives a coherent workflow with explicit stages, dependencies or checkpoints; documented means documented in the source, not independently observed or validated.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "dataset_role": "qualified_workflow_or_practice"
  },
  {
    "id": "XOPS-07",
    "title": "Hilton Tokyo Bay uses waste evidence to revise preparation and purchasing",
    "organization": "Hilton Tokyo Bay",
    "geography": "Japan",
    "function": "operations/food planning",
    "functions": [
      "operations/food planning"
    ],
    "sector": "Hospitality",
    "source_url": "https://stories.hilton.com/apac/releases/savoring-sustainability-hotels-in-asia-pacific-tackling-food-waste",
    "source_title": "Hotels in Asia Pacific Tackling Food Waste",
    "accessed_date": "2026-10-18",
    "source_type": "First-party operating report",
    "evidence_status": "organization-reported",
    "workflow_mode": "reported-ai-practice",
    "summary": "Kitchen teams use daily waste data to understand excess preparation and change purchasing and ingredient use.",
    "steps": [
      "Measure daily food waste with Winnow",
      "Identify excess preparation and trimming opportunities",
      "Use insights to alter practices and buying decisions",
      "Repurpose suitable surplus ingredients"
    ],
    "inputs": [
      "Daily waste measurements"
    ],
    "outputs": [
      "Waste-source insights",
      "Revised preparation and purchasing choices"
    ],
    "decision_points": [
      "Where can preparation or buying change?"
    ],
    "quality_checks": [
      "Measurement method and validation not specified"
    ],
    "exceptions": [
      "Report offers leftover croissants becoming bread pudding as an example"
    ],
    "context_constraints": [
      "Adopted at Tokyo Bay from January 2020; reported reductions are company claims"
    ],
    "structural_motifs": [
      "Physical feedback informs planning",
      "Continuous resource adjustment"
    ],
    "candidate_midlevel_pattern": "Use operational loss measurements to revise the next production plan",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a print room could use discarded-job measurements to revise batch sizes and material purchasing.",
    "transfer_limit": "Waste reduction must not compromise service quality or safety; causal attribution requires a comparison.",
    "unknowns": [
      "Baseline comparability",
      "Waste recognition accuracy",
      "Decision cadence",
      "Independent savings verification"
    ],
    "knowledge_work_boundary": "Interpreting measurements and changing plans are included; cooking and disposal labor are excluded.",
    "provenance_note": "Operational fields paraphrase the cited report, not independent observation or a recommended procedure. Unknown or unspecified controls are not filled in. Structural motifs, candidate pattern, transfer example, transfer limit, knowledge-work boundary and codebook challenge are analyst interpretations. Reported outcomes are not independently verified.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2024-08-15",
      "other_date_type": "displayed_article_date_type_unspecified",
      "evidence_url": "https://stories.hilton.com/apac/releases/savoring-sustainability-hotels-in-asia-pacific-tackling-food-waste",
      "evidence_note": "News Releases header displays August 15, 2024; no separate update history established.",
      "checked_at": "2026-10-18T03:15:00Z",
      "status": "verified_displayed_date_type_unspecified"
    },
    "aliases": [],
    "research_classification": {
      "pattern_ids": [],
      "partial_candidate_pattern_ids": [
        "P02",
        "P07"
      ],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "codebook_challenge": "Passive waste measurement is not P09 testing; the measure-adjust-repeat control loop lacks a clean standalone match.",
    "outcome_evidence_status": "Self-report only; no causal or independent validation established.",
    "original_evidence_status": "organization-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Baseline comparability",
        "Waste recognition accuracy",
        "Decision cadence",
        "Independent savings verification",
        "Waste reduction must not compromise service quality or safety; causal attribution requires a comparison."
      ]
    },
    "eligibility_register_id": "XOPS-07",
    "expansion_classification": {
      "id": "XOPS-07",
      "record_kind": "new_case",
      "source_url": "https://stories.hilton.com/apac/releases/savoring-sustainability-hotels-in-asia-pacific-tackling-food-waste",
      "fit": "partial",
      "matched_existing_pattern_ids": [],
      "partial_candidate_pattern_ids": [
        "P02",
        "P07"
      ],
      "not_supported_pattern_ids": [
        "P09"
      ],
      "rationale": "Waste evidence informs changes, but the account lacks a deliberate test and evaluated alternatives; passive measurement is not an experiment.",
      "newly_needed_dimensions": [
        "ongoing_adaptation",
        "physical_execution"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "reported practice with sufficient mechanics",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source supplies a bounded task, material inputs and outputs, and concrete transformations or feedback; all practice remains source-reported, not independently observed.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "dataset_role": "qualified_workflow_or_practice"
  },
  {
    "id": "XOPS-09",
    "title": "Singapore General Hospital reconciles daily service charges with exceptions",
    "organization": "Singapore General Hospital",
    "geography": "Singapore",
    "function": "finance/billing operations",
    "functions": [
      "finance/billing operations"
    ],
    "sector": "Healthcare administration",
    "source_url": "https://www.singhealth.com.sg/news/singapore-health/enhancing-patient-care-operations",
    "source_title": "Enhancing patient care operations",
    "accessed_date": "2026-10-18",
    "source_type": "First-party staff interviews",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "reported-rules-based-automation",
    "summary": "Pre-Admission Centre staff changed paper-based charging into daily automated checks and manual exception handling.",
    "steps": [
      "Generate a report of the previous day’s performed tests",
      "Check missing and duplicate billing",
      "Post eligible charges to accounts",
      "Flag charges that cannot be posted",
      "Staff check and post exceptions"
    ],
    "inputs": [
      "Performed-service records",
      "Billing accounts"
    ],
    "outputs": [
      "Posted charges",
      "Exception list"
    ],
    "decision_points": [
      "Can this charge be posted?"
    ],
    "quality_checks": [
      "Missed- and double-billing checks",
      "Manual exception review"
    ],
    "exceptions": [
      "Unpostable bills remain with staff"
    ],
    "context_constraints": [
      "Process redesign involved Finance and other departments; source reports fewer hours and no reported errors"
    ],
    "structural_motifs": [
      "Routine execution plus exception queue",
      "Cross-department process consolidation"
    ],
    "candidate_midlevel_pattern": "Reconcile completed services into charges with explicit residual work",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an equipment-rental office could reconcile completed hires to invoice drafts and review unmatched records.",
    "transfer_limit": "Automation of payment or billing still needs domain-specific authorization and dispute handling.",
    "unknowns": [
      "Error ascertainment method",
      "Reconciliation coverage",
      "Exception frequency",
      "System controls"
    ],
    "knowledge_work_boundary": "Administrative charge reconciliation only; ordering tests or judging their clinical necessity is excluded.",
    "provenance_note": "Operational fields paraphrase the cited report, not independent observation or a recommended procedure. Unknown or unspecified controls are not filled in. Structural motifs, candidate pattern, transfer example, transfer limit, knowledge-work boundary and codebook challenge are analyst interpretations. Reported outcomes are not independently verified.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2024-01-10",
      "other_date_type": "displayed_article_date_type_unspecified",
      "evidence_url": "https://www.singhealth.com.sg/news/singapore-health/enhancing-patient-care-operations",
      "evidence_note": "Page displays 2024-01-10 without separately labeling publication versus update.",
      "checked_at": "2026-10-18T03:15:00Z",
      "status": "verified_displayed_date_type_unspecified"
    },
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P05"
      ],
      "partial_candidate_pattern_ids": [
        "P06"
      ],
      "split": "expansion_not_validation",
      "fit": "fit",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "codebook_challenge": null,
    "outcome_evidence_status": "Self-report only; no causal or independent validation established.",
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Error ascertainment method",
        "Reconciliation coverage",
        "Exception frequency",
        "System controls",
        "Automation of payment or billing still needs domain-specific authorization and dispute handling."
      ]
    },
    "eligibility_register_id": "XOPS-09",
    "expansion_classification": {
      "id": "XOPS-09",
      "record_kind": "new_case",
      "source_url": "https://www.singhealth.com.sg/news/singapore-health/enhancing-patient-care-operations",
      "fit": "fit",
      "matched_existing_pattern_ids": [
        "P05"
      ],
      "partial_candidate_pattern_ids": [
        "P06"
      ],
      "not_supported_pattern_ids": [],
      "rationale": "Daily test records are compared with billing and discrepancies handled. Exception checking is supported but detailed causal diagnosis is not.",
      "newly_needed_dimensions": [
        "authority_boundary"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "documented workflow",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source account gives a coherent workflow with explicit stages, dependencies or checkpoints; documented means documented in the source, not independently observed or validated.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "dataset_role": "qualified_workflow_or_practice"
  },
  {
    "id": "XOPS-10",
    "title": "Singapore General Hospital turns fragmented bill enquiries into one service",
    "organization": "Singapore General Hospital",
    "geography": "Singapore",
    "function": "customer service/billing enquiries",
    "functions": [
      "customer service/billing enquiries"
    ],
    "sector": "Healthcare administration",
    "source_url": "https://www.singhealth.com.sg/news/Lighternotes/digital-first-counter-less-strategy-takes-shape-in-sgh",
    "source_title": "Digital-first, counter-less strategy takes shape in SGH",
    "accessed_date": "2026-10-18",
    "source_type": "First-party staff interview",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "conventional-workflow",
    "summary": "A former claims counter became a phone/email team handling broader billing enquiries in a shared Business Office.",
    "steps": [
      "Move counter enquiries to phone and email",
      "Expand staff knowledge beyond their former claims remit",
      "Train staff and supply a standard email template",
      "Combine billing enquiry responsibilities in the Business Office"
    ],
    "inputs": [
      "Patient billing enquiries",
      "Shared billing knowledge",
      "Email template"
    ],
    "outputs": [
      "Single-contact responses"
    ],
    "decision_points": [
      "How to clarify a billing enquiry remotely?"
    ],
    "quality_checks": [
      "Training and template supported clearer written responses"
    ],
    "exceptions": [
      "Staff lost access to body-language cues and initially struggled with email tone"
    ],
    "context_constraints": [
      "Change occurred in stages during 2019–2021"
    ],
    "structural_motifs": [
      "Consolidate fragmented demand",
      "Channel-specific communication learning",
      "Remove customer handoffs"
    ],
    "candidate_midlevel_pattern": "Consolidate service ownership while teaching the new communication medium",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an employee expenses team could consolidate fragmented enquiries and teach generalists a shared response framework.",
    "transfer_limit": "One contact point needs actual cross-domain competence; centralizing a queue alone can create bottlenecks.",
    "unknowns": [
      "Resolution time",
      "Escalation paths",
      "Patient satisfaction",
      "Exact template"
    ],
    "knowledge_work_boundary": "Knowledge sharing, response formulation and ownership design are included; no medical advice or patient case data is retained.",
    "provenance_note": "Operational fields paraphrase the cited report, not independent observation or a recommended procedure. Unknown or unspecified controls are not filled in. Structural motifs, candidate pattern, transfer example, transfer limit, knowledge-work boundary and codebook challenge are analyst interpretations. Reported outcomes are not independently verified.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2021-05-31",
      "other_date_type": "displayed_article_date_type_unspecified",
      "evidence_url": "https://www.singhealth.com.sg/news/Lighternotes/digital-first-counter-less-strategy-takes-shape-in-sgh",
      "evidence_note": "Page displays 2021-05-31 without separately labeling publication versus update.",
      "checked_at": "2026-10-18T03:15:00Z",
      "status": "verified_displayed_date_type_unspecified"
    },
    "aliases": [],
    "research_classification": {
      "pattern_ids": [],
      "partial_candidate_pattern_ids": [
        "P11"
      ],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "codebook_challenge": "P11 captures transition, but eliminating customer handoffs and widening staff competence are substantive redesign outcomes.",
    "outcome_evidence_status": "Self-report only; no causal or independent validation established.",
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Resolution time",
        "Escalation paths",
        "Patient satisfaction",
        "Exact template",
        "One contact point needs actual cross-domain competence; centralizing a queue alone can create bottlenecks."
      ]
    },
    "eligibility_register_id": "XOPS-10",
    "expansion_classification": {
      "id": "XOPS-10",
      "record_kind": "new_case",
      "source_url": "https://www.singhealth.com.sg/news/Lighternotes/digital-first-counter-less-strategy-takes-shape-in-sgh",
      "fit": "partial",
      "matched_existing_pattern_ids": [],
      "partial_candidate_pattern_ids": [
        "P11"
      ],
      "not_supported_pattern_ids": [
        "P03"
      ],
      "rationale": "Service consolidation and training describe transition, but continuity/verification details are sparse. A supplied email template does not establish an artifact-drafting workflow.",
      "newly_needed_dimensions": [
        "labor_ownership",
        "relationship_outcomes"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "reported practice with sufficient mechanics",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source supplies a bounded task, material inputs and outputs, and concrete transformations or feedback; all practice remains source-reported, not independently observed.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "dataset_role": "qualified_workflow_or_practice"
  },
  {
    "id": "XOPS-12",
    "title": "Mayo Clinic converts referral documents into a reviewed cover sheet",
    "organization": "Mayo Clinic",
    "geography": "United States: Phoenix and Rochester",
    "function": "operations/referral intake",
    "functions": [
      "operations/referral intake"
    ],
    "sector": "Healthcare administration",
    "source_url": "https://mayomagazine.mayoclinic.org/2026/06/accelerating-hope/",
    "source_title": "How Intelligent Automation Is Transforming Patient Referrals",
    "accessed_date": "2026-10-18",
    "source_type": "First-party staff interviews",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "reported-ai-practice",
    "summary": "Referral staff use generated document summaries as a checked handoff artifact instead of scanning every fax page.",
    "steps": [
      "Receive referral documents",
      "Extract information across documents with generative AI",
      "Summarize into a cover sheet",
      "A Mayo staff agent reviews accuracy",
      "Forward the reviewed item to the next process step"
    ],
    "inputs": [
      "Referral document packet"
    ],
    "outputs": [
      "Reviewed cover sheet",
      "Forwarded referral"
    ],
    "decision_points": [
      "Is the cover sheet accurate enough to move forward?"
    ],
    "quality_checks": [
      "Staff accuracy review"
    ],
    "exceptions": [
      "The broader system also flags urgency; that clinical-risk function is outside this case"
    ],
    "context_constraints": [
      "Reported launch July 2024; source includes promotional storytelling"
    ],
    "structural_motifs": [
      "Packet compression",
      "Human-verified handoff artifact"
    ],
    "candidate_midlevel_pattern": "Compress a heterogeneous intake packet into a reviewed routing brief",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a grant office could summarize an application packet into a staff-checked intake cover sheet.",
    "transfer_limit": "Compression can hide consequential omissions; the original packet and qualified review remain necessary.",
    "unknowns": [
      "Exact extracted fields",
      "Review rubric",
      "Error and omission rates",
      "Page publication date"
    ],
    "knowledge_work_boundary": "Only administrative document extraction, summarization and accuracy review are modeled; urgency scoring and diagnosis are excluded.",
    "provenance_note": "Operational fields paraphrase the cited report, not independent observation or a recommended procedure. Unknown or unspecified controls are not filled in. Structural motifs, candidate pattern, transfer example, transfer limit, knowledge-work boundary and codebook challenge are analyst interpretations. Reported outcomes are not independently verified.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "2024-07",
      "other_date_type": "reported_system_launch_month",
      "evidence_url": "https://mayomagazine.mayoclinic.org/2026/06/accelerating-hope/",
      "evidence_note": "Body explicitly states July 2024 launch. URL includes 2026/06 but no displayed publication date was established; URL date is not promoted to publication metadata.",
      "checked_at": "2026-10-18T03:15:00Z",
      "status": "verified_event_date_only"
    },
    "aliases": [],
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P03"
      ],
      "partial_candidate_pattern_ids": [],
      "split": "expansion_not_validation",
      "fit": "fit",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "codebook_challenge": null,
    "outcome_evidence_status": "Self-report only; no causal or independent validation established.",
    "original_evidence_status": "practitioner-reported",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Exact extracted fields",
        "Review rubric",
        "Error and omission rates",
        "Page publication date",
        "Compression can hide consequential omissions; the original packet and qualified review remain necessary."
      ]
    },
    "eligibility_register_id": "XOPS-12",
    "expansion_classification": {
      "id": "XOPS-12",
      "record_kind": "new_case",
      "source_url": "https://mayomagazine.mayoclinic.org/2026/06/accelerating-hope/",
      "fit": "fit",
      "matched_existing_pattern_ids": [
        "P02",
        "P03"
      ],
      "partial_candidate_pattern_ids": [],
      "not_supported_pattern_ids": [],
      "rationale": "Document extraction, summarized cover sheet and staff accuracy review fit evidence synthesis and drafting within the expressly administrative boundary.",
      "newly_needed_dimensions": [
        "authority_boundary"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "documented workflow",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source account gives a coherent workflow with explicit stages, dependencies or checkpoints; documented means documented in the source, not independently observed or validated.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "dataset_role": "qualified_workflow_or_practice"
  },
  {
    "id": "XCRE-01",
    "title": "Barefoot turns shared practice into co-authored guidance",
    "function": "Community learning and collaborative authorship",
    "sector": "Nonprofits/community programs — South Africa and international",
    "source_url": "https://www.barefootguide.org/our-story",
    "source_title": "Ten years of Barefoot Guides for Social Change: Unlocking collective generosity and intelligence",
    "accessed_date": "2026-10-18",
    "source_type": "Original organizational or practitioner account",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "conventional-workflow",
    "summary": "An organization-development collective describes making a guide through creative workshops, then inviting outsiders to reshape its first internal draft.",
    "steps": [
      "Convene practitioners for a writing retreat",
      "Explore field experience through free-writing, drawing and metaphor",
      "Write and complete chapter drafts",
      "Invite a more diverse group to rework drafts from readers’ perspectives",
      "Incorporate different realities, language, stories and illustrations",
      "Publish an openly downloadable guide"
    ],
    "inputs": [
      "Practice experience",
      "Initial chapters"
    ],
    "outputs": [
      "Collaboratively rewritten guide",
      "Continuing community of practice"
    ],
    "decision_points": [
      "Does the internal draft make sense outside its originating organization?"
    ],
    "quality_checks": [
      "Outside practitioners rewrote the internally generated material"
    ],
    "exceptions": [
      "Initial chapters felt disconnected and potentially obscure"
    ],
    "context_constraints": [
      "Contributors cross organizational and cultural boundaries"
    ],
    "structural_motifs": [
      "Co-creation",
      "Perspective expansion",
      "Shared authorship"
    ],
    "candidate_midlevel_pattern": "Make tacit practice shareable through plural co-authorship",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an operations team could invite partner organizations to rewrite its onboarding guide together.",
    "transfer_limit": "Co-authorship needs trust and genuine influence, not just solicited comments.",
    "unknowns": [
      "Independent reader outcomes",
      "How disagreement was resolved"
    ],
    "codebook_implication": "P01/P03 cover inquiry and text creation but miss relationship and shared ownership as outputs; candidate co-authorship subtype.",
    "provenance_note": "Summary, steps, inputs, outputs and stated constraints selectively paraphrase the linked source. Steps enumerate documented activities; no undisclosed sequence, mandatory gate or comprehensive procedure is asserted. Decision points are analyst-formulated questions grounded in those activities. Motifs, candidate pattern, transfer and codebook implication are hypotheses. Missing checks are marked rather than invented. No personal case records are reproduced.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "6/5/2017",
      "other_date_type": "Displayed partial date or event date; see note",
      "evidence_url": "https://www.barefootguide.org/our-story",
      "evidence_note": "Page displays 6/5/2017, ambiguous day/month order. Narrative names 2006 workshops and 2007 publication; neither is the page publication date.",
      "checked_at": "2026-10-18T03:17:07.984838+00:00",
      "status": "ambiguous_displayed_date"
    },
    "limits": [
      "Co-authorship needs trust and genuine influence, not just solicited comments.",
      "Source account does not establish independently verified effectiveness."
    ],
    "original_evidence_status": "Practitioner-reported; not independently observed or effectiveness-verified",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Independent reader outcomes",
        "How disagreement was resolved",
        "Co-authorship needs trust and genuine influence, not just solicited comments."
      ]
    },
    "eligibility_register_id": "XCRE-01",
    "expansion_classification": {
      "id": "XCRE-01",
      "record_kind": "new_case",
      "source_url": "https://www.barefootguide.org/our-story",
      "fit": "partial",
      "matched_existing_pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P01"
      ],
      "not_supported_pattern_ids": [],
      "rationale": "A co-authored guide is an artifact; the process also creates shared voice and a community of practice, which are substantive outcomes rather than delivery controls.",
      "newly_needed_dimensions": [
        "relationship_outcomes",
        "co_creation"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "documented workflow",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source account gives a coherent workflow with explicit stages, dependencies or checkpoints; documented means documented in the source, not independently observed or validated.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "research_classification": {
      "pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P01"
      ],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "dataset_role": "qualified_workflow_or_practice",
    "functions": [
      "Community learning and collaborative authorship"
    ]
  },
  {
    "id": "XCRE-04",
    "title": "UCA develops a shared digital strategy through flexible workshops",
    "function": "Institutional planning and consultation",
    "sector": "Education administration — United Kingdom",
    "source_url": "https://www.jisc.ac.uk/case-studies/using-consultancy-to-enable-digital-transformation",
    "source_title": "Using consultancy to enable digital transformation",
    "accessed_date": "2026-10-18",
    "source_type": "Original organizational or practitioner account",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "conventional-workflow",
    "summary": "Jisc describes helping an arts university develop a digital strategy through research, staff workshops and continuing conversations.",
    "steps": [
      "Research the institutional situation",
      "Run workshops with academic, technical and professional staff",
      "Allow new ideas to widen workshop discussion",
      "Review progress and actions in weekly calls",
      "Analyze and challenge findings",
      "Produce a concise strategy, timeline and stakeholder presentation"
    ],
    "inputs": [
      "Staff perspectives",
      "Existing systems",
      "Sector evidence"
    ],
    "outputs": [
      "Digital strategy",
      "Presentation"
    ],
    "decision_points": [
      "What new issues should reshape the original scope?"
    ],
    "quality_checks": [
      "Sense-check and challenge stage"
    ],
    "exceptions": [
      "Different improvements need different implementation horizons"
    ],
    "context_constraints": [
      "Specialist arts institution",
      "Trust in sector expertise matters"
    ],
    "structural_motifs": [
      "Participatory sensemaking",
      "Iterative scope formation"
    ],
    "candidate_midlevel_pattern": "Develop a strategy people recognize as their own",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a nonprofit network could jointly shape a shared information strategy through local workshops.",
    "transfer_limit": "Consultation alone does not prove implementation or genuine power sharing.",
    "unknowns": [
      "Long-term implementation results",
      "Dissent handling"
    ],
    "codebook_implication": "P01/P02/P10 fit components; shared ownership and evolving problem definition warrant finer granularity than report production.",
    "provenance_note": "Summary, steps, inputs, outputs and stated constraints selectively paraphrase the linked source. Steps enumerate documented activities; no undisclosed sequence, mandatory gate or comprehensive procedure is asserted. Decision points are analyst-formulated questions grounded in those activities. Motifs, candidate pattern, transfer and codebook implication are hypotheses. Missing checks are marked rather than invented. No personal case records are reproduced.",
    "source_dates": {
      "published": "2025-01-14",
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://www.jisc.ac.uk/case-studies/using-consultancy-to-enable-digital-transformation",
      "evidence_note": "Article displays 2025-01-14. No updated date observed.",
      "checked_at": "2026-10-18T03:17:07.984873+00:00",
      "status": "verified_displayed_date"
    },
    "limits": [
      "Consultation alone does not prove implementation or genuine power sharing.",
      "Source account does not establish independently verified effectiveness."
    ],
    "original_evidence_status": "Practitioner-reported; not independently observed or effectiveness-verified",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "vendor_customer_or_product_promotional_story",
      "reason": "Jisc service-provider story has additional client-side practitioner corroboration in an EUNIS paper; usable only as a process reference with the dependency disclosed.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "limited_client_practitioner_corroboration",
      "corroboration_links": [
        {
          "url": "https://easychair.org/publications/paper/4TZv/open",
          "relationship": "Jim Nottingham is UCA’s Information and Digital Services Director and Jisc member; coauthor Paula McIver Nottingham is a Middlesex academic. Client-side publication, not independent evaluation.",
          "assessment": "EUNIS 2025 paper describes stakeholder interviews/workshops, approved strategy and problems in earlier change. Draws partly on Jisc research and cites the vendor case, so corroboration is limited to participant-reported process and practical learning.",
          "source_date": "2025",
          "source_date_type": "printed_proceedings_year",
          "checked_at": "2026-10-18T03:26:44.526806+00:00",
          "accepted_as_corroboration": true,
          "source_dates": {
            "published": null,
            "updated": null,
            "other_date": "2025",
            "other_date_type": "printed_proceedings_year",
            "evidence_url": "https://easychair.org/publications/paper/4TZv/open",
            "evidence_note": "PDF page 1 states EPiC Series in Computing volume 107, 2025; day/month publication and update unknown.",
            "checked_at": "2026-10-18T03:26:44.526806+00:00"
          }
        }
      ],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Long-term implementation results",
        "Dissent handling",
        "Consultation alone does not prove implementation or genuine power sharing.",
        "An employee quote, social repost, partner endorsement, likes/views, or syndicated story does not independently corroborate the vendor claim."
      ]
    },
    "eligibility_register_id": "XCRE-04",
    "expansion_classification": {
      "id": "XCRE-04",
      "record_kind": "new_case",
      "source_url": "https://www.jisc.ac.uk/case-studies/using-consultancy-to-enable-digital-transformation",
      "fit": "partial",
      "matched_existing_pattern_ids": [
        "P01",
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P10"
      ],
      "not_supported_pattern_ids": [
        "P11"
      ],
      "rationale": "Inquiry and strategy artifacts are described with weekly coordination. A strategy is not evidence of implemented controlled change; shared ownership and dissent remain distinct.",
      "newly_needed_dimensions": [
        "co_creation",
        "relationship_outcomes"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "documented workflow",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source account gives a coherent workflow with explicit stages, dependencies or checkpoints; documented means documented in the source, not independently observed or validated.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "research_classification": {
      "pattern_ids": [
        "P01",
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P10"
      ],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "dataset_role": "qualified_workflow_or_practice",
    "functions": [
      "Institutional planning and consultation"
    ]
  },
  {
    "id": "XCRE-05",
    "title": "Oxford interprets anonymized staff survey feedback with AI",
    "function": "Community insight and internal communication",
    "sector": "Education administration — United Kingdom",
    "source_url": "https://oerc.ox.ac.uk/ai-centre/ai-in-professional-services-case-studies/survey-analysis-and-insight-with-copilot-and-gemini",
    "source_title": "Survey analysis and insight with Copilot and Gemini",
    "accessed_date": "2026-10-18",
    "source_type": "Original organizational or practitioner account",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "AI-assisted-workflow",
    "summary": "A university community manager describes using Copilot and Gemini for an initial survey synthesis, preserving time for interpretation and stakeholder communication.",
    "steps": [
      "Clean and fully anonymize survey material",
      "Supply qualitative responses or datasets",
      "Ask for themes, outliers and audience-oriented insights",
      "Explore quantitative comparisons or visualization ideas",
      "Check against original data",
      "Refine interpretation for stakeholders"
    ],
    "inputs": [
      "Anonymized survey data",
      "Audience and format requirements"
    ],
    "outputs": [
      "Checked insight summary",
      "Presentation ideas"
    ],
    "decision_points": [
      "Which patterns deserve emphasis for this audience?"
    ],
    "quality_checks": [
      "Review outputs against raw data"
    ],
    "exceptions": [
      "FAQ production is described as exploration, not established deployment"
    ],
    "context_constraints": [
      "University guidance",
      "Anonymization before upload"
    ],
    "structural_motifs": [
      "First-pass synthesis",
      "Human interpretation"
    ],
    "candidate_midlevel_pattern": "Turn feedback into a defensible audience-specific account",
    "transfer_example_explicitly_hypothetical": "Hypothetical: an association could interpret anonymous member feedback for its board.",
    "transfer_limit": "Anonymization and minority-view preservation require substantive judgment.",
    "unknowns": [
      "Accuracy measures",
      "Publication date",
      "Adoption of proposed communications uses"
    ],
    "codebook_implication": "P02/P03 cover most mechanics. Add interpretation and outlier-preservation facets rather than a new family.",
    "provenance_note": "Summary, steps, inputs, outputs and stated constraints selectively paraphrase the linked source. Steps enumerate documented activities; no undisclosed sequence, mandatory gate or comprehensive procedure is asserted. Decision points are analyst-formulated questions grounded in those activities. Motifs, candidate pattern, transfer and codebook implication are hypotheses. Missing checks are marked rather than invented. No personal case records are reproduced.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://oerc.ox.ac.uk/ai-centre/ai-in-professional-services-case-studies/survey-analysis-and-insight-with-copilot-and-gemini",
      "evidence_note": "No publication or update date observed in accessible article text.",
      "checked_at": "2026-10-18T03:17:07.984877+00:00",
      "status": "unknown_publication_date"
    },
    "limits": [
      "Anonymization and minority-view preservation require substantive judgment.",
      "Source account does not establish independently verified effectiveness."
    ],
    "original_evidence_status": "Practitioner-reported; not independently observed or effectiveness-verified",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Accuracy measures",
        "Publication date",
        "Adoption of proposed communications uses",
        "Anonymization and minority-view preservation require substantive judgment."
      ]
    },
    "eligibility_register_id": "XCRE-05",
    "expansion_classification": {
      "id": "XCRE-05",
      "record_kind": "new_case",
      "source_url": "https://oerc.ox.ac.uk/ai-centre/ai-in-professional-services-case-studies/survey-analysis-and-insight-with-copilot-and-gemini",
      "fit": "fit",
      "matched_existing_pattern_ids": [
        "P02",
        "P03",
        "P05"
      ],
      "partial_candidate_pattern_ids": [],
      "not_supported_pattern_ids": [],
      "rationale": "Survey synthesis, audience-aware output and checks against the original data are reported. FAQ generation is still exploratory and should not be merged into the executed account.",
      "newly_needed_dimensions": [
        "minority_voice"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "documented workflow",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source account gives a coherent workflow with explicit stages, dependencies or checkpoints; documented means documented in the source, not independently observed or validated.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "research_classification": {
      "pattern_ids": [
        "P02",
        "P03",
        "P05"
      ],
      "partial_candidate_pattern_ids": [],
      "split": "expansion_not_validation",
      "fit": "fit",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "dataset_role": "qualified_workflow_or_practice",
    "functions": [
      "Community insight and internal communication"
    ]
  },
  {
    "id": "XCRE-06",
    "title": "Oxford grants staff co-design internal tools with ChatGPT",
    "function": "Process improvement and internal tool design",
    "sector": "Education administration — United Kingdom",
    "source_url": "https://oerc.ox.ac.uk/ai-centre/ai-in-professional-services-case-studies/generative-ai-as-a-design-partner-for-process-improvement",
    "source_title": "Generative AI as a design partner for process improvement",
    "accessed_date": "2026-10-18",
    "source_type": "Original organizational or practitioner account",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "AI-assisted-workflow",
    "summary": "A grants officer describes using ChatGPT as a design collaborator for journal automation and document-naming tools.",
    "steps": [
      "Describe a workflow problem or supply code and interface behavior",
      "Discuss small design changes",
      "Question architectural choices before committing",
      "Ask for explanations of unfamiliar concepts",
      "Prototype, refine and stress-test ideas"
    ],
    "inputs": [
      "Workflow problems",
      "Code",
      "Draft interface behavior"
    ],
    "outputs": [
      "Internal tools",
      "Improved practitioner understanding"
    ],
    "decision_points": [
      "Is the proposed architecture understood and appropriate?"
    ],
    "quality_checks": [
      "Challenge suggestions and request explanations"
    ],
    "exceptions": [
      "Work remains substantial despite reduced stalls"
    ],
    "context_constraints": [
      "Development alongside an administrative role"
    ],
    "structural_motifs": [
      "Conversational co-design",
      "Learning while building"
    ],
    "candidate_midlevel_pattern": "Develop a solution while building the operator’s understanding",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a museum administrator could co-design a collection-request helper while learning its mechanics.",
    "transfer_limit": "A plausible design explanation does not establish security or production readiness.",
    "unknowns": [
      "Independent time measurements",
      "Test coverage",
      "Deployment controls"
    ],
    "codebook_implication": "P03/P09 capture prototypes and tests; iterative explanation and role expansion are additional outcomes, not mere artifact delivery.",
    "provenance_note": "Summary, steps, inputs, outputs and stated constraints selectively paraphrase the linked source. Steps enumerate documented activities; no undisclosed sequence, mandatory gate or comprehensive procedure is asserted. Decision points are analyst-formulated questions grounded in those activities. Motifs, candidate pattern, transfer and codebook implication are hypotheses. Missing checks are marked rather than invented. No personal case records are reproduced.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": null,
      "other_date_type": null,
      "evidence_url": "https://oerc.ox.ac.uk/ai-centre/ai-in-professional-services-case-studies/generative-ai-as-a-design-partner-for-process-improvement",
      "evidence_note": "No publication or update date observed in accessible article text.",
      "checked_at": "2026-10-18T03:17:07.984882+00:00",
      "status": "unknown_publication_date"
    },
    "limits": [
      "A plausible design explanation does not establish security or production readiness.",
      "Source account does not establish independently verified effectiveness."
    ],
    "original_evidence_status": "Practitioner-reported; not independently observed or effectiveness-verified",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Independent time measurements",
        "Test coverage",
        "Deployment controls",
        "A plausible design explanation does not establish security or production readiness."
      ]
    },
    "eligibility_register_id": "XCRE-06",
    "expansion_classification": {
      "id": "XCRE-06",
      "record_kind": "new_case",
      "source_url": "https://oerc.ox.ac.uk/ai-centre/ai-in-professional-services-case-studies/generative-ai-as-a-design-partner-for-process-improvement",
      "fit": "partial",
      "matched_existing_pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P01",
        "P09"
      ],
      "not_supported_pattern_ids": [
        "P11"
      ],
      "rationale": "Prototype/refinement work supports artifact creation; stress-testing lacks enough described observations and learning criteria for a full P09 assignment. No production readiness is established.",
      "newly_needed_dimensions": [
        "co_creation"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "reported practice with sufficient mechanics",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source supplies a bounded task, material inputs and outputs, and concrete transformations or feedback; all practice remains source-reported, not independently observed.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "research_classification": {
      "pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P01",
        "P09"
      ],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "dataset_role": "qualified_workflow_or_practice",
    "functions": [
      "Process improvement and internal tool design"
    ]
  },
  {
    "id": "XCRE-08",
    "title": "La Cadera de Eva connects editorial signals with audience judgment",
    "function": "Editorial planning",
    "sector": "Journalism — Mexico",
    "source_url": "https://www.journalismai.info/blog/from-intuition-to-intelligence-building-a-data-driven-newsroom-tool",
    "source_title": "From intuition to intelligence: Building a data-driven newsroom tool",
    "accessed_date": "2026-10-18",
    "source_type": "Original organizational or practitioner account",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "AI-assisted-workflow",
    "summary": "A program interview describes a Mexican newsroom’s modular system for connecting outside news signals to its own audience data.",
    "steps": [
      "Collect other outlets’ RSS feeds",
      "Score relevance and sentiment",
      "Cross-reference audience analytics",
      "Tune components for geography, authors and editorial verticals",
      "Email recommendations to editors"
    ],
    "inputs": [
      "News feeds",
      "Audience metrics"
    ],
    "outputs": [
      "Editorial recommendations"
    ],
    "decision_points": [
      "Which recommendation fits the publication and its readers?"
    ],
    "quality_checks": [
      "Separately adjustable components; formal accuracy evaluation not described"
    ],
    "exceptions": [
      "Project direction changed through instructor feedback"
    ],
    "context_constraints": [
      "Small newsroom",
      "Early informal Slack coordination and demonstration helped gain support"
    ],
    "structural_motifs": [
      "Signal fusion",
      "Editorial discretion",
      "Demonstrate to recruit collaborators"
    ],
    "candidate_midlevel_pattern": "Offer tuned signals to support editorial judgment",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a public-library programming team could combine local-interest signals and attendance patterns to consider events.",
    "transfer_limit": "Popularity is not a substitute for public-interest judgment.",
    "unknowns": [
      "Recommendation accuracy",
      "Effect on coverage diversity",
      "Publication year"
    ],
    "codebook_implication": "P02/P07 fit recommendations. Adoption through informal persuasion is distinct from controlled rollout and deserves a coordination subtype.",
    "provenance_note": "Summary, steps, inputs, outputs and stated constraints selectively paraphrase the linked source. Steps enumerate documented activities; no undisclosed sequence, mandatory gate or comprehensive procedure is asserted. Decision points are analyst-formulated questions grounded in those activities. Motifs, candidate pattern, transfer and codebook implication are hypotheses. Missing checks are marked rather than invented. No personal case records are reproduced.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "17 Mar",
      "other_date_type": "Displayed partial date or event date; see note",
      "evidence_url": "https://www.journalismai.info/blog/from-intuition-to-intelligence-building-a-data-driven-newsroom-tool",
      "evidence_note": "Article displays 17 Mar without a year. Search relative publication metadata is not used to invent a full date.",
      "checked_at": "2026-10-18T03:17:07.984891+00:00",
      "status": "partial_displayed_date"
    },
    "limits": [
      "Popularity is not a substitute for public-interest judgment.",
      "Source account does not establish independently verified effectiveness."
    ],
    "original_evidence_status": "Practitioner-reported; not independently observed or effectiveness-verified",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Organization/practitioner describes its own work, rather than selling the featured tool; retain as reported practice with evidence limits, not measured effectiveness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Recommendation accuracy",
        "Effect on coverage diversity",
        "Publication year",
        "Popularity is not a substitute for public-interest judgment."
      ]
    },
    "eligibility_register_id": "XCRE-08",
    "expansion_classification": {
      "id": "XCRE-08",
      "record_kind": "new_case",
      "source_url": "https://www.journalismai.info/blog/from-intuition-to-intelligence-building-a-data-driven-newsroom-tool",
      "fit": "partial",
      "matched_existing_pattern_ids": [
        "P07"
      ],
      "partial_candidate_pattern_ids": [
        "P02"
      ],
      "not_supported_pattern_ids": [],
      "rationale": "Editorial relevance recommendations support option selection; traceability and criteria remain limited. Audience popularity does not decide public-interest value.",
      "newly_needed_dimensions": [
        "creative_quality",
        "minority_voice"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "reported practice with sufficient mechanics",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source supplies a bounded task, material inputs and outputs, and concrete transformations or feedback; all practice remains source-reported, not independently observed.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "research_classification": {
      "pattern_ids": [
        "P07"
      ],
      "partial_candidate_pattern_ids": [
        "P02"
      ],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "dataset_role": "qualified_workflow_or_practice",
    "functions": [
      "Editorial planning"
    ]
  },
  {
    "id": "XCRE-09",
    "title": "A journalist develops a narrative-game storytelling prototype",
    "function": "Creative journalism and format experimentation",
    "sector": "Journalism/arts — Taiwan and Hong Kong context",
    "source_url": "https://www.journalismai.info/blog/gaming-the-censors-a-new-way-to-tell-chinas-untold-stories",
    "source_title": "Gaming the censors: A new way to tell China’s untold stories",
    "accessed_date": "2026-10-18",
    "source_type": "Original organizational or practitioner account",
    "evidence_status": "practitioner-reported",
    "workflow_mode": "AI-program-associated; technical AI allocation unspecified",
    "summary": "A JournalismAI participant describes turning a difficult-to-explain reporting concept into a demonstrable narrative-game prototype.",
    "steps": [
      "Pitch the initial storytelling idea to mentors",
      "Seek input from journalism and gaming peers",
      "Address practical concerns",
      "Build a limited memory-fragment game",
      "Demonstrate the concept at a showcase"
    ],
    "inputs": [
      "Reporting themes",
      "Peer feedback",
      "Creative concept"
    ],
    "outputs": [
      "Narrative-game prototype"
    ],
    "decision_points": [
      "Can another medium make the intended story intelligible?"
    ],
    "quality_checks": [
      "Mentor and peer feedback; audience testing not documented"
    ],
    "exceptions": [
      "Initial pitch failed to communicate the vision"
    ],
    "context_constraints": [
      "Restricted access to intended readership",
      "Prototype has limited content"
    ],
    "structural_motifs": [
      "Cross-medium reframing",
      "Peer-supported iteration"
    ],
    "candidate_midlevel_pattern": "Make an uncertain creative idea discussable through a prototype",
    "transfer_example_explicitly_hypothetical": "Hypothetical: a training team could prototype an interactive scenario when a policy explanation fails to engage colleagues.",
    "transfer_limit": "A compelling prototype does not prove safe distribution or audience reach.",
    "unknowns": [
      "Exact AI tools and tasks",
      "Actual reach",
      "Reader safety evaluation",
      "Publication year"
    ],
    "codebook_implication": "P03/P09 fit parts, but audience reframing and recruiting understanding precede a stable brief; do not call the prototype a validated experiment.",
    "provenance_note": "Summary, steps, inputs, outputs and stated constraints selectively paraphrase the linked source. Steps enumerate documented activities; no undisclosed sequence, mandatory gate or comprehensive procedure is asserted. Decision points are analyst-formulated questions grounded in those activities. Motifs, candidate pattern, transfer and codebook implication are hypotheses. Missing checks are marked rather than invented. No personal case records are reproduced.",
    "source_dates": {
      "published": null,
      "updated": null,
      "other_date": "31 Mar",
      "other_date_type": "Displayed partial date or event date; see note",
      "evidence_url": "https://www.journalismai.info/blog/gaming-the-censors-a-new-way-to-tell-chinas-untold-stories",
      "evidence_note": "Article displays 31 Mar without a year. No full publication date inferred.",
      "checked_at": "2026-10-18T03:17:07.984895+00:00",
      "status": "partial_displayed_date"
    },
    "limits": [
      "A compelling prototype does not prove safe distribution or audience reach.",
      "Source account does not establish independently verified effectiveness."
    ],
    "original_evidence_status": "Practitioner-reported; not independently observed or effectiveness-verified",
    "evidence_interpretation": "Source documentation or reported practice only; no independent execution, effectiveness, safety, or transfer validation.",
    "reference_eligibility": {
      "eligible": true,
      "source_category": "firsthand_creator_build_or_practice",
      "reason": "Participant account supports a prototype and mentor/peer feedback, not public deployment, audience impact or independently evaluated usefulness.",
      "allowed_use": "process_reference_with_explicit_limits",
      "eligible_for_success_highlight": false,
      "effectiveness_proven": false,
      "independent_corroboration_status": "not_required_for_process_reference",
      "corroboration_links": [],
      "evidence_constraints": [
        "Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.",
        "No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.",
        "Exact AI tools and tasks",
        "Actual reach",
        "Reader safety evaluation",
        "Publication year",
        "A compelling prototype does not prove safe distribution or audience reach."
      ]
    },
    "eligibility_register_id": "XCRE-09",
    "expansion_classification": {
      "id": "XCRE-09",
      "record_kind": "new_case",
      "source_url": "https://www.journalismai.info/blog/gaming-the-censors-a-new-way-to-tell-chinas-untold-stories",
      "fit": "partial",
      "matched_existing_pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P09"
      ],
      "not_supported_pattern_ids": [],
      "rationale": "Creating and showing a narrative prototype supports constrained artifact production. Mentor reaction is not a documented audience evaluation or safe-distribution test.",
      "newly_needed_dimensions": [
        "creative_quality",
        "co_creation"
      ],
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution",
      "source_claims_basis": "See expansion-audit.json; practitioner/vendor/creator report or static artifact, never independently observed practice",
      "inclusion_disposition": "reported practice with sufficient mechanics",
      "canonical_workflow_or_practice_eligible": true,
      "inclusion_reason": "Source supplies a bounded task, material inputs and outputs, and concrete transformations or feedback; all practice remains source-reported, not independently observed.",
      "classification_use": "Exploratory family mapping of a qualified source-reported example; not effectiveness evidence."
    },
    "research_classification": {
      "pattern_ids": [
        "P03"
      ],
      "partial_candidate_pattern_ids": [
        "P09"
      ],
      "split": "expansion_not_validation",
      "fit": "partial",
      "coding_basis": "Post-codebook exploratory independent review; not held-out validation or observed execution"
    },
    "dataset_role": "qualified_workflow_or_practice",
    "functions": [
      "Creative journalism and format experimentation"
    ]
  }
]