# Governance > Canonical HTML: https://initkoa.org/infrastructures/kristal-farms/governance > Markdown mirror: https://initkoa.org/infrastructures/kristal-farms/governance/index.html.md > Route: /infrastructures/kristal-farms/governance > Source: app/infrastructures/kristal-farms/governance/page.mdx > Generated: 2026-06-13T02:25:42.872Z [Open the HTML page](https://initkoa.org/infrastructures/kristal-farms/governance) "How Kristal Farms are governed: shared decision-making across community, operator, tenants, and environmental stewards—plus the agreements, reporting, and grievance paths that make it enforceable.", # Governance Kristal Farms is infrastructure that touches **power**, **heat**, **water**, **network**, and **community outcomes**. That means “operator discretion” is not enough. The project is designed so that: - critical priorities are **decided explicitly**, not implied, - commitments are **written down**, not promised, - and performance is **observable**, not hidden. Governance is the mechanism that keeps the project **community-aligned**, **tenant-safe**, and **environmentally constrained**. ## The governance stack (four bodies) Kristal Farms uses four standing bodies. Each operates under a charter defining what it can **decide** vs what it can **recommend**. ### 1) Project Council (steering) The high-level steering forum where the key parties sit together: - community representatives, - public owner (if applicable), - site operator (host), - tenant representatives, - greenhouse operator (if present). **Mandate:** overall strategy, budget approvals, compliance with agreements, and escalation for major disputes. ### 2) Heat Committee (heat-first operations) A committee dedicated to heat allocation and the heat-first rule. **Mandate:** - set seasonal heat priorities (e.g., clinic/school first in winter), - approve the list and timing of heat sinks (including greenhouse windows), - review heat logs and curtailment events, - recommend operational adjustments based on weather and demand. - Heat-first design → - Metrics & dashboard → ### 3) Environment Committee (ecological limits) A committee responsible for environmental compliance and incident review. **Mandate:** - monitor discharge temperature delta (ΔT) and other agreed limits, - oversee monitoring on flows and water quality indicators, - review environmental incidents and mitigation, - trigger operational responses when constraints tighten (e.g., low flow periods). - Environment & safety → ### 4) Kristals Council (knowledge commons) A committee governing the public-interest knowledge outputs associated with the project. **Mandate:** - select public-interest topics, - validate quality/appropriateness before publication, - oversee update cadence and usage metrics, - enforce the “black-box boundary” (no private tenant data, no personal data; only consented/public sources). ## Decision rights (who controls what) A simple principle: **operations are technical; priorities are civic.** - The **operator** runs utilities and safety procedures (power, cooling, alarms, access control). - **tenants** run workloads inside their pads. - the **community**, through governance, controls the *priorities and commitments*: - heat allocation priorities, - environmental limits and response policies, - community benefit mechanisms, - transparency and reporting obligations. This prevents drift into “we’ll decide later” governance. ## Agreements that make governance real Governance is backed by enforceable agreements. Typical documents include: - **Pad lease + SLA:** defines interfaces and service levels (power, cooling handoff, fiber handoff, yard rules), plus step-in rights for safety. - **Heat supply agreement:** defines delivery bands, metering, curtailment order, and reserved social-use heat allocations. - **Fiber service agreement:** defines network availability/latency expectations and maintenance notice requirements. - **Community Benefits Agreement (CBA/IBA):** defines local hiring/training, procurement preferences, community fund mechanisms, and reporting. Governance committees use these as their “source of authority” for decisions and audits. - Tenancy model → - Go / No-Go gates → ## Community-first engagement (FPIC) Kristal Farms is intended to operate on a **community-first engagement process** consistent with Free, Prior, and Informed Consent (FPIC): - inform early, - consult and incorporate feedback, - obtain formal consent before build/power-on, - and hold periodic reviews to renew or reassess consent over time. This is treated as a continuing condition of legitimacy, not a one-time checkbox. ## Transparency & reporting (how accountability is enforced) Governance without visibility becomes theater. Kristal Farms therefore uses: - a **public-facing dashboard/scorecard** (monthly or near real-time summaries), - **published meeting summaries** (and minutes where appropriate), - **quarterly reviews** across committees, - and an **annual public report** covering technical + community benefit metrics. - Metrics & dashboard → ## Grievance and dispute resolution The governance model includes a formal path for conflicts and complaints: - a clear channel for community members to raise concerns, - defined response timelines, - escalation to the Project Council when needed, - and the option for mediation as specified in agreements. The goal is to prevent silent resentment and ensure problems are handled while they are still solvable. ## Why this matters Kristal Farms is not only a technical site. It is a long-lived relationship between: - a community, - tenants, - an operator, - and the local environment. Governance is the mechanism that keeps that relationship **explicit, measurable, and correctable**. - Metrics & dashboard → - Go / No-Go gates →