Sync Repo-README from project files
+35
@@ -0,0 +1,35 @@
|
|||||||
|
<!-- codex-wiki-sync:ead218df16f02f4b96ad1a24 -->
|
||||||
|
|
||||||
|
> Mirrored from `/mnt/DATA/git/govoplan-cases/README.md`.
|
||||||
|
> Origin: `repository`.
|
||||||
|
> Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
|
||||||
|
|
||||||
|
---
|
||||||
|
# govoplan-cases
|
||||||
|
|
||||||
|
<!-- govoplan-repository-type:start -->
|
||||||
|
**Repository type:** module (domain).
|
||||||
|
<!-- govoplan-repository-type:end -->
|
||||||
|
|
||||||
|
`govoplan-cases` owns formal administrative case context for GovOPlaN.
|
||||||
|
|
||||||
|
The module should stay focused on case identity, lifecycle state, assignments,
|
||||||
|
deadlines, participants, evidence links, and case-level audit context. It should
|
||||||
|
not own forms, files, workflow execution, task queues, templates, payments, or
|
||||||
|
mail delivery; those are integrated through GovOPlaN capabilities, events,
|
||||||
|
commands, and DTOs.
|
||||||
|
|
||||||
|
The first executable headless slice exposes:
|
||||||
|
|
||||||
|
- `cases.service_intake`, which converts one published, effective Service
|
||||||
|
definition into a case intake plan while retaining the exact service,
|
||||||
|
mandate, jurisdiction, legal-basis, form, workflow, result, evidence, and
|
||||||
|
deadline references; and
|
||||||
|
- `cases.party_context`, which consumes an optional procedure-party provider
|
||||||
|
or a bounded Cases-only compatibility projection and emits policy-filtered,
|
||||||
|
frozen contact snapshot references for downstream delivery.
|
||||||
|
|
||||||
|
This slice does not yet persist case records or own institutional Service,
|
||||||
|
Party, representation, identity, address, Mandate, or Decision lifecycles.
|
||||||
|
|
||||||
|
See [docs/CONCEPT.md](docs/CONCEPT.md) for the current module concept.
|
||||||
Reference in New Issue
Block a user