Entity Revisions

Entity Revisions

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

On this page

Status

FinKore Core 2.0.4 stable.

Purpose

This document refines Entity Revision semantics for imported and observed Financial Entities. It distinguishes stable Entity identity, business revision identity, and conflict-version tokens without defining persistence, deduplication, authorization, or a global identity registry.

Terminology

An Entity Revision is a stable, opaque identifier for a declared business observation or version of a continuing Financial Entity.

A Current Entity Revision is the revision identified by the caller or composing domain as current for the supplied Entity observation and revision scope.

A Historical Entity Revision is a preserved prior revision for the same stable Entity identity.

An Entity Conflict Version is an optional opaque precondition token used to detect stale observations. It is not an Entity Revision, stable Entity identity, database row identity, or display number.

Requirements

  • ENTITY-REVISION-001 - Entity Revision identity MUST be stable, opaque, and supplied by the caller or composing domain.
  • ENTITY-REVISION-002 - Entity Revision identity MUST remain distinct from stable Entity identity, display numbers, source-system identifiers, database row identity, storage counters, timestamps, and Entity Conflict Version unless a composing specification explicitly defines one immutable value as carrying both meanings.
  • ENTITY-REVISION-003 - A Current Entity Revision observation MUST identify the same stable Entity type and Entity identity as the Entity observation it qualifies.
  • ENTITY-REVISION-004 - A Historical Entity Revision observation MUST preserve the supplied revision identity and MUST NOT rewrite stable Entity identity, current lifecycle State, or current Entity data.
  • ENTITY-REVISION-005 - An implementation MUST NOT generate, increment, normalize, sort, or reinterpret Entity Revision identity from array order, lifecycle State, storage position, timestamps, display numbers, or mutable financial facts.
  • ENTITY-REVISION-006 - When both Entity Revision and Entity Conflict Version are supplied, they MUST remain independently observable and MUST NOT be substituted for one another during precondition checks.
  • ENTITY-REVISION-007 - A missing, malformed, duplicate, or identity-conflicting Entity Revision observation MUST fail with FINKORE_ENTITY_INVALID_IDENTITY unless a more specific primary domain error applies.

Invariants

Entity Revisions identify declared business observations. They do not replace stable Entity identity and do not define storage locking or a persistence transaction model.

Bounded import identity interpretation

In the bounded reference import representation, current business revision and conflict-version strings denote distinct tokens under ENTITY-REVISION-002. Supplying identical tokens without a composing-specification declaration of immutable shared meaning is identity-conflicting input and uses FINKORE_ENTITY_INVALID_IDENTITY under ENTITY-REVISION-007. The existing fixture has no shared-meaning declaration mechanism; an arbitrary input flag does not establish that exception.

This scoped interpretation does not require global string uniqueness across typed or separately scoped identifiers. A composing specification may still explicitly define one immutable value as carrying both meanings. Even then, independent observation and precondition checks remain required by ENTITY-REVISION-006.

Non-Goals

This document does not define concrete invoice revisions, optimistic locking algorithms, storage row versions, migration across Workflow definitions, or a global Entity registry.

Back to the top ↑