[Task] Define governed real-time collaboration channel profiles #45

Open
opened 2026-08-06 14:11:31 +02:00 by zemion · 2 comments
Owner

Outcome

GovOPlaN can use video meetings, chat, instant messaging, and forums as governed channels around institutional work without prematurely building another communications stack.

Acceptance criteria

  • Define provider-neutral meeting/thread/message/participant references and source-authority modes.
  • Define access, represented capacity, classification, retention, legal hold, export, correction, moderation, and evidence expectations.
  • Identify deep-launch, embed, synchronization, notification, and record-filing boundaries.
  • Compare integration with established providers against the bounded native functionality required by one reference journey.
  • Keep Mail, Postbox, Calendar, Committee, Files, Records, Search, and Notifications ownership intact.

Source orientation: docs/PRODUCT_INPUT_REGISTER.md.

## Outcome GovOPlaN can use video meetings, chat, instant messaging, and forums as governed channels around institutional work without prematurely building another communications stack. ## Acceptance criteria - Define provider-neutral meeting/thread/message/participant references and source-authority modes. - Define access, represented capacity, classification, retention, legal hold, export, correction, moderation, and evidence expectations. - Identify deep-launch, embed, synchronization, notification, and record-filing boundaries. - Compare integration with established providers against the bounded native functionality required by one reference journey. - Keep Mail, Postbox, Calendar, Committee, Files, Records, Search, and Notifications ownership intact. Source orientation: `docs/PRODUCT_INPUT_REGISTER.md`.
Author
Owner

Decision checkpoint before implementation:

  • Select one reference journey and first provider/protocol; meeting launch, durable team/thread, direct message, recording/transcript, and records filing have materially different authority and retention semantics.
  • Choose tenant-managed versus user-connected credentials and precedence, participant identity mapping, guest/federation policy, classification inheritance, recording/consent rules, moderation, retention/legal hold, and who may file a collaboration artifact into Records.
  • Decide which state GovOPlaN owns (governed references, intent, receipts) versus provider-owned mutable content.

Manual inputs: non-production provider tenant/room, API credentials/certificates, test identities including a guest, retention/recording policy, and provider receipt/error fixtures. Recommend starting with meeting/thread reference creation and immutable acknowledgement evidence, excluding recording content.

Decision checkpoint before implementation: - Select one reference journey and first provider/protocol; meeting launch, durable team/thread, direct message, recording/transcript, and records filing have materially different authority and retention semantics. - Choose tenant-managed versus user-connected credentials and precedence, participant identity mapping, guest/federation policy, classification inheritance, recording/consent rules, moderation, retention/legal hold, and who may file a collaboration artifact into Records. - Decide which state GovOPlaN owns (governed references, intent, receipts) versus provider-owned mutable content. Manual inputs: non-production provider tenant/room, API credentials/certificates, test identities including a guest, retention/recording policy, and provider receipt/error fixtures. Recommend starting with meeting/thread reference creation and immutable acknowledgement evidence, excluding recording content.
zemion added
status
needs-info
and removed
status
triage
labels 2026-08-21 14:22:28 +02:00
Author
Owner

Decision update 2026-08-23: the provider-neutral first-slice boundary is approved, but no first collaboration product has been selected. This issue therefore remains needs-info for a target-tested provider. The required selection context is: suite/provider, data-residency and deployment model, API/auth availability, immutable meeting/thread identifiers, retention/legal-hold/export behavior, and whether GovOPlaN deep-links, synchronizes metadata, or files selected content as a record.

Decision update 2026-08-23: the provider-neutral first-slice boundary is approved, but no first collaboration product has been selected. This issue therefore remains needs-info for a target-tested provider. The required selection context is: suite/provider, data-residency and deployment model, API/auth availability, immutable meeting/thread identifiers, retention/legal-hold/export behavior, and whether GovOPlaN deep-links, synchronizes metadata, or files selected content as a record.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#45