GovOPlaN/govoplan-calendar
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Implement correlated campaign invitations

Browse Source
This commit is contained in:
zemion
2026-08-02 16:38:40 +02:00
parent 77a40ec2f9
commit 56d7b2108d
4 changed files with 404 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CALENDAR_INTEGRATION_CONCEPT.md
+12
View File
@@ -219,6 +219,18 @@ Tasks/workflow remain owners of assignment, status, SLA logic, and completion se
Mail remains owner of SMTP/IMAP profiles and mailbox transport. Notifications remains owner of delivery channels and delivery policy.
The versioned `calendar.invitations` capability is the concrete Campaign/Mail
boundary. Campaign renders and freezes one `METHOD:REQUEST` attachment per
recipient, then upserts the correlated VEVENT only after delivery acceptance.
Calendar owns attendee `PARTSTAT`, response timestamps, bounded evidence,
CalDAV outbox state, and batched correlation/summary queries. Mail can forward
`METHOD:REPLY` parts discovered by an authorized, checkpointed IMAP
delivery-status source. Replaying the same mailbox evidence is idempotent.
Campaign reports read current Calendar state and retain only the invitation
request and mirror result in their own delivery provenance. Recurring Campaign
invitation series remain a separate workflow rather than being inferred from
unrelated recipient rows.
### Documents And DMS
`govoplan-dms` can link documents to events for: