Model scheduling as poll-backed workflow
This commit is contained in:
@@ -75,6 +75,13 @@ The Scheduling manifest declares `poll` as a required dependency because
|
||||
availability collection and option/date poll primitives belong in
|
||||
`govoplan-poll`.
|
||||
|
||||
Scheduling should model each meeting-finding flow as a poll-backed workflow:
|
||||
Poll owns candidate options, signed participation links, responses, visibility,
|
||||
and result aggregation. Scheduling stores the scheduling-specific context and
|
||||
uses Poll context fields to point back to its request or proposal resource.
|
||||
Typical workflow steps are collect availability, rank candidates, decide, notify
|
||||
participants, and hand off to Calendar or Appointments.
|
||||
|
||||
The manifest declares `access` and `evaluation` as optional dependencies.
|
||||
Scheduling may use Access for identity, groups, and permissions, and may trigger
|
||||
post-event or post-appointment feedback through Evaluation. It must not require
|
||||
|
||||
Reference in New Issue
Block a user