Versioning and restoration of assets

This commit is contained in:
2026-05-06 09:00:07 +02:00
parent b8d087538e
commit df3b43d311
4 changed files with 346 additions and 10 deletions

View File

@@ -46,6 +46,11 @@ and SQLite repositories are adapters behind those ports.
transition, and denied mutations.
- Asset version records for create, content/representation changes, metadata
changes, and lifecycle changes.
- Optimistic `expected_current_version_id` conflict checks on stale-sensitive
asset mutations.
- Append-only asset restore operations that create new auditable versions.
- Asset supersession operations that create `superseded_by` relationships,
retire the source asset by default, and record a supersession version.
- Context entity persistence.
- Relationship persistence for asset-to-asset and asset-to-context-entity
links.
@@ -79,8 +84,7 @@ idempotency key.
## Not Yet Implemented
- Policy assignment storage and enterprise policy adapters.
- Conflict detection beyond version-sequence uniqueness.
- Restore and supersession service operations.
- Conflict detection beyond service-level optimistic version guards.
- Batch partial-failure envelopes.
These remain in scope for later `KONT-WP-0005` tasks or adjacent workplans.
@@ -103,3 +107,5 @@ These remain in scope for later `KONT-WP-0005` tasks or adjacent workplans.
- persistent metadata schema registry and assignment reload behavior,
- classification and metadata-record asset filtering across memory and SQLite
repositories.
- optimistic version conflict checks on asset mutations,
- restore and supersession as append-only versioned operations.