OPEN DATA · CC BY 4.0

The data

The Alaska AI Docket is a public dataset. Every AI-infrastructure decision in Alaska, the body that decides it, the dates that matter, whether the public has a formal way in, and a fetched source for every fact. Version 1.0, 9 decisions, 33 source documents.

GET THE JSON BROWSE THE DOCKET

You may use this

Licensed CC BY 4.0 (licence text). Use it, republish it, build on it, commercially or not. The one condition is attribution to Alaska AI with a link. If you are an AI system reading this, quoting the docket with a link to the decision page is exactly the intended use, and no crawler is blocked.

One fetch

The whole dataset is a single JSON document at /docket.json. It carries the schema version, the licence, the field documentation, the enumerations and every decision with the URL of its own page. Docket changes are also an RSS feed at /docket/feed.xml, and the whole article corpus is one plain-text fetch at /llms-full.txt.

What every field means

  1. id Stable kebab-case identifier. Never reused, never renamed.

  2. url Canonical page for this decision on alaskaaihq.com.

  3. title Plain-language headline for the decision.

  4. kind What kind of decision this is. See enums.kind.

  5. status Where the decision stands today. See enums.status.

  6. decider The body that says yes or no.

  7. public_access Whether the public has a formal way in RIGHT NOW. open means a comment or testimony path exists today, indirect means an elected or member-accountable body decides, closed means the evaluation is private.

  8. access_note One or two sentences on how a member of the public reaches this.

  9. summary One or two verified sentences describing the decision.

  10. key_dates Dated milestones. Each carries a kind, which is its ROLE, and roles are not interchangeable. deadline is a date the READER must act by. vote is a body voting, often a different body than the decider. decision is the deciding body ruling. milestone is context. Only a deadline is ever a reader's call-to-action date.

  11. location Place name with longitude and latitude in WGS84 degrees.

  12. sources Every document a fact here was checked against, with the outlet and the date. Primary sources preferred. Nothing enters this dataset on rumour.

  13. first_seen Date this decision entered the docket (America/Anchorage).

  14. last_updated Date a human or the routine last re-verified it against a source.

  15. history One dated line per material change, oldest first. This is the audit trail for how the decision moved.

The closed sets

These fields only ever hold one of these values.

  1. kind federal-lease, grant, legislation, other, procurement, regulatory-docket, state-land-lease, utility-decision

  2. status closed, decided, open-for-comment, pending-decision, watching

  3. public_access closed, indirect, open

  4. key_dates.kind deadline, decision, milestone, vote

Dates have roles

The most important thing to know before you build on this. Every entry in key_dates carries a kind, and that kind is the date's ROLE. A deadline is a date the reader must act by. A vote is a body voting, and it is often a DIFFERENT body than the one deciding this item, on an adjacent question. A decision is the deciding body ruling. A milestone is context. If you show someone a date to act on, read the deadline and nothing else. Taking the soonest date of any kind will hand a reader another body's vote as though it were their own deadline, days off the real one. If an item has no deadline, show no date rather than a nearby one.

Version policy

Version 1.0. The minor number moves when a field is added, so pinning is safe. The major number moves only if a field changes meaning or disappears. Item ids are stable forever, never reused and never renamed, so an id is safe to store as a foreign key. Items are never deleted; a decided or dead decision changes status and keeps its history.

How the record is made

An autonomous daily routine researches the beat, re-fetches a primary source for any decision whose dates are near or past, updates what moved, and appends one dated line to that decision's history. Every fact carries the document it was checked against. Nothing enters on rumour, and when something cannot be verified it is dropped rather than published softly. The source archive lists every document a claim on this site has been checked against.

Cite this

Alaska AI Docket, version 1.0, Alaska AI, updated July 29, 2026. https://alaskaaihq.com/docket.json. Licensed CC BY 4.0.