[User Story] File and recover the assisted service-to-decision journey as an eAkte #8

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

Parent: #1

Prove the first Records reference package by filing digital and assisted intake evidence, representations, form versions, decisions, delivery/correction evidence and related files into equivalent records; close the record, start retention, apply a hold, restore it, search/reconstruct it and simulate archive transfer.

Acceptance: the actor can resume the journey through the UI and the evidence explains source, version, authority, purpose, policy, chronology and custody end to end.

Parent: #1 Prove the first Records reference package by filing digital and assisted intake evidence, representations, form versions, decisions, delivery/correction evidence and related files into equivalent records; close the record, start retention, apply a hold, restore it, search/reconstruct it and simulate archive transfer. Acceptance: the actor can resume the journey through the UI and the evidence explains source, version, authority, purpose, policy, chronology and custody end to end.
Author
Owner

Codex State: progress

Summary

  • Added an executable service-to-decision golden fixture covering a record, exact filed source, closure, retention, hold/release, appraisal, governed disposition and archive-transfer simulation.
  • The Records WebUI now exposes catalog, volume, chronology, lifecycle, hold, disposition, transfer and recovery controls without bypassing module boundaries.

Changed Files

  • tests/fixtures/service_to_decision_journey.json
  • tests/test_records.py
  • webui/src/features/records/RecordsPage.tsx
  • webui/src/features/records/RecordLifecyclePanel.tsx

Next / Blocked

  • Complete the resumable cross-module assisted journey: Forms Runtime intake, Case/Decision handoffs, delivery and correction branches, workflow task resume, and one real archive target.
  • Keep the journey module-optional and verify each degraded module combination before closure.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Added an executable service-to-decision golden fixture covering a record, exact filed source, closure, retention, hold/release, appraisal, governed disposition and archive-transfer simulation. - The Records WebUI now exposes catalog, volume, chronology, lifecycle, hold, disposition, transfer and recovery controls without bypassing module boundaries. ### Changed Files - `tests/fixtures/service_to_decision_journey.json` - `tests/test_records.py` - `webui/src/features/records/RecordsPage.tsx` - `webui/src/features/records/RecordLifecyclePanel.tsx` ### Next / Blocked - Complete the resumable cross-module assisted journey: Forms Runtime intake, Case/Decision handoffs, delivery and correction branches, workflow task resume, and one real archive target. - Keep the journey module-optional and verify each degraded module combination before closure. Suggested status label: `status/in-progress`
Author
Owner

Codex State: progress

The reference journey now has executable service-to-decision composition evidence and exact filing paths for Forms submissions, managed attachment evidence, Cases and formal Decisions. The product package records these required capabilities and the focused platform gate proves their module combination.

Commits: govoplan-forms-runtime@3c292b8, govoplan-files@aa9f90c, govoplan-cases@23f5091, govoplan-decisions@3845e06, govoplan-records@011c388, govoplan@69ba103.

Still open: one resumable actor-facing journey covering representation, delivery/correction evidence, closure, retention start, hold, restore/reconstruction and simulated archive transfer through the UI.

## Codex State: progress The reference journey now has executable service-to-decision composition evidence and exact filing paths for Forms submissions, managed attachment evidence, Cases and formal Decisions. The product package records these required capabilities and the focused platform gate proves their module combination. Commits: `govoplan-forms-runtime@3c292b8`, `govoplan-files@aa9f90c`, `govoplan-cases@23f5091`, `govoplan-decisions@3845e06`, `govoplan-records@011c388`, `govoplan@69ba103`. Still open: one resumable actor-facing journey covering representation, delivery/correction evidence, closure, retention start, hold, restore/reconstruction and simulated archive transfer through the UI.
Author
Owner

Extending the ready P1 journey with browser-level resume, action-layout, filing, reconstruction, retention/hold/recovery, and accessible digital/assisted evidence while preserving the existing exact-source contracts.

Extending the ready P1 journey with browser-level resume, action-layout, filing, reconstruction, retention/hold/recovery, and accessible digital/assisted evidence while preserving the existing exact-source contracts.
Author
Owner

Implemented and released in Records v0.1.20 (commit a5eee2c); workspace catalogue pin: GovOPlaN/govoplan@cc7c2a9.

Acceptance evidence:

  • The reference package now files equivalent authenticated-digital and assisted intake journeys, each with the exact form, attachment, case/representation, decision, delivery and correction evidence roles.
  • Deterministic multi-source providers record source/version, institutional authority, purpose, policy references, chronology and digests; replay is idempotent.
  • The Records UI can resume a record from the recordId URL context and exposes filing, evidence, governance and lifecycle/recovery actions through shared page/action-bar primitives.
  • Lifecycle coverage proves closure/retention, legal hold and blocked disposition, hold release, appraisal, independent approval and archive-transfer simulation.
  • SQLite backup/restore then proves search and current/historic reconstruction, source digest and manifest integrity, and the explicit boundary that Records does not take binary custody.
  • Static user/admin documentation and a records.reference-journey DocumentationTopic describe the workflow, limitations and operating consequences.

Verification passed: 24 Records tests, Ruff, full Core TypeScript compilation, manifest shapes (68/68), release-package registry checks, shared layout/primitive/foundation checks, and the complete focused workspace gate including 63 WebUI module permutations plus 8/8 Playwright conformance tests.

The target-tested external archive implementation remains tracked separately in #7 and does not block this reference-journey story.

Implemented and released in Records v0.1.20 (commit a5eee2c); workspace catalogue pin: GovOPlaN/govoplan@cc7c2a9. Acceptance evidence: - The reference package now files equivalent authenticated-digital and assisted intake journeys, each with the exact form, attachment, case/representation, decision, delivery and correction evidence roles. - Deterministic multi-source providers record source/version, institutional authority, purpose, policy references, chronology and digests; replay is idempotent. - The Records UI can resume a record from the recordId URL context and exposes filing, evidence, governance and lifecycle/recovery actions through shared page/action-bar primitives. - Lifecycle coverage proves closure/retention, legal hold and blocked disposition, hold release, appraisal, independent approval and archive-transfer simulation. - SQLite backup/restore then proves search and current/historic reconstruction, source digest and manifest integrity, and the explicit boundary that Records does not take binary custody. - Static user/admin documentation and a records.reference-journey DocumentationTopic describe the workflow, limitations and operating consequences. Verification passed: 24 Records tests, Ruff, full Core TypeScript compilation, manifest shapes (68/68), release-package registry checks, shared layout/primitive/foundation checks, and the complete focused workspace gate including 63 WebUI module permutations plus 8/8 Playwright conformance tests. The target-tested external archive implementation remains tracked separately in #7 and does not block this reference-journey story.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-records#8