THE PUBLIC RECORD · COVERAGE & COLLECTION PLAN
What we know.
What we still need.
Community by community, follow the evidence behind San Diego's prosperity—and the work needed to make it complete.
Explore the verified collection, its reporting periods and its gaps. Collection, database ingestion, public release and a completeness audit are separate milestones.
01 / THE COLLECTION
A useful collection. An ongoing audit.
There is no honest “percent of everything” yet. The complete universe of obtainable records has not been enumerated. We can measure specific, defined source frames and show unresolved coverage explicitly.
What the counts mean
Normalized rows have different grains: documents, entities, relationships, financial flows, observations, geographies and general source records. They are not a count of unique people, payments or dollars.
Collected is different from public
The hosted database contains the accepted collection. The public explorer currently serves a bounded research publication and 20 verified Census exports. Broader database views remain unreleased.
Explore the public Census exports →
02 / COMMUNITY COVERAGE
These counts come from every row of the 20 checksum-verified public Census files. They show selected ACS observations for all 18 cities and the native county estimate. They do not establish complete prosperity or government-record coverage.
Unincorporated communities and neighborhoods: selected tract records exist, but a validated separate aggregate/crosswalk is not established by this release. ZIP codes, tracts, neighborhoods and supervisorial districts are different geographies. No city or tract median is averaged to invent a community estimate.
Row counts measure observations collected, not residents, statistical reliability or a community's prosperity. The county estimate includes incorporated and unincorporated areas. Overlapping ACS windows are not independent annual observations.
03 / AGENCIES & RECORD TYPES
See who publishes the evidence.
Source families are ingestion workstreams. Publisher names are source-reported labels; aliases have not been reconciled into unique agencies. Counts below cover each source's entire retained scope.
Trace a record through its stages
- IdentifiedA source is registered; records may still be inaccessible.
- RetrievedOriginal bytes retained with dates and checksums.
- NormalizedRecords transformed with provenance and validation.
- Database acceptedStored values and source bindings verified.
- Publicly releasedReuse, privacy and actual download checks passed.
- Coverage auditedA defined expected record set is reconciled, with gaps explained.
04 / YEARS & REPORTING PERIODS
Time is part of the evidence.
Keep four dates separate
- Event date: when a vote, payment or other event occurred.
- Reporting period: calendar, fiscal, election, tax or survey window.
- Retrieval date: when we obtained the source.
- Snapshot date: when this inventory was produced.
What a year filter can say
A source may cover multiple years, fiscal years, exact dates or a five-year survey window. The year filter below matches year text in the original period labels. It does not turn those labels into annual record counts.
Missing period metadata remains unknown. A date mentioned in a source title or URL is not silently substituted for a reporting period.
05 / THE COLLECTION PLAN
Broaden the evidence. Finish the connections.
This is an ordered work plan, not a claim of completed coverage or a promised delivery date. Apply the same evidence standards across communities and political actors.
1Community prosperity
Build Encinitas and city comparisons from verified ACS data. Define rent burden, poverty and uncertainty; add supported health, education, mobility and environmental measures.
2Community & year audit
Enumerate agencies and expected files for each reporting period. Establish neighborhood and district crosswalks. Reconcile missing periods and distinguish access failures from absent records.
3Decisions & resource flows
Connect budgets, contracts, awards, payments, grants, properties and projects. Preserve their different accounting meanings and prevent double counting.
4Accountability & outcomes
Connect decisions to recorded votes, recusals, stated rationales and public commitments; assess outcomes using explicit methods. Do not infer motives or causation from a connection.
Full collection checklist across the mission
- Government budgets, revenue, debt, procurement, payments, grants and audits.
- Nonprofit filings, boards, compensation, related parties and outcomes.
- Religious institutions' publicly documented entities, property and public-benefit activities; no inferred affiliation.
- Campaign filings, lobbying, disclosures, officials, committees, votes and commitments.
- Companies, ownership evidence, development, land transactions and incentives.
- Housing supply, affordability, evictions, homelessness programs and sustained outcomes.
- Transportation agencies, project delivery, service and ridership.
- Air, water, sewage, hazardous sites, enforcement and remediation.
- Health access/outcomes, schools, universities and training.
- Income, wages, employment, poverty, household stability, safety and mobility.
- Comparable counties and metropolitan areas with matching periods and definitions.
- Verified civic meetings/community events, source licensing, refresh schedules and accessible public releases.
THE SUPPORTING INVENTORY
Find the coverage behind a question.
Filter by community, publisher/agency label, family, year, period text, record type and collection state. Community matching uses verified ACS rows or explicit publisher/jurisdiction context. An agency's jurisdiction is not the location of every record or the place benefiting from spending.
The source-total column always spans all periods and geographies for that source. A year or community filter selects matching sources; it does not allocate their totals. Actual selected-community row counts are shown separately where verified public ACS records support them.