[Feature] Add native transfer packages and one tested eAkte/archive provider #7

Open
opened 2026-08-06 00:28:35 +02:00 by zemion · 2 comments
Owner

Parent: #1

After the native contract stabilizes, implement transfer manifests and one target-tested xDOMEA/archive provider profile, including capability/health/freshness state, receipts, retry/reconciliation and explicit native/external/hybrid authority modes. Naming a standard is not a conformance claim.

External decision: select and provide the first target archive/DMS endpoint and conformance profile.

Parent: #1 After the native contract stabilizes, implement transfer manifests and one target-tested xDOMEA/archive provider profile, including capability/health/freshness state, receipts, retry/reconciliation and explicit native/external/hybrid authority modes. Naming a standard is not a conformance claim. External decision: select and provide the first target archive/DMS endpoint and conformance profile.
Author
Owner

Codex State: needs-info

Summary

  • Implemented the neutral Core records.archive. capability, runtime provider-contract validation, exact-source transfer manifests, deterministic package checksums and persisted dispatch receipts.
  • Implemented an explicitly simulated provider and UI/status semantics that never claim archival custody; real-provider dispatch is rejected unless the provider declares a target-specific recovery profile.

Changed Files

  • /mnt/DATA/git/govoplan-core/src/govoplan_core/core/records.py
  • src/govoplan_records/backend/archive.py
  • src/govoplan_records/backend/service.py

Verification

  • Core archive contract tests and Records transfer/recovery tests pass.

Next / Blocked

  • Select the first target archive/DMS endpoint and conformance profile (for example a concrete xDOMEA/export profile), including its authentication, acceptance receipt and outcome-reconciliation behavior.
  • After that selection, implement and run the target-system transfer conformance fixture before closing this issue.

Suggested status label: status/needs-info

## Codex State: needs-info ### Summary - Implemented the neutral Core records.archive.<provider> capability, runtime provider-contract validation, exact-source transfer manifests, deterministic package checksums and persisted dispatch receipts. - Implemented an explicitly simulated provider and UI/status semantics that never claim archival custody; real-provider dispatch is rejected unless the provider declares a target-specific recovery profile. ### Changed Files - `/mnt/DATA/git/govoplan-core/src/govoplan_core/core/records.py` - `src/govoplan_records/backend/archive.py` - `src/govoplan_records/backend/service.py` ### Verification - `Core archive contract tests and Records transfer/recovery tests pass.` ### Next / Blocked - Select the first target archive/DMS endpoint and conformance profile (for example a concrete xDOMEA/export profile), including its authentication, acceptance receipt and outcome-reconciliation behavior. - After that selection, implement and run the target-system transfer conformance fixture before closing this issue. Suggested status label: `status/needs-info`
Author
Owner

Decision/implementation update 2026-08-23: d.velop d3 DMS is the selected first target. govoplan-dms v0.1.19 provides the target profile and fail-closed store-plan/preflight foundation. This issue remains open because acceptance requires target-tested custody, receipt, retry/reconciliation and recovery evidence. Required manual inputs are the d3 sandbox/endpoint, repository and object-definition mapping, Origin, credential envelope, custody meaning and a correlation lookup/recovery procedure. No xDOMEA conformance is claimed by this slice.

Decision/implementation update 2026-08-23: d.velop d3 DMS is the selected first target. govoplan-dms v0.1.19 provides the target profile and fail-closed store-plan/preflight foundation. This issue remains open because acceptance requires target-tested custody, receipt, retry/reconciliation and recovery evidence. Required manual inputs are the d3 sandbox/endpoint, repository and object-definition mapping, Origin, credential envelope, custody meaning and a correlation lookup/recovery procedure. No xDOMEA conformance is claimed by this slice.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-records#7