Initialize Scheduling module manifest

README.md

@@ -8,9 +8,10 @@ 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, a backend manifest, and a WebUI package together when the first
-implementation slice is designed.
+This repository is initialized as a discoverable module seed. It exposes the
+module manifest, permission surface, role templates, and documentation metadata
+before runtime APIs, database models, migrations, and WebUI routes are
+introduced.
 
 The core boundary decision register is in
 `/mnt/DATA/git/govoplan-core/docs/MODULE_ARCHITECTURE.md`.
@@ -19,7 +20,7 @@ The core boundary decision register is in
 
 Scheduling owns:
 
-- meeting scheduling polls and proposals
+- meeting scheduling polls and proposals built on `govoplan-poll`
 - participant availability collection
 - time-window and resource constraints
 - candidate-slot ranking and conflict explanation
@@ -68,8 +69,20 @@ unless a configured process requires longer evidence retention.
 - `scheduling.decisionHandoff`
 - `scheduling.portalParticipation`
 
+## Manifest Dependency Decision
+
+The Scheduling manifest declares `poll` as a required dependency because
+availability collection and option/date poll primitives belong in
+`govoplan-poll`.
+
+The manifest declares `evaluation` as an optional dependency. Scheduling may
+trigger post-event or post-appointment feedback, but scheduling must not depend
+on the heavier evaluation model just to find a meeting time.
+
 ## Expected Integrations
 
+- `govoplan-poll`: required availability matrix and lightweight poll primitives
+- `govoplan-evaluation`: optional post-event, post-appointment, or process feedback
 - `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
@@ -79,8 +92,8 @@ unless a configured process requires longer evidence retention.
 
 ## First Package Scaffold Decision
 
-The first scaffold should include both backend and WebUI package metadata once
-implementation starts:
+The first implementation slice should add runtime APIs and WebUI routes around
+the existing manifest seed:
 
 - backend manifest, permissions, DTOs, and APIs for internal polls
 - WebUI route contribution for poll creation and response collection