# Facility-readiness data dictionary

## `facility_readiness_cases.csv`

| Field group | Fields | Meaning |
|---|---|---|
| Identity | `case_id`, `case_name`, `unit_type`, `comparison_group`, `country`, `city_or_development`, `owner`, `operator` | Stable analytical unit and accountable parties |
| Status | `service_layer_status`, `physical_delivery_stage`, `delivery_stage_date`, `delivery_evidence` | Logical service status kept separate from the highest supported physical milestone |
| Site | `site_evidence_level`, `public_address`, `latitude`, `longitude`, `coordinate_confidence` | Publicly supportable location and whether coordinates are safe for spatial analysis |
| Capacity | `headline_capacity_mw`, `capacity_definition`, `capacity_evidence_level` | Source-reported MW without conversion, plus the strength of its definition |
| Power | `utility_or_power_counterparty`, `substation_or_grid_asset`, `voltage_kv`, `requested_or_firm_mw`, `grid_queue_or_connection_stage`, `energization_date`, `power_evidence_level` | Project-specific path from supply intent to energized power |
| Operability | `cooling_system`, `pue`, `wue`, `water_source`, `water_capacity`, `discharge_or_water_permit`, `fiber_diversity`, `building_or_operating_permit`, `operability_evidence_level` | Site-specific ability to cool, connect, use water, and operate legally |
| Targets | `current_target_date`, `target_date_history`, `target_revision_flag` | Current target and preserved revisions; targets are never milestones |
| Provenance | `primary_source_id`, `supporting_source_ids`, `source_locator`, `cutoff_date` | Source joins and evidence cutoff |
| Judgment | `material_unknowns`, `decision_use` | Concise interpretation and the facts that would change it |
| Coverage | `public_field_count`, `public_field_total`, `evidence_coverage_pct` | Disclosure coverage across the 18 core fields; not a readiness score |

## `facility_evidence_events.csv`

One row per dated announcement, milestone, target revision, certification, procurement record, or status observation. `reported_value` preserves the source claim; `normalized_interpretation` states what the evidence supports; `evidence_effect` identifies which dimension changes.

## `facility_evidence_gaps.csv`

One row for every unestablished core field in every case. `priority` reflects decision materiality, not ease of collection. `next_best_source` identifies the documentary class most likely to close the gap.

## `power_path_tracker.csv`

| Field group | Fields | Meaning |
|---|---|---|
| Identity | `tracker_id`, `case_id`, `case_name`, `country`, `location`, `analytical_unit`, `comparison_group` | One tracker row linked to one audited readiness case |
| Physical context | `physical_delivery_stage`, `headline_capacity_mw`, `capacity_definition` | Source-reported delivery and capacity context; headline MW is never assumed to be firm power |
| Power status | `power_evidence_level`, `power_path_status`, `utility_or_power_counterparty`, `grid_asset_or_reinforcement`, `voltage_kv`, `requested_or_firm_mw`, `connection_stage`, `energization_date` | Documentary sequence from no public evidence through project-specific energization |
| Milestone | `latest_power_milestone_date`, `latest_power_milestone` | Latest source-linked event that changes or supports the public power-path status |
| Research queue | `open_critical_power_gaps`, `next_required_document` | Exact missing fields and the document class needed to advance the case |
| Provenance and judgment | `primary_source_id`, `supporting_source_ids`, `assessment`, `cutoff_date` | Source joins, bounded interpretation, and evidence cutoff |

The tracker is built from the case ledger, event chronology, field-gap register, and source register. Its specific rules are in `docs/POWER_PATH_TRACKER_METHOD.md`.

## Codes

- Physical delivery: `D0`–`D6`
- Site specificity: `S0`–`S4`
- Capacity definition: `C0`–`C3`
- Power path: `P0`–`P4`
- Operability: `O0`–`O3`

Definitions and interpretation rules are in `docs/FACILITY_READINESS_METHOD.md`.