Add poll-backed scheduling backend
This commit is contained in:
19
README.md
19
README.md
@@ -100,13 +100,18 @@ either module just to find a meeting time.
|
||||
|
||||
## First Package Scaffold Decision
|
||||
|
||||
The first implementation slice should add runtime APIs and WebUI routes around
|
||||
the existing manifest seed:
|
||||
The first backend implementation slice adds runtime APIs and storage around
|
||||
poll-backed scheduling requests:
|
||||
|
||||
- backend manifest, permissions, DTOs, and APIs for internal polls
|
||||
- WebUI route contribution for poll creation and response collection
|
||||
- capability contracts for calendar free/busy, access/IDM lookup,
|
||||
mail/notification sending, portal participation links, appointment handoff,
|
||||
and workflow/task follow-up
|
||||
- scheduling request, candidate slot, and participant storage
|
||||
- automatic `govoplan-poll` availability poll creation
|
||||
- signed poll invitations for internal or external participants
|
||||
- request lifecycle APIs: draft, collecting, closed, decided, handed off, cancelled
|
||||
- result summaries sourced from Poll response aggregation
|
||||
- calendar integration preferences and handoff metadata, without hard-coupling
|
||||
Scheduling to Calendar internals
|
||||
|
||||
The next slices should add the WebUI, notification delivery, real Calendar
|
||||
free/busy checks, and Calendar/Appointments event creation after decision.
|
||||
|
||||
The active backlog lives in Gitea issues.
|
||||
|
||||
Reference in New Issue
Block a user