This matrix is a build checklist to keep the public-first case study complete, sourced, and honest about uncertainty. It enforces separation between verified facts, actor claims, analysis, and unknowns, and it is designed to support a snapshot-in-time artifact rather than an open-ended monitoring brief.
Snapshot window to carry through the build: late 2025 to February 25, 2026, with a discovery configuration in ../inputs/sources.yaml set to a 365-day search window and a monitoring note in ../inputs/latest_updates.md dated February 20, 2026.
| Section ID | Purpose | Must Include | Primary Inputs | Evidence / Data Needed | Output Artifact | Status |
|---|---|---|---|---|---|---|
| S1 Opening: A Technical Adjustment in an Age of HPAI | Open with the policy change as a concrete administrative adjustment while establishing why animal-disease response makes traceability salient. | - State the reported policy delta: shorter movement-reporting windows and expanded reporting expectations from ../inputs/executive_case_study_legitimacy.md.- Introduce HPAI as the real biosecurity backdrop, tied to ../inputs/latest_updates.md and the ostrich/H5N1 trust context in ../inputs/town_hall_inventory.md.- Clarify that the opening will distinguish regulator risk logic from producer burden narratives before moving into politics. - Set the snapshot frame as late 2025 to February 2026, not an evergreen monitor. |
executive_case_study_legitimacy.md, latest_updates.md, town_hall_inventory.md, sources.yaml |
- A plain-language summary of the proposed traceability adjustments. - A careful HPAI baseline: ongoing avian-influenza risk is real, but no claim of imminent cattle catastrophe without evidence. - Unknown: whether CFIA issued a single definitive public summary of the exact proposal in this source set. - Unknown: exact implementation text beyond what secondary inputs describe. |
index.md §S1 + ledger cross-references for verified baseline vs actor framing |
TODO |
| S2 Epidemiological Reality: Why HPAI Changes the Stakes | Explain the disease-response context clearly enough that readers understand why regulators care without turning the section into fear-based persuasion. | - Explicitly say HPAI is a real epidemiological and biosecurity context, drawing from ../inputs/latest_updates.md and H5N1 references in ../inputs/town_hall_inventory.md.- Avoid fear-mongering by distinguishing outbreak preparedness from certainty claims. - Clearly separate "why regulators care" from "what producers foreground" using the legitimacy framing in ../inputs/executive_case_study_legitimacy.md.- Note that trust inheritance from prior CFIA actions can shape reception even when disease-control goals are not wholly rejected. |
latest_updates.md, town_hall_inventory.md, executive_case_study_legitimacy.md |
- A sourced statement that avian influenza remained a regional and global concern in February 2026. - A sourced description of the BC ostrich culling as an H5N1-linked event if included. - Unknown: direct CFIA epidemiological modeling specific to the traceability proposal is not present in the copied inputs. - Unknown: species-specific pathway from HPAI concern to cattle traceability changes should be marked as inferred unless primary regulatory text is added later. |
index.md §S2 + ledger note marking disease context vs inference |
TODO |
| S3 What Traceability Is (Mechanics + Policy Delta) | Give readers a plain-language explanation of traceability mechanics and the proposed policy change before escalating into conflict narratives. | - Define the operational basics: premise identification, movement reporting, tag/reporting workflows, and administrative expectations from ../inputs/town_hall_inventory.md.- Explain the reported shift from 30 days to 7 days and the mention of additional data fields, tying wording to ../inputs/executive_case_study_legitimacy.md and ../inputs/traceability_language_analysis.md.- Identify concerns about tags, readers, online reporting, fairs, 4-H, auction channels, vet trips, and death reporting where those are described in ../inputs/town_hall_inventory.md and ../inputs/traceability_language_analysis.md.- Mark where details are coming from producer-facing descriptions rather than primary regulation text. |
town_hall_inventory.md, executive_case_study_legitimacy.md, traceability_language_analysis.md |
- Plain-language definitions suitable for a public audience. - At least one verified distinction between current practice and proposed change. - Unknown: full official rule text, exemptions, transition periods, and final enforcement design are absent from the copied package. - Unknown: whether all reported requirements applied uniformly across species and movement contexts. |
index.md §S3 + ledger entries for verified mechanics and actor-reported burdens |
TODO |
| S4 Escalation: How a Policy Becomes a Revolt | Show how a technical file turned into a broad protest narrative through meetings, turnout, petitions, and political uptake. | - Reconstruct the escalation from technical rule questions to identity and fairness conflict using ../inputs/executive_case_study_legitimacy.md.- Tie town halls, attendance figures, petition counts, and video-view references directly to ../inputs/town_hall_inventory.md.- Identify organizer and political bridge figures only as documented in ../inputs/political_context_analysis.md and ../inputs/town_hall_inventory.md.- Mark where counts lack denominators or independent validation. |
town_hall_inventory.md, executive_case_study_legitimacy.md, political_context_analysis.md, traceability_narrative_audit.md |
- Dates and locations for the Innisfail and Stettler-related meetings. - Attendance, petition, and view counts with caution labels when denominator/context is missing. - Unknown: full event inventory across Alberta beyond the meetings named in the inputs. - Unknown: exact conversion from turnout to broader producer sentiment across the province. |
index.md §S4 + ledger entries for event facts, scale claims, and open questions |
TODO |
| S5 Legitimacy Gaps: Procedural, Epistemic, Distributive, Relational | Analyze why resistance hardened by using the legitimacy framework rather than treating the conflict as mere misinformation or messaging failure. | - Use the four-part legitimacy framework from ../inputs/executive_case_study_legitimacy.md: procedural, epistemic, distributive, relational.- Connect procedural concerns to consultation complaints and pause/revision dynamics noted in ../inputs/town_hall_inventory.md.- Connect epistemic and distributive concerns to small-vs-large producer burdens, digital readiness, and scale asymmetry claims from ../inputs/traceability_language_analysis.md.- Explain relational legitimacy through accumulated distrust, including careful use of the ostrich-culling trust inheritance if retained. |
executive_case_study_legitimacy.md, town_hall_inventory.md, traceability_language_analysis.md, traceability_narrative_audit.md |
- A disciplined separation between analytical framework and direct evidence. - Specific examples of each legitimacy gap from the copied inputs. - Unknown: primary evidence for enforcement asymmetry is not in the package and cannot be stated as fact. - Unknown: whether consultation mechanisms materially changed policy details before the pause. |
index.md §S5 + structured ledger classifications by claim type |
TODO |
| S6 Narrative Ecosystems: Weaponization Without Overclaiming | Map the messaging environment around the revolt while avoiding unsupported assertions about coordination, intent, or disinformation. | - Pull rhetorical motifs such as "government overreach," "digital ID for food," "bureaucratic culling," "small farm survival," and "system failure" from ../inputs/traceability_language_analysis.md and ../inputs/traceability_narrative_audit.md.- Tie named media and political-actor ecosystem claims to ../inputs/political_context_analysis.md only as documented claims or analytical observations.- Frame narrative weaponization as ecosystem dynamics and message amplification, not a blanket accusation against all critics. - Mark where the source base relies on secondary monitoring rather than primary transcripts. |
traceability_language_analysis.md, traceability_narrative_audit.md, political_context_analysis.md |
- Examples of repeated motifs across meetings and media coverage. - Clear labeling of what is documented speech versus analytical interpretation. - Unknown: full reach, coordination, and audience impact across the wider media ecosystem. - Unknown: causal proof that any one actor deliberately orchestrated the whole narrative field. |
index.md §S6 + ledger split between documented rhetoric and analytical interpretation |
TODO |
| S7 Food System Fragility Meets Democratic Fragility | Connect the dispute to broader questions of food-system resilience, institutional trust, and rural democratic legitimacy without flattening distinct concerns. | - Combine the resilience rationale from ../inputs/executive_case_study_legitimacy.md with community-level burden arguments from ../inputs/traceability_language_analysis.md and ../inputs/traceability_narrative_audit.md.- Show how worries about rural depopulation, schools, hospitals, and local markets are framed by actors, not automatically verified outcomes. - Explain how trust deficits can turn administrative modernization into a constitutional-feeling conflict. - Keep the section public-first while staying legible to experts by separating observed rhetoric from systemic interpretation. |
executive_case_study_legitimacy.md, traceability_language_analysis.md, traceability_narrative_audit.md, town_hall_inventory.md |
- At least one verified baseline sentence on why traceability matters to food-system resilience. - Actor-claim examples about rural community effects and economic fragility. - Unknown: independent economic modeling of rural closures or consumer price effects is not in the package. - Unknown: whether food-system fragility claims generalize beyond the cited communities. |
index.md §S7 + ledger entries marking downstream-effect claims as claims unless sourced |
TODO |
| S8 A Glimpse Forward: Agentic Sense-Making and Governance Adaptation | End by sketching how institutions and publics might handle future policy disputes with better evidence discipline and iterative governance. | - Use the redesign and co-design implications from ../inputs/executive_case_study_legitimacy.md as the core forward-looking base.- Position future sense-making as better separation of facts, claims, and uncertainty rather than automation hype. - If monitoring is mentioned, tie it narrowly to ../inputs/latest_updates.md as an example of bounded updates, not live surveillance.- Keep this section explicitly modest: a glimpse forward, not a full solution architecture. |
executive_case_study_legitimacy.md, latest_updates.md, instructions.txt |
- A concise bridge from the case study to governance adaptation. - A reminder that this package is a snapshot and not an always-on intelligence product. - Unknown: no direct evidence in the package about which governance redesigns would be politically acceptable. - Unknown: applicability of "agentic" approaches beyond a conceptual aside. |
index.md §S8 + optional ledger note on speculative forward-looking claims |
TODO |
| S9 What This Is Not (Boundary-setting section) | Prevent misreadings by stating what the case study does not claim, prove, or attempt to resolve. | - State that the package is not a legal brief, not a live monitoring dashboard, and not a verdict on every actor’s motives. - State that it does not prove enforcement asymmetry, conspiracy, or producer unanimity without stronger primary evidence. - Note that named political/media ecosystem patterns come from ../inputs/political_context_analysis.md, ../inputs/traceability_narrative_audit.md, and ../inputs/traceability_language_analysis.md, and may require further verification before stronger claims are made.- Reaffirm the separation of verified facts, actor claims, analysis, and unknowns. |
political_context_analysis.md, traceability_narrative_audit.md, traceability_language_analysis.md, executive_case_study_legitimacy.md |
- A disciplined list of non-claims. - Explicit uncertainty labels for contested or weakly sourced assertions. - Unknown: complete official record needed to settle several disputed implementation details. - Unknown: whether omitted stakeholders would materially change interpretation. |
index.md §S9 + ledger legend for claim classes and exclusions |
TODO |
| S10 Companion Link: How to Read the Claim Ledger | Explain the ledger’s role so readers can inspect sourcing boundaries and uncertainty without interrupting the essay flow. | - Link to ../claim-ledger.md via the publishable relative path ./claim-ledger/.- Explain that the ledger will separate verified baseline facts, actor claims, analytical interpretations, and open questions. - Note that town hall numbers, petition counts, media-node references, and rhetorical motifs should be easy to trace back to ../inputs/ files.- Encourage readers to check the ledger whenever a sentence in the essay makes a nontrivial claim. |
claim-ledger.md, town_hall_inventory.md, traceability_language_analysis.md, traceability_narrative_audit.md, political_context_analysis.md |
- A short explainer of ledger categories. - Cross-reference pattern between narrative sections and ledger entries. - Unknown: final citation style and anchor format are still to be chosen during drafting. |
index.md §S10 + claim-ledger.md intro and section anchors |
TODO |
inputs/town_hall_inventory.md./claim-ledger/)