# Existing data-source connections: coverage and boundaries

**Release:** v0.3.8  
**Checkpoint:** `20260814 v2 Checkpoint.zip`  
**Checkpoint capture:** August 14, 2026 at 1:17:58 p.m. EDT  
**Connection date:** August 14, 2026

## What this release connects

The reporting path now includes the previously omitted decision-critical domains identified in the August 14 coverage-gap review:

- capital-project components, funding, cost observations, financing cost, interim financing, debt-issue bridges, operating context, service metrics, and reconciliation;
- security-level maturities, coupons, pricing, contractual cash flows, legal authorizations, BAN links, redemption terms, parties, continuing-disclosure terms, and official-statement changes;
- HWRSD governance, operations, workforce, reserves, services, facility events, and financial rules;
- audited financial statements, statement rows and values, nonmajor-fund facts, notes, supporting schedules, audit engagement, and opinion records;
- normalized financial observations, General Fund facts, disclosure mappings, the disclosure-compliance event, and open follow-ups;
- property-card assessment components, land, construction, notes, improvements, sale history, multi-year valuation, assessment-account history, findings, and QA controls;
- property constraints, investigations, possible outcomes, environmental features, and links to assets and parcels;
- four database scenario families, six working variants, asset actions, function assignments, parameters, execution requirements, linked constraints, delivery components, leaseback terms, and risks;
- the complete core asset/building/parcel-link registry and the source-artifact alias, relationship, system, and quality-exception graph.

All base tables in the checkpoint appear in `DATA-SOURCE-CONNECTION-REGISTER.csv`. Decision-critical business relations receive row-level CSV extracts. Very large page, line, numeric-token, crosswalk, and other provenance relations are connected by relation count and QA role rather than reproduced as resident-facing financial tables.

## Evidence-status boundary

- The packaged v0.3.8 extracts were produced from the supplied custom-format checkpoint and checked against the checkpoint's exact table-count catalog. This is a verified checkpoint extraction, not a claim that the live `cske_dev` database was executed from this environment.
- The Mac launcher performs read-only queries against the configured live database, regenerates the extracts, and records the runtime result in its execution log.
- Database rows preserve their own source, verification, status, and reconciliation fields. Packaging does not upgrade `WORKING`, `PREPARED`, `PRELIMINARY`, `UNRESOLVED`, or similar records to adopted, executed, or verified decisions.

## Interpretation boundaries

- Record counts are not counts of unique financial facts. They include facts, dimensions, links, controls, source rows, and provenance.
- Funding records can represent authorizations, estimates, final par, transfers, grants, reserves, or other measurement bases. They are not automatically additive.
- Contractual cash-flow rows cover historical and current issues. They are not a security-level current-outstanding balance and are not one affordability total.
- Audit assurance belongs only to the entity, period, scope, and statement identified in the audit record. The loaded engagement and opinion tables describe the HWRSD FY2024 audit; they are not extended to other filings.
- The February 17, 2026 disclosure-compliance event is loaded as `FOLLOW_UP_REQUIRED`. Reporting it does not resolve it.
- Property assessments are assessment records, not market appraisals, replacement costs, insurance values, project estimates, or guaranteed sale proceeds.
- The Memorial School FY2024-to-FY2025 building-value decline is confirmed in the loaded assessment history, but its cause remains unresolved.
- Property constraints and the reported pond/wetland feature remain preliminary or unresolved. They are not title opinions, surveys, wetland delineations, Article 97 determinations, or final legal conclusions.
- Scenario families and variants are working configurations. Their assumed actions, unresolved function assignments, blocking requirements, risks, and 30-year comparison horizon are not adopted policy, cost estimates, appraisals, or recommendations.
- Empty receiving tables represent missing evidence, not a financial zero.

## Cross-domain bridge boundary

`CROSS-DOMAIN-BRIDGE-REGISTER.csv` distinguishes complete connections from partial bridges. In particular, not every project has an explicit warrant-article or asset foreign key; not every grant has an article/account/closeout bridge; and an exact household allocation of HWRSD cost remains unavailable.