[Feature] Implement the govoplan-cases MVP #1

Closed
opened 2026-07-10 22:02:56 +02:00 by zemion · 5 comments
Owner

Moved from add-ideas/govoplan-core#118.

Reason: Cases MVP work belongs to the cases module.

Original issue body:

Imported from a backlog-like text file.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md
  • Line: 312
  • Source kind: product
  • Section: GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone B: Daily Administrative Work

Imported item:

Create `govoplan-cases` concept and MVP.

Remaining MVP Scope (reconciled 2026-07-20)

The module concept is complete in docs/CONCEPT.md; runtime implementation remains open.

Acceptance Criteria

  • Tenant-scoped case-type and status catalogs.
  • Create, list, read, and update APIs.
  • Parties, assignments, deadlines, and stable evidence references.
  • Case lifecycle events and audit references.
  • Case ACL and tenant-summary capability providers.
  • Basic /cases list and /cases/:caseId detail routes.
  • No direct imports from Forms, Files, Workflow, Tasks, or other sibling modules.

Architecture reconciliation (2026-07-31)

Procedure-party semantics are tracked in GovOPlaN/govoplan#32; formal decisions are tracked in GovOPlaN/govoplan#33.

Cases may keep minimal local party and outcome projections for a Cases-only composition, but must not grow identity/contact masters, effective-dated representation powers, mandate/jurisdiction, or generic formal-decision lifecycles. Persist stable provider references plus only the immutable role/outcome evidence snapshot needed to reconstruct the case, with an explicit migration path when shared providers are introduced.

Moved from add-ideas/govoplan-core#118. Reason: Cases MVP work belongs to the cases module. Original issue body: <!-- codex-generic-backlog-fingerprint:94dd33aef34d8eefdb50847e --> Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `312` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone B: Daily Administrative Work` Imported item: ```text Create `govoplan-cases` concept and MVP. ``` ## Remaining MVP Scope (reconciled 2026-07-20) The module concept is complete in `docs/CONCEPT.md`; runtime implementation remains open. ### Acceptance Criteria - [ ] Tenant-scoped case-type and status catalogs. - [ ] Create, list, read, and update APIs. - [ ] Parties, assignments, deadlines, and stable evidence references. - [ ] Case lifecycle events and audit references. - [ ] Case ACL and tenant-summary capability providers. - [ ] Basic `/cases` list and `/cases/:caseId` detail routes. - [ ] No direct imports from Forms, Files, Workflow, Tasks, or other sibling modules. ## Architecture reconciliation (2026-07-31) Procedure-party semantics are tracked in [GovOPlaN/govoplan#32](https://git.add-ideas.de/GovOPlaN/govoplan/issues/32); formal decisions are tracked in [GovOPlaN/govoplan#33](https://git.add-ideas.de/GovOPlaN/govoplan/issues/33). Cases may keep minimal local party and outcome projections for a Cases-only composition, but must not grow identity/contact masters, effective-dated representation powers, mandate/jurisdiction, or generic formal-decision lifecycles. Persist stable provider references plus only the immutable role/outcome evidence snapshot needed to reconstruct the case, with an explicit migration path when shared providers are introduced. <!-- codex-institutional-governance-cases-2026-07-31 -->
zemion changed title from [Feature] Create `govoplan-cases` concept and MVP to [Feature] Implement the govoplan-cases MVP 2026-07-20 14:34:50 +02:00
Author
Owner

Retained as the canonical Cases MVP issue. The concept already exists; the title and acceptance criteria now describe the remaining runtime slice. Scheduling is deferred while interface and Campaign work are prioritized.

Retained as the canonical Cases MVP issue. The concept already exists; the title and acceptance criteria now describe the remaining runtime slice. Scheduling is deferred while interface and Campaign work are prioritized.
Author
Owner

Codex State: progress

Summary

  • The repository is now an installable headless module with Service intake and optional Party-provider/compatibility capabilities.
  • The slice preserves institutional context, rejects provider access bypass and cross-tenant parties, and produces frozen delivery authority references.

Verification

  • Cases suite: 7 tests passed

Next / Blocked

  • Continue the Cases MVP with persistent case/type/status models, migrations, ACL, API, timeline, events, and list/detail WebUI.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - The repository is now an installable headless module with Service intake and optional Party-provider/compatibility capabilities. - The slice preserves institutional context, rejects provider access bypass and cross-tenant parties, and produces frozen delivery authority references. ### Verification - `Cases suite: 7 tests passed` ### Next / Blocked - Continue the Cases MVP with persistent case/type/status models, migrations, ACL, API, timeline, events, and list/detail WebUI. Suggested status label: `status/in-progress`
Author
Owner

Codex State: progress

Summary

  • Implemented the persistent Cases MVP and the missing /cases list plus /cases/:caseId detail workspace.
  • The UI supports search/status filtering, facts and typed links, immutable history/timeline, and OCC-guarded title/status revisions with explicit change reasons.

Verification

  • 10 focused Cases tests pass; the consolidated Core WebUI production build passes and includes both lazy Cases routes within bundle budgets.

Next / Blocked

  • Close after the source changes are pushed; finer case-specific shares remain a separate policy slice beyond this MVP acceptance boundary.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Implemented the persistent Cases MVP and the missing /cases list plus /cases/:caseId detail workspace. - The UI supports search/status filtering, facts and typed links, immutable history/timeline, and OCC-guarded title/status revisions with explicit change reasons. ### Verification - `10 focused Cases tests pass; the consolidated Core WebUI production build passes and includes both lazy Cases routes within bundle budgets.` ### Next / Blocked - Close after the source changes are pushed; finer case-specific shares remain a separate policy slice beyond this MVP acceptance boundary. Suggested status label: `status/in-progress`
Author
Owner

Codex State: done

Summary

  • The full MVP acceptance set is implemented locally, including catalogues, immutable revisions, APIs, events, ACL/summary providers, list/detail/history/timeline/share WebUI, and optional-provider boundaries.
  • Restricted cases now support explicit user/group and assignment-derived grants; exact Service launches are deterministic and replay-safe.

Changed Files

  • src/govoplan_cases
  • webui
  • docs/CONCEPT.md

Verification

  • 14 Cases tests passed; Ruff passed; integrated institutional journeys passed; Core WebUI production build passed.

Next / Blocked

  • Close after the implementation commit is pushed.
## Codex State: done ### Summary - The full MVP acceptance set is implemented locally, including catalogues, immutable revisions, APIs, events, ACL/summary providers, list/detail/history/timeline/share WebUI, and optional-provider boundaries. - Restricted cases now support explicit user/group and assignment-derived grants; exact Service launches are deterministic and replay-safe. ### Changed Files - `src/govoplan_cases` - `webui` - `docs/CONCEPT.md` ### Verification - `14 Cases tests passed; Ruff passed; integrated institutional journeys passed; Core WebUI production build passed.` ### Next / Blocked - Close after the implementation commit is pushed.
zemion added
status
in-progress
and removed
status
ready
labels 2026-08-01 14:56:04 +02:00
Author
Owner

Codex State: done

The verified implementation has been committed and pushed on main in c7821a5. The issue acceptance scope is complete; follow-on product depth remains tracked separately.

## Codex State: done The verified implementation has been committed and pushed on `main` in `c7821a5`. The issue acceptance scope is complete; follow-on product depth remains tracked separately.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-cases#1