# ADR-001 — Existing Master Table Mapping

**Status:** APPROVED  
**Approved by:** Project owner  
**Date:** 2026-10-08

## Context

The Blueprint used logical master table names beginning with `tbl_`. Read-only
inspection of the authoritative hosting database found different physical names.
The project rules require the implementation to follow the existing hosting database
and prohibit renaming or rebuilding master tables without explicit approval.

## Decision

Use an adapter mapping between logical Blueprint names and physical hosting tables:

| Blueprint logical name | Authoritative physical table |
|---|---|
| `tbl_propinsi` | `wil_provinsi` |
| `tbl_kabkota` | `wil_kabkot` |
| `tbl_kecamatan` | `wil_kecamatan` |
| `tbl_kelurahan` | `wil_kelurahan` |
| `tbl_bank` | `bank` |
| `tbl_cabang` | `bank_cabang` |

All database-facing implementation must use the physical names through the approved
mapping. Logical module terminology may continue to use the Blueprint names.

## Consequences

- No database table is renamed, created, deleted, or migrated by this decision.
- Column names and types remain unconfirmed until PT-003 completes its metadata report.
- Physical column names and types in hosting are authoritative. Blueprint field names
  are logical examples and do not authorize renaming or migrating existing columns.
- Future repositories and queries must not hardcode the obsolete `tbl_` physical names.
- Any further physical-table mapping change requires another approved architecture decision.

The Kabupaten/Kota physical name was corrected from the initially supplied
`wil_kabkota` to the live `INFORMATION_SCHEMA` value `wil_kabkot` on 2026-10-08.