[Feature] Persist the native Records kernel and bitemporal file plan #2

Closed
opened 2026-08-06 00:28:34 +02:00 by zemion · 1 comment
Owner

Parent: #1

Implement the native eAkte persistence boundary: versioned file plans and record classes, stable record identities, volumes/parts, immutable record items and chronology, exact typed source references, tenant isolation, optimistic concurrency, valid/recorded time, institutional context, purpose capture, current authorization for historical reads, APIs, migrations, search projection, and uninstall/retirement guards.

Acceptance: native records remain reconstructable without another feature module; all writes are revision/idempotency guarded; temporal current/at/all reads never bypass current authorization.

Parent: #1 Implement the native eAkte persistence boundary: versioned file plans and record classes, stable record identities, volumes/parts, immutable record items and chronology, exact typed source references, tenant isolation, optimistic concurrency, valid/recorded time, institutional context, purpose capture, current authorization for historical reads, APIs, migrations, search projection, and uninstall/retirement guards. Acceptance: native records remain reconstructable without another feature module; all writes are revision/idempotency guarded; temporal current/at/all reads never bypass current authorization.
Author
Owner

Implemented and verified

The native Records kernel is now persistent and migration-backed:

  • bitemporal file-plan, record-class, record, volume, item, and chronology models;
  • tenant isolation, permission gates, optimistic revision checks, idempotent writes, and fail-closed restricted-record handling;
  • current and historical reads through the platform temporal context;
  • a permission-rechecked Records search projection; and
  • fresh-database Alembic coverage plus kernel, conflict, replay, cycle, temporal, tenant, and search tests.

Implemented in govoplan-records@f316523 with the shared contract in govoplan-core@5d12877.

Verification: Records 9-test suite, Core contract/module tests, 65-manifest validation, strict platform inventory, and the focused platform test battery all pass.

## Implemented and verified The native Records kernel is now persistent and migration-backed: - bitemporal file-plan, record-class, record, volume, item, and chronology models; - tenant isolation, permission gates, optimistic revision checks, idempotent writes, and fail-closed restricted-record handling; - current and historical reads through the platform temporal context; - a permission-rechecked Records search projection; and - fresh-database Alembic coverage plus kernel, conflict, replay, cycle, temporal, tenant, and search tests. Implemented in `govoplan-records@f316523` with the shared contract in `govoplan-core@5d12877`. Verification: Records 9-test suite, Core contract/module tests, 65-manifest validation, strict platform inventory, and the focused platform test battery all pass. <!-- codex-records-kernel-f316523 -->
zemion removed the
status
in-progress
label 2026-08-06 01:54:47 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-records#2