# HAV Seafood — Enterprise Entity Ownership Matrix

## Purpose

This workbook defines which HAV Seafood business domain is authoritative for each important static/master entity and how other domains may extend or reference that entity.

It is a governance layer for the synthetic business architecture. It does **not** contain operational or transactional history.

## Workbook contents

- **Entity_Ownership** — Main ownership matrix showing current authority, intended target authority, shared use, extension domains, reference domains and transition rules.
- **Domain_Registry** — Standard list and scope of HAV Seafood architecture domains.
- **Ownership_Rules** — Enterprise rules for master-data ownership, references, extensions and transitions.
- **Domain_Extension_Rules** — Examples of how major shared entities may be extended by other domains without redefining identity.
- **Production_Reconciliation** — Reconciles all entities in the existing Production reference register with their current and intended enterprise ownership.
- **Ownership_Statuses** — Defines Confirmed, Transitional, Provisional and Needs_Reconciliation states.
- **Architecture_Notes** — Key assumptions, boundaries and migration/adoption decisions.
- **Data_Dictionary** — Field definitions and datatypes for the workbook.

## Key ownership decisions

Production remains authoritative for the mature production-specific masters already created. Several existing entities are explicitly transitional: the future HR architecture should adopt the existing employee and role IDs; Finance should adopt the existing cost-center IDs; Quality should adopt existing quality/control-point IDs; and Maintenance & Engineering should adopt existing maintenance plan/task IDs.

Other domains may add domain-specific attributes, but they must retain the authoritative entity identifier rather than create competing master records.

## Relationship to other architecture

This workbook should be consulted whenever a new HAV Seafood domain architecture is created. New architectures should either own a new entity, extend an existing authoritative entity, or reference it. If ownership is still uncertain, the entity should remain provisional until the relevant architecture is designed.

System-of-record ownership is intentionally outside this workbook and will be defined later in the Enterprise Systems / System & Data Ownership architecture.
