Governance

This document defines how the EpiHack Arizona 2026 stack is governed post-event. It encodes the cross-cutting governance track from plan/05-roadmap.md and is binding on maintainers, agency-affiliated committers, and contributing agents (human or LLM).

The intent is not bureaucracy. It is a small, durable structure that keeps the four founding agencies in the loop on anything that could change how surveillance data is collected, suppressed, or routed — and that gives tribal partners a hard veto on anything touching tribal data.

Standing review board

The standing review board has four seats. Membership is by organization, not by individual, so transitions inside an agency do not require a repo change.

Seat Organization Scope of authority
ADHS Arizona Department of Health Services — Vector-Borne & Zoonotic Diseases program and the Heat Preparedness Network Statewide arbovirus + heat-mortality surveillance; reportable-condition definitions; triage-class thresholds
AZGFD Arizona Game and Fish Department — Wildlife Health Program Wildlife observation flows; WHISPers + iNaturalist enrichment behaviour; species-attribution rules
ITCA-TEC Inter Tribal Council of Arizona — Tribal Epidemiology Center All decisions touching tribal data; veto authority below
Maricopa Vector Control Maricopa County Environmental Services Department, Vector Control Division Mosquito / tick pool data flows; cluster-detection threshold calibration for VBD; Phoenix-metro cooling-center integrations

The board operates by lazy consensus on the GitHub PR thread (any member can request changes; absence is consent after a 5-business-day window). Two domains escape lazy consensus and require explicit signoff:

Proposal-then-merge cadence

Changes fall into three buckets with different review depths.

Schema changes — proposal first

Anything in schema/ — node types, edge predicates, property keys, slug renames, view definitions.

Runtime / orchestrator changes — PR first, fast review

Changes in agents/, app/, dashboard/, today/.

MCP server changes — PR first, prefix-scoped review

Changes in mcp/<server>/.

Tribal-partner veto

ITCA-TEC and any participating tribal nation hold an unconditional veto on every change that touches tribal data, including but not limited to:

A veto is recorded on the PR. There is no override mechanism.

Tribal-partner opt-in posture

The default for every new tribal partner is no data flows in either direction until an MOU is signed and a corresponding consent_profile row is added with default = opt_in. There is no opt-out posture and no default that shares tribal data; tribes opt in explicitly per data source.

Concretely:

Conflict-of-interest disclosure

Committers affiliated with one of the standing-board agencies (ADHS, AZGFD, ITCA-TEC, Maricopa Vector Control) or any state, county, or tribal health authority must disclose that affiliation:

A disclosed conflict does not disqualify the contributor; it informs reviewers, who may ask for an independent second review. An undisclosed conflict that is later discovered is grounds for revoking commit access pending board review.

Sunset clauses

Any MCP server that acts as a proxy for a tribal data source operates only as long as the underlying MOU is live. Specifically:

The same posture applies, less formally, to MCP servers proxying non-tribal partner data (ADHS, MAG, 211 Arizona, USGS WHISPers, iNaturalist): if the data-sharing agreement lapses, the server is disabled in deployment configs and the README header is updated.

Amending this document

This file is amended via PR, with the same lazy-consensus rules as runtime changes, plus: amendments to the Standing review board section, the Tribal-partner veto section, or the Sunset clauses section require explicit approval from all four seats. Other sections may be amended by lazy consensus.