{
  "_about": "A codebook is the controlled vocabulary of a qualitative study. Each code has a definition and inclusion/exclusion rules so that two coders (human or model) apply it the same way. Codes are applied to evidence units in a SEPARATE pass (codings.json) - so when the codebook changes, you re-code, you do not re-extract. Counting codes across interviews is how the 'bigger picture' becomes a number with a denominator.",
  "version": "cb-v3",
  "history": [
    { "version": "cb-v1", "date": "2026-09-16", "change": "Initial 11 codes from tx_001." },
    { "version": "cb-v2", "date": "2026-09-23", "change": "Added C05 (automation succeeded) and C08 (reconciliation) after tx_002. C04 renamed from 'automation_attempt' to 'automation_attempt_failed' to separate from C05." },
    { "version": "cb-v3", "date": "2026-12-11", "change": "Added C14 (staffing change) after tx_003." }
  ],
  "codes": [
    { "id": "C01", "label": "manual_consolidation",        "definition": "A recurring, human-performed step that merges data from more than one source into a report.", "include": "Any mention of people combining exports/files by hand on a schedule.", "exclude": "One-off data pulls; automated merges (see C05).", "exemplar": "ev_004" },
    { "id": "C02", "label": "schema_drift",                "definition": "Export column names, order, or format changing between runs.", "include": "Any statement that structure changed, whatever the cause.", "exclude": "Changes in the data VALUES (see C08).", "exemplar": "ev_009" },
    { "id": "C03", "label": "workaround",                  "definition": "A home-built or manual fix that compensates for a problem rather than removing it.", "include": "Manual remapping, hard-coded mapping tables, chasing people.", "exclude": "Vendor tools adopted as solutions.", "exemplar": "ev_011" },
    { "id": "C04", "label": "automation_attempt_failed",   "definition": "A team-built automation that was tried and abandoned.", "include": "Explicit abandonment or reversion to manual.", "exclude": "Automation still in use (C05).", "exemplar": "ev_014" },
    { "id": "C05", "label": "automation_attempt_succeeded","definition": "A team-built automation that is in use and credited with reducing effort.", "include": "Scripts/queries currently running.", "exclude": "Vendor products.", "exemplar": "ev_104" },
    { "id": "C06", "label": "timeliness_pressure",         "definition": "Deadlines, cutoffs, lateness, or the consequences of lateness.", "include": "Cutoff policies, late deliveries, decisions made on stale data.", "exclude": "Incompleteness without a timing element (C07).", "exemplar": "ev_018" },
    { "id": "C07", "label": "data_completeness",           "definition": "The report shipping with missing content.", "include": "Gaps, missing sources, partial reports.", "exclude": "Wrong values (C08).", "exemplar": "ev_205" },
    { "id": "C08", "label": "data_reconciliation",         "definition": "Effort spent resolving disagreement between figures from different systems.", "include": "'Numbers never agree', deciding which source is right.", "exclude": "Structural mismatches (C02).", "exemplar": "ev_109" },
    { "id": "C09", "label": "purchase_authority",          "definition": "Who can approve a purchase and up to what amount.", "include": "Thresholds, escalation to a director.", "exclude": "Whether money is actually allocated (C10).", "exemplar": "ev_021" },
    { "id": "C10", "label": "budget_availability",         "definition": "Whether funds are actually allocated for tooling.", "include": "'No budget line', discretionary budgets, money found.", "exclude": "Authority without allocation (C09).", "exemplar": "ev_023" },
    { "id": "C11", "label": "security_gating",             "definition": "Security review as a condition on adopting a tool, and its duration.", "include": "Conditions that trigger a review; how long it took.", "exclude": "General IT approvals not framed as security.", "exemplar": "ev_024" },
    { "id": "C12", "label": "downstream_stakeholder_demand","definition": "Requests or pressure from the report's audience.", "include": "Requests for different cadence/content; how the audience uses the report.", "exclude": "The speaker's own preferences.", "exemplar": "ev_028" },
    { "id": "C13", "label": "solution_interest",           "definition": "Expressed interest, disinterest, or willingness to pay for a proposed solution.", "include": "Positive and negative reactions to interviewer-proposed tools; pilots; quotes.", "exclude": "Descriptions of existing tools.", "exemplar": "ev_020" },
    { "id": "C14", "label": "staffing_change",             "definition": "People joining, leaving, or changing responsibilities on the team.", "include": "Departures, reassignments.", "exclude": "Headcount stated without change.", "exemplar": "ev_213" }
  ]
}
