# ER Visual Delivery Reconciliation

**Delivery version:** v2.0.1  
**Diagram-set version:** v2.0.0  
**Generated:** 2026-08-25  
**Read-only observation:** 2026-08-25 08:58:53-04  
**Current represented baseline:** `POST_0363_ACCEPTED / 0364 NOT_RUN`

## Snapshot reconciliation

The accepted architecture assessment v1.0.0 is valid point-in-time evidence at `POST_0356_VERIFIED_PENDING_MASTER_CONTROL`. It contained 698 application tables, 1,459 physical FKs, and 292 application views. That label is preserved on its source files and all new renders of those sources.

The live accepted database subsequently advanced. The read-only census used for this visual layer found exact committed registry state through:

- `0360_CNA2021_FULL_USABILITY_WP1_SEMANTIC_NORMALIZATION_V01`;
- `0361_CNA2021_ASSET001_SHARED_SCHEMA_HARDENING_V01`;
- `0362_CNA2021_ASSET001_COMPONENT_SOURCE_CANDIDATE_EXTRACTION_V01`;
- `0363_CNA2021_ASSET001_COMPONENT_CLASS_REFERENCE_HARDENING_V01`.

Migration 0364 was absent. Current visuals therefore use `POST_0363_ACCEPTED / 0364 NOT_RUN`; they do not rewrite the older assessment snapshot.

## Current coverage

| Measure | Reconciled result |
|---|---:|
| Application base/partitioned tables represented | **703 / 703** |
| Physical FK constraints reconciled | **1,475 / 1,475** |
| Within-subject physical FK edges drawn exactly | **938** |
| Cross-subject physical FK edges represented on high-level map as group-to-group counts | **537** |
| Application views cataloged | **301** |
| Current subject maps | **10** |
| Current family maps | **169** |
| Accepted v1.0.0 Mermaid family blocks rendered | **169 / 169** |
| Accepted v1.0.0 subject overviews rendered | **10** |
| Traditional detailed subject-sized ER diagrams | **25** |
| Distinct tables appearing in detailed diagrams | **435** |
| Distinct physical FKs appearing in detailed diagrams | **410** |
| Explicit logical/unenforced links appearing in detailed diagrams | **39** |
| Total SVG files | **384** |
| High-level PNG files | **1** |

The five tables added after the accepted v1.0.0 assessment are:

- `cske.capital_condition_component`;
- `cske.capital_recommendation_component`;
- `cske.core_component`;
- `cske.core_component_assignment`;
- `cske.core_ref_component_class`.

The current package has 16 more physical FKs and nine more application views than the v1.0.0 assessment snapshot.

## Intentional exclusions and readability divisions

- No protected data rows or values are included. Diagrams use catalog metadata, object names, key/column definitions, relationship definitions, and non-sensitive control identifiers only.
- The database-wide map intentionally aggregates physical FKs by content group. It does not print 1,475 individual lines.
- Current subject maps draw all 938 physical FKs whose endpoints are in the same subject. The 537 cross-subject FKs are represented as exact group-pair counts on the high-level map and remain individually enumerated in `evidence/current-foreign-key-catalog.csv`.
- Family maps are readability slices. Relationships leaving a family are visible at subject/high-level layers and in the exact FK catalog.
- Detailed diagrams intentionally select important reporting columns rather than every column. Each box states when more columns exist; the complete 10,822 table-column records remain in `evidence/current-column-catalog.csv`.
- Detailed diagrams are not exhaustive for every table. Broad/subject/family maps supply 703-table navigation; 25 detailed views drill into the reporting areas judged most material.
- Semantic/reporting views are selected when direct dependencies make them useful to the detailed subject. All 301 views and 971 dependency edges remain in the evidence catalogs.
- Existing accepted v1.0.0 Mermaid blocks did not draw cross-family relationships inside their Mermaid blocks; those relationships were listed separately in the source Markdown. The historic renders preserve that design rather than retroactively changing it.

## Logical or unenforced relationships

The detailed Annual Report diagrams show 38 logical links from typed `cske.atr_*` subject tables to `cske.atr_report_edition` by `report_edition_id`. They are high-confidence design relationships but remain physically unenforced in the current baseline.

The shared provenance diagram shows the governed polymorphic link between `cske.evidence_fact_assertion` and the evidence subject registry as a dashed logical relationship. Candidate/native identifiers and other possible cross-domain matches are not converted into ordinary FK lines without identity review.

Remaining unresolved relationship questions:

1. The 38 ATR edition-parent links still require a separately governed FK design/population UAT sequence (`DBA-ATR-003`).
2. Thirty same-named GIS-card table families remain present in `cske` and `cske_wilbraham_gis`. The diagrams distinguish schemas and do not imply that consumers may combine them. Cutover/decommission remains governed by `DBA-GIS-001` gates.
3. Source-native IDs and candidate mappings, including BUC account/parcel candidates and polymorphic subject IDs, remain logical/candidate links until conformance evidence and a separately accepted design establish canonical identity.
4. The new component tables are current physical structures, but CNA component business population remained outside this visual task; the diagrams do not infer populated/current component facts.
5. Reporting-view presence does not by itself establish semantic-contract or Master Control acceptance.

## Validation results

- Read-only database identity: `cske_dev`, `cske_owner`, PostgreSQL 18.4, transaction read-only `on`.
- Table, column, key, FK, view, view-column, dependency, migration, and baseline CSV exports completed without error.
- All 384 SVG files passed XML parsing.
- The high-level SVG converted successfully to a 3,200 × 1,992 PNG.
- HTML, SVG, source, evidence, and documentation link validation passed before sealing.
- No rendering failures occurred.
- Diagrams were divided into 10 subjects, 169 families, and 25 detailed views specifically to avoid one unreadable picture.
- No file or directory path component ends in the CloudDocs conflict suffix ` 2`.
- No `.DS_Store` file is present in the package or ZIP.
- Safari click-through covers index loading, search/filter, multiple diagram opens, zoom, pan, return navigation, source links, and keyboard controls; the durable result is in `evidence/SAFARI-CLICK-THROUGH-v2.0.1-20260825.md`.
- Safari's inability to directly display local `.mmd`/`.md` targets was resolved with an offline source reader; all 215 linked embedded texts matched their preserved files exactly.

## State-change confirmation

PostgreSQL and Git state were unchanged. No schema, data, sequence, grant, migration, loader, release, UAT, Master Control, deployment, reporting, or publication action was performed.