# HAV Seafood — Enterprise Identifier Standards

## Purpose

This workbook defines the enterprise-wide standards for identifiers, keys, datatypes, field names, statuses, booleans, code lists and cross-domain references used across the HAV Seafood synthetic business architecture.

It provides the rules that future HR, Procurement, Sales, Finance, IT, Quality, Logistics and operational datasets should follow without replacing the authoritative entity masters owned by those domains.

## Workbook contents

- **Identifier_Standards** — Current, legacy and reserved identifier conventions, examples, ownership and generation rules.
- **Datatype_Standards** — Standard logical datatypes and how they should be represented in Excel, CSV and JSON.
- **Field_Naming_Standards** — Naming conventions for fields such as `_ID`, `_Date`, `_DateTime`, `_Code` and `_Status`.
- **Key_Rules** — Primary-key, foreign-key, lifecycle, uniqueness and cross-file reference rules.
- **Status_Boolean_Rules** — Standard treatment of Active/Inactive states, Yes/No booleans, nulls and domain-specific states.
- **Code_List_Standards** — Governance rules for shared controlled codes such as countries, currencies, languages and units.
- **Domain_Prefixes** — Registry of current and reserved identifier prefixes across Shared Enterprise and Production.
- **Cross_Domain_Key_Rules** — Defines which authoritative IDs other business domains must use when referencing shared entities.
- **Legacy_Production_Map** — Reconciles the existing Production identifier register with the enterprise standards and records known exceptions.
- **Architecture_Notes** — Scope, principles, compatibility decisions and boundaries.
- **Data_Dictionary** — Field definitions for all sheets in the workbook.

## Key decisions

All identifiers are treated as **text**, even when they contain numeric characters. IDs are permanent, are not reused after inactivation, and do not change when an entity is renamed.

Existing Production identifiers are preserved rather than cosmetically renumbered. New enterprise datasets use consistent naming and datatype conventions while referencing the authoritative IDs owned by each domain.

Future enterprise IT systems reserve the `ESYS-*` pattern because Production already uses `SYS-*` as a valid Production Line/System identifier.

## Production compatibility and known exceptions

The Production reference register contains a small number of inconsistencies that are documented rather than silently changed:

- Factory areas use both `SEC-*` section IDs and `FA-*` detailed-area IDs.
- By-product documentation declares `BYP-*` but its example uses `BP-*`.
- Cleaning requirements declare `CLR-*` but their example uses `CR-*`.
- Cleaning methods declare `CLM-*` but their example uses `CLN-*`.

New IDs for the three conflicting Production entity types should not be generated until their authoritative source workbooks are reviewed.

## Boundaries

This workbook is a governance/reference architecture. It does not contain operational history, transactions, sales orders, production batches, inventory movements, invoices, maintenance events or other dated business activity.
