Sync Repo-README from project files

Repo-README.-.md

@@ -0,0 +1,49 @@
+<!-- codex-wiki-sync:f8cd549e8363e1671cd7e9ce -->
+
+> Mirrored from `/mnt/DATA/git/govoplan-scheduling/README.md`.
+> Origin: `repository`.
+> Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
+
+---
+# GovOPlaN Scheduling
+
+GovOPlaN Scheduling owns meeting scheduling and `Terminfindung`: finding suitable times across people, resources, calendars, constraints, and scheduling polls.
+
+This repository is currently a tag-only scaffold. It should gain package metadata and module manifests only after the first backend or WebUI slice is designed.
+
+## Scope
+
+Scheduling owns:
+
+- meeting scheduling polls and proposals
+- participant availability collection
+- time-window and resource constraints
+- candidate-slot ranking and conflict explanation
+- scheduling state, reminders, and decision handoff
+- optional links to external calendar/groupware systems through capabilities
+
+Scheduling does not own:
+
+- calendar primitives such as events, recurrence, availability storage, resources, and calendar adapters; those belong in `govoplan-calendar`
+- fixed-slot public or internal appointment booking; that belongs in `govoplan-appointments`
+- tasks, case work, approvals, and generic workflow state; those belong in `govoplan-tasks`, `govoplan-cases`, and `govoplan-workflow`
+- mail delivery or notifications; those belong in `govoplan-mail` and `govoplan-notifications`
+
+## Expected Integrations
+
+- `govoplan-calendar`: availability, calendars, resources, rooms, recurrence, Open-Xchange/calendar adapters
+- `govoplan-appointments`: conversion from a selected meeting time into a booked appointment where appropriate
+- `govoplan-access` and `govoplan-idm`: participants, groups, directory lookup, permissions
+- `govoplan-mail` and `govoplan-notifications`: invitations, reminders, confirmations
+- `govoplan-portal`: external participant scheduling flows
+- `govoplan-workflow` and `govoplan-tasks`: follow-up work after a time is selected
+
+## Initial Backlog
+
+The active backlog lives in Gitea issues. Start with:
+
+- define the scheduling module boundary
+- decide whether scheduling polls are internal-only, external/public, or both
+- define the relationship between scheduling proposals and calendar events
+- define privacy and retention rules for participant availability
+- define capability contracts with calendar, access, IDM, mail, notifications, portal, and appointments