Entity Errors

Entity Errors

Entity Errors — FinKore specification text, requirements, and related reading.

On this page

Status

FinKore Core 2.0.4 stable.

Purpose

This document defines initial portable entity failure categories.

Error Codes

CodeMeaning
FINKORE_ENTITY_INVALID_IDENTITYEntity identity is missing, unstable, or conflicts within its scope.
FINKORE_ENTITY_IMMUTABLEA requested mutation targets data immutable in the current state.
FINKORE_ENTITY_INVALID_MUTATIONA requested change is not a recognized or permitted domain mutation.
FINKORE_ENTITY_STATE_CONFLICTThe operation's expected state does not match current state.
FINKORE_ENTITY_VALIDATION_FAILEDOne or more Structural Validation or Business Validation rules failed.

Requirements

  • ENTITY-ERROR-001 — A Financial Entity failure MUST leave identity, current State, and entity data unchanged.
  • ENTITY-ERROR-002 — Validation failures SHOULD include stable violation identifiers.
  • ENTITY-ERROR-003 — Implementations MAY attach safe diagnostic context without changing portable code meaning.
  • ENTITY-ERROR-004 — A Workflow, Money, Approval, or Audit failure MUST retain its domain-specific code when that condition is the primary failure; it MUST NOT be replaced by FINKORE_ENTITY_VALIDATION_FAILED.

Entity evolution error mapping is defined by ENTITY-EVOLUTION-024 through ENTITY-EVOLUTION-028 in Entity Evolution. Core 2.0 does not introduce a dedicated evolution error code.

ENTITY-EVOLUTION-034 requires intrinsic Audit validation to precede evolution correspondence validation, preserving the primary Audit error if both fail. Valid Audit evidence that does not correspond to the requested evolution uses FINKORE_ENTITY_INVALID_MUTATION. ENTITY-EVOLUTION-035 uses that same Entity code for unresolved contradictory currentness history; a known, consistent currentness value that differs from a request's expectation instead uses FINKORE_ENTITY_STATE_CONFLICT under ENTITY-EVOLUTION-025. These distinctions do not define a total ordering of every possible Entity failure.

Malformed/unsupported validator declarations use FINKORE_ENTITY_INVALID_MUTATION under ENTITY-VALIDATION-009. A valid declared predicate rejecting data retains FINKORE_ENTITY_VALIDATION_FAILED.

Malformed mutability declarations use FINKORE_ENTITY_INVALID_MUTATION under ENTITY-MUTABILITY-008; a valid rule protecting a requested field instead uses FINKORE_ENTITY_IMMUTABLE. Malformed supplied Audit history, including explicit null, retains FINKORE_AUDIT_INVALID_EVENT under AUDIT-ERROR-004 and ENTITY-EVOLUTION-034. Constructing an adapter's failure observations cannot replace that primary domain error or imply a partial successful history import.

Invariants

A failed Financial Entity operation must not produce a partially valid Financial Entity.

Open Questions

  • Should a future specification version define a dedicated portable error catalog for additional evolution concepts if existing Entity errors become too broad?

Non-Goals

This is not a complete catalog and does not define concurrency control or transport errors.

Back to the top ↑