[Task] Define provider-neutral workforce, desktop, and groupware integration profiles #16

New Issue

2026-08-06T14:11:31+02:00

zemion commented

2026-08-06 14:11:31 +02:00

Outcome

GovOPlaN uses stable provider-neutral contracts to integrate existing workforce, office, groupware, mail, calendar, and file tools before introducing custom desktop clients or native replacements.

Acceptance criteria

Catalogue standards, deep links, synchronization, protocol handlers, local agents, and provider APIs for Office/Outlook, LibreOffice, Thunderbird, file managers, Windows, Unix, macOS, and OpenDesk-style stacks.
Define authority, field ownership, conflicts, health, credentials, provenance, offline behavior, and retirement for each profile.
Treat LBV Baden-Wuerttemberg as a candidate workforce/payroll reference adapter once an authorized interface and test environment are available.
Reuse module-owned Mail, Calendar, Files, Organizations/IDM, Templates, and Workflow contracts rather than proxying their internals.
Select one bounded integration required by a reference journey before implementation.
Document security and deployment implications of browser, desktop, and local-agent options.

Source orientation: govoplan/docs/PRODUCT_INPUT_REGISTER.md.

## Outcome GovOPlaN uses stable provider-neutral contracts to integrate existing workforce, office, groupware, mail, calendar, and file tools before introducing custom desktop clients or native replacements. ## Acceptance criteria - Catalogue standards, deep links, synchronization, protocol handlers, local agents, and provider APIs for Office/Outlook, LibreOffice, Thunderbird, file managers, Windows, Unix, macOS, and OpenDesk-style stacks. - Define authority, field ownership, conflicts, health, credentials, provenance, offline behavior, and retirement for each profile. - Treat LBV Baden-Wuerttemberg as a candidate workforce/payroll reference adapter once an authorized interface and test environment are available. - Reuse module-owned Mail, Calendar, Files, Organizations/IDM, Templates, and Workflow contracts rather than proxying their internals. - Select one bounded integration required by a reference journey before implementation. - Document security and deployment implications of browser, desktop, and local-agent options. Source orientation: `govoplan/docs/PRODUCT_INPUT_REGISTER.md`.

zemion added the module/calendar module/mail module/connectors

module/files module/idm codex/needs-human area/governance

priority

p2

area/api labels 2026-08-06 14:11:31 +02:00

zemion commented

2026-08-21 14:22:28 +02:00

This provider-neutral profile issue is coupled to workspace #44 (workforce status) and #45 (real-time collaboration). To unblock it, select one bounded first profile and real provider rather than designing every workforce/desktop/groupware surface at once.

Decisions required: source-of-truth and write-back authority, system/tenant/user profile precedence, identity matching, offline/staleness behavior, conflict quarantine, credential custody, and retirement/revocation behavior.

Manual inputs: authorized provider API documentation, sandbox endpoint, credential/certificate material, synthetic directory/calendar/file/mail fixtures, rate-limit/error examples, and a documented operator owner. The autonomous framework can then add versioned profile configuration, dry connection tests, immutable sync evidence, replay-safe cursors, and provider-state diagnostics.

This provider-neutral profile issue is coupled to workspace #44 (workforce status) and #45 (real-time collaboration). To unblock it, select one bounded first profile and real provider rather than designing every workforce/desktop/groupware surface at once. Decisions required: source-of-truth and write-back authority, system/tenant/user profile precedence, identity matching, offline/staleness behavior, conflict quarantine, credential custody, and retirement/revocation behavior. Manual inputs: authorized provider API documentation, sandbox endpoint, credential/certificate material, synthetic directory/calendar/file/mail fixtures, rate-limit/error examples, and a documented operator owner. The autonomous framework can then add versioned profile configuration, dry connection tests, immutable sync evidence, replay-safe cursors, and provider-state diagnostics.

zemion added

and removed

labels 2026-08-21 14:22:29 +02:00

zemion commented

2026-08-23 11:23:49 +02:00

Decision update 2026-08-23: the recommended workforce boundary is approved (native governed effective-dated facts first; provider adapters later). The collaboration-provider and concrete desktop/groupware target choices remain open. The next autonomous work may define provider-neutral authority, provenance, health and retirement contracts, but a real adapter needs a named product/API plus an authorized test environment.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-connectors#16