Hecate Impact Resolver Canonical Reference

EPU external alias persistence reference

This reference binds the EPU external-alias semantics to a deterministic HNC v1.2 impact declaration. It is intentionally capability- and semantics-oriented: physical database topology and AWS service selection remain implementation decisions unless separately governed.

version: 1
persistence:
  - logical_object: ExternalAlias
    change_type: CREATE_LOGICAL_OBJECT
    derivation_authority: CANONICAL_REQUIRED
    requirement_ref: EPU-IDENTITY-INSTANCES:external-aliases
    storage_semantics:
      durability: persistent
      history: effective-dated
      immutability: state-transition-only
      volume_profile: high
      provenance_required: true
    fields:
      - field_name: alias_id
        semantic_definition: Immutable identifier of the governed alias relationship.
        logical_type: identifier
        required: true
        mutability: immutable
        classification: internal
        provenance_requirement: record
        registry_ref: null
        constraints: [unique]
      - field_name: epu_id
        semantic_definition: Reference to the immutable EPU product identity resolved by the alias.
        logical_type: reference
        required: true
        mutability: immutable
        classification: tenant-confidential
        provenance_requirement: record
        registry_ref: null
        constraints: [referential-integrity]
      - field_name: alias_type
        semantic_definition: Governed external product identifier type.
        logical_type: enum
        required: true
        mutability: immutable
        classification: internal
        provenance_requirement: field
        registry_ref: EPU External Alias Type Registry
        constraints: [registered-value]
      - field_name: alias_value
        semantic_definition: Normalized external product identifier value.
        logical_type: string
        required: true
        mutability: immutable
        classification: tenant-confidential
        provenance_requirement: field
        registry_ref: null
        constraints: [normalized]
      - field_name: source_eco_id
        semantic_definition: Organization identity defining the authority scope of the alias assertion.
        logical_type: reference
        required: true
        mutability: effective-dated
        classification: tenant-confidential
        provenance_requirement: evidence-linked
        registry_ref: null
        constraints: [authority-scope]
      - field_name: valid_from
        semantic_definition: Business-validity start timestamp for the alias assertion.
        logical_type: timestamp
        required: true
        mutability: immutable
        classification: internal
        provenance_requirement: record
        registry_ref: null
        constraints: []
      - field_name: valid_to
        semantic_definition: Business-validity end timestamp when the alias assertion is superseded or withdrawn.
        logical_type: timestamp
        required: false
        mutability: effective-dated
        classification: internal
        provenance_requirement: record
        registry_ref: null
        constraints: []
    keys:
      - key_type: primary
        fields: [alias_id]
        semantic_purpose: Stable identity of the alias relationship.
      - key_type: unique
        fields: [source_eco_id, alias_type, alias_value, valid_from]
        semantic_purpose: Prevent duplicate authoritative alias assertions within the same validity scope.
    relationships:
      - relationship_type: reference
        source_fields: [epu_id]
        target_logical_object: EPU
        target_fields: [epu_id]
        cardinality: many-to-one
        integrity_required: true
    indexes:
      - purpose: identity-resolution
        fields: [source_eco_id, alias_type, alias_value]
        uniqueness_required: false
      - purpose: temporal-query
        fields: [valid_from, valid_to]
        uniqueness_required: false
    policies:
      temporal:
        required: true
        policy_ref: EPU:effective-dated-aliases
        notes: Historical alias assertions remain reconstructable.
      tenant:
        required: true
        policy_ref: ZAYAZ:tenant-isolation
        notes: Alias discovery and access are tenant and authority scoped.
      security:
        required: true
        policy_ref: ZAYAZ:product-identity-access
        notes: Supplier-confidential identifiers require governed access.
      retention:
        required: true
        policy_ref: ZAYAZ:audit-retention
        notes: Historical identity-resolution lineage remains auditable.
    migration_required: true
    implementation_freedom:
      - Physical table decomposition may differ if all governed persistence semantics and constraints are preserved.
    migration:
      migration_type: CREATE
      compatibility_strategy: backward-compatible
      destructive_change: false
      downtime_expectation: none
rulesets:
  - impact_type: REUSE
    ruleset_ref: EPU:alias-conflict-resolution
    owner_ref: EPU
    derivation_authority: CANONICAL_REQUIRED
    requirement_ref: EPU-IDENTITY-INSTANCES:source-product-identity-resolution
    versioning:
      current_version: 1.0.0
      target_version: 1.0.0
      compatibility: unchanged
    test_scenarios:
      - scenario_id: alias-conflict-001
        given: The same source-scoped alias resolves to conflicting active EPU candidates.
        expected: Automatic assignment is rejected and the ambiguity is routed to human review.
infrastructure:
  - impact_type: CREATE_CAPABILITY
    derivation_authority: DERIVED_NECESSARY
    requirement_ref: EPU-IDENTITY-INSTANCES:external-aliases
    capability:
      class: database-storage
      semantic_purpose: Durable governed storage and indexed resolution of effective-dated EPU external aliases.
    capacity_profile:
      volume: high
      throughput: high
      latency: interactive
      burst: bursty
      growth: rapid
    security_requirements:
      - Tenant isolation
      - Supplier confidentiality
      - Least-privilege service access
    observability_requirements:
      - Alias-resolution latency
      - Conflict rate
      - Persistence and migration failures
    availability_requirements:
      - Identity resolution fails closed if authoritative persistence is unavailable.
    implementation_constraints:
      - Use approved ZAYAZ platform persistence architecture.
      - Do not select or introduce a new canonical database technology through HNC impact resolution.
unresolved: []

The directive is canonical input to Hecate, not an implementation script. It defines required semantics and capabilities while leaving authorized physical implementation choices to the engineering layer.