Sync Repo-docs-GOVOPLAN-MODULE-ROADMAP from project files

Repo-docs-GOVOPLAN-MODULE-ROADMAP.-.md

@@ -0,0 +1,52 @@
+<!-- codex-wiki-sync:b5f07d31c895a5b7c48a2db8 -->
+
+> Mirrored from `/mnt/DATA/git/govoplan-core/docs/GOVOPLAN_MODULE_ROADMAP.md`.
+> Origin: `repository`.
+> Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
+
+---
+# GovOPlaN Module And Integration Roadmap
+
+This page captures module and integration candidates that should be tracked in Gitea issues. It is durable planning context; implementation state, priorities, blockers, and acceptance criteria belong on the linked issues.
+
+## Existing Platform Modules
+
+- `govoplan-access`: authentication, accounts, sessions, API keys, groups, memberships, RBAC, principal resolution, and identity integrations.
+- `govoplan-tenancy`: tenants, lifecycle, tenant settings, switching, delete vetoes, and erasure orchestration.
+- `govoplan-policy`: permission catalogues, hierarchical policy decisions, delegation ceilings, explainability, and simulations.
+- `govoplan-audit`: audit sink, audit queries, exports, evidence bundles, and compliance traceability.
+- `govoplan-admin`: administrative shell and module-contributed admin surfaces.
+
+## Existing Service And Business Modules
+
+- `govoplan-files`: managed files, storage spaces, sharing, downloads, metadata, and future document storage boundaries.
+- `govoplan-mail`: SMTP/IMAP profiles, credentials, sending, mailbox views, policy, and mail workflow integration.
+- `govoplan-campaign`: campaign authoring, validation, review/send control, reports, and recipient-driven communication.
+
+## Proposed Missing Modules
+
+- `govoplan-projects`: project management abstractions and OpenProject integration.
+- `govoplan-datasources`: database, CSV, file, API, and external system source definitions.
+- `govoplan-dataflow`: pipelines that connect datasources, transform data, and feed BI/reporting outputs.
+- `govoplan-reports`: templates, letters, documents, dashboards, exports, scheduled reports, and report rendering.
+- `govoplan-file-connectors`: Nextcloud, Seafile, SMB, NFS, WebDAV, S3, and DMS/eAkte storage connectors.
+- `govoplan-connectors`: catalogue and runtime for public-sector software integrations, including import/link/replace strategies.
+- `govoplan-recipients`: address management, adrema-style recipient lists, email lists, postal-letter recipients, and audience segmentation.
+- `govoplan-sources`: consume sources, normalize provenance, publish sources, emit feeds, and track source-to-source workflows.
+- `govoplan-calendar`: calendars, scheduling, Terminplaner, Terminbuchung, appointment availability, booking flows, and reminders.
+- `govoplan-documents`: collaborative document workflows, document state, review, locking, and file-module boundaries.
+- `govoplan-forms`: reusable form definitions, submissions, validation, and workflow handoff.
+- `govoplan-opendesk`: integration profile for the OpenDesk stack: Open-Xchange, Nextcloud, OpenProject, LDAP, Active Directory, OIDC/SAML, SCIM, and related shared identity/document/project capabilities.
+
+## Integration Questions
+
+- Which public-sector systems are common enough to be first-class GovOPlaN connectors?
+- For each external system, should GovOPlaN integrate, link, import, synchronize, or replace the workflow?
+- Which modules own source consumption versus source publishing?
+- Which document collaboration features belong in `govoplan-files`, and which require a separate `govoplan-documents` module?
+- Should calendar, appointment booking, and Terminplaner live in one module or split into calendar plus booking modules?
+- Should reports/templates be one module initially, or split into document templates, report rendering, and BI dashboards later?
+
+## Routing Rule
+
+Create implementation issues in the owning module repository when the module exists. Create proposal and split-design issues in `govoplan-core` when the module is missing or cross-cutting.