Evidence

The source registry every claim cites, and the method that governs how the record is built, hashed, and corrected.

The source registry

One entry per document, forever. Every claim on this site cites one of these IDs. Archived files are content-addressed: the SHA-256 shown is the file's permanent fingerprint. Entries marked TODO-HUMAN are honest gaps, not omissions. Canonical: registry/sources.yaml · machine-readable data/sources.json.

Method & governance

Governance

*Living Atlas — governance policy, published per architecture §8. Written before it was needed. Four sections; each is short on purpose.*

What this record does and does not establish. The Living Atlas preserves what was publicly represented, what was executed, and what is binding — the documented decision context. It does not establish why any person voted, negotiated, or decided as they did. Motive is not in the public record, and the Atlas does not infer it. Where the record shows a gap — between a promotional figure and a binding term, between a memo and the vote that preceded it — the gap is recorded as a fact about the documents, not as a claim about anyone's intent.

*(Added 2026-08-14, WO-015 — external-input disposition 2026-08-14, adopt-now item 1; verbatim. Nothing below is rewritten.)*

1. Editorial independence

The Atlas documents consequential public decisions; it does not campaign about them. It holds open questions open, endorses nothing, opposes nothing, and imputes no motive to any person — individuals appear only in their public capacities, sourced to public documents. Its editorial control is not for sale, not for rent, and not available to any funder, subject, or ally. Where the record supports two readings, the Atlas preserves both and says so.

2. Funding disclosure

Every dollar source behind the Atlas will be named here, including any public-body or economic-development money that reaches the separate Gulf Cluster Brief. This project is founder-funded exclusively: a personal Claude Max subscription, domain registration, and incidental compute costs. No outside money, no sponsors, no institutional support. (Disclosure as of 2026-08-09; any change will be recorded as a dated append, never an edit, per the corrections policy.)

3. The two-brand firewall

The Atlas (this record, this site) and the Gulf Cluster Brief (a separate, promotional publication) share a documentary corpus and nothing else. Separate repositories, separate names, separate voices. Nothing promotional lives in this repository or speaks in the Atlas's voice; the Brief reads the public data the same way anyone else does. Stated plainly: the neutral record is the asset, and it is walled off from anything that sells.

4. Corrections policy — and the founding example

Corrections are appended with a date; nothing is silently rewritten. Git history is the audit trail, and every published page renders original claims beside their dated corrections rather than merging them.

The founding example is the record's own: **Portfolio Synthesis v1 → v1.1 (July 2026).** The synthesis over-generalized from a curated corpus — reading a Port-of-Pensacola cluster as evidence about Triumph Gulf Coast's whole portfolio — and the human reviewer caught it. The correction was appended, dated, with the original preserved above it, and the corrected scope now governs every portfolio-level claim. A second correction followed the same path (v1.2, August 2026: a wage floor attributed to the wrong instrument, caught by extracting the instrument itself). The method caught its own author, twice. That is the credibility story, and this policy exists so it keeps happening in the open.

Coverage disclosure

COVERAGE — as of 2026-08-25
Decisions mapped ............ 7
Executed governing instrument (the GAA / lease / performance
agreement / construction contract creating the obligations each
page describes):
  IN HAND ................... 4 — american-magic-315 (S-89), st-titan-120 (S-41),
                              ihmc-233 (S-88), uwf-wave-330 (S-90)
  NOT RETRIEVED ............. 2 — believed to exist,
                              not yet obtained:
                              hpmce-dock-26-029, port-road-rail
  NONE EXISTS YET ........... 1 — pre-execution:
                              birdon-367
Watch-only .................. 1
Inclusion criteria .......... published at /evidence/#inclusion
Universe enumeration ........ IN PROGRESS — the full list of qualifying
                              decisions is being enumerated and will be
                              published; until then, this site does not
                              claim its coverage is representative.

All counts are derived at build time from the record (decision pages; the per-decision governing-instrument facts in record/decisions/instruments.yaml, joined against the hash-archived registry; watch-subject entries in the wanted list) — none is hand-typed. NOT RETRIEVED means the record believes an executed instrument exists and the corpus has not obtained it — absence from the corpus is a gap in the corpus, not a fact about the world.

Inclusion criteria

Decisions are included when they involve $1,000,000 or more in public funds or public assets committed by the City of Pensacola, Escambia County, or Triumph Gulf Coast within Escambia County, under an executed or pending instrument — or, at any amount, when a public instrument amends, funds, or directly serves a decision already in the corpus (the follow-on rule). Current coverage reflects extraction order, not a judgment of importance.

The design system (v1) — the status vocabulary

Colour carries meaning, never emphasis, and one build function assigns it. Two accents at most appear in any one view, and amber appears only where a monitored question (Q-xx) is actually attached.

self-reported / promotional — a claim made by a party about itself, always visibly badged. too_early exists in the record's working vocabulary and does not render; a rendered claim carrying it fails the build. Every decision page also prints to a one-page black-on-white brief (the ⎙ button) with the same statuses rendered in ink: solid rules for verified, dashed for the rest.

The machinery

The record is plain text in a public repository: markdown extraction runs, a YAML source registry with SHA-256 hashes, an immutable document archive, and generated JSON contracts (graph, sources, docket). A validation gate checks every citation, hash, and ID on every change. This site is a disposable view; the record is not.