[Feature] Implement campaign ownership transfer as a two-step process #21

Closed
opened 2026-07-06 11:23:53 +02:00 by zemion · 5 comments
Owner

Imported from the consolidated GovOPlaN product backlog.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md
  • Line: 175
  • Section: Milestones > Milestone 10 - Collaboration And Advanced Governance
  • Source status: PARTIAL.

Imported backlog item:

- [ ] Implement campaign ownership transfer as a two-step process.
<!-- codex-backlog-fingerprint:81bacbac3c5299005cae19e7 --> Imported from the consolidated GovOPlaN product backlog. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md` - Line: `175` - Section: `Milestones > Milestone 10 - Collaboration And Advanced Governance` - Source status: `PARTIAL.` Imported backlog item: ```markdown - [ ] Implement campaign ownership transfer as a two-step process. ```
zemion added this to the Milestone 10 - Collaboration And Advanced Governance milestone 2026-07-06 13:14:20 +02:00
Author
Owner

Codex State: needs-info

Summary

  • The current PUT owner endpoint changes ownership immediately; it should be replaced, not extended, by the generic workflow tracked in govoplan-core#276.
  • Business ownership, administrative recovery authority, and cryptographic key control are separate concepts. An administrative takeover must never silently grant E2EE plaintext or private keys.
  • A new govoplan-encryption module is not justified yet: existing boundaries already place envelope/content ownership in Postbox, device/key epochs in Identity Trust, policy in Policy, and generic key recovery/rotation work in Core.

Next / Blocked

  • Decide who accepts for a group owner: one authorized manager, a designated representative, or quorum.
  • Select default transfer expiry and deployment-profile assurance/quorum for exceptional recovery.

Suggested status label: status/needs-info

## Codex State: needs-info ### Summary - The current PUT owner endpoint changes ownership immediately; it should be replaced, not extended, by the generic workflow tracked in govoplan-core#276. - Business ownership, administrative recovery authority, and cryptographic key control are separate concepts. An administrative takeover must never silently grant E2EE plaintext or private keys. - A new govoplan-encryption module is not justified yet: existing boundaries already place envelope/content ownership in Postbox, device/key epochs in Identity Trust, policy in Policy, and generic key recovery/rotation work in Core. ### Next / Blocked - Decide who accepts for a group owner: one authorized manager, a designated representative, or quorum. - Select default transfer expiry and deployment-profile assurance/quorum for exceptional recovery. Suggested status label: `status/needs-info`
zemion added
status
needs-info
and removed
status
triage
labels 2026-07-30 05:28:20 +02:00
Author
Owner

The generic workflow and policy briefing is recorded in govoplan-core#276. Campaign should consume that contract rather than implement local transfer semantics. Recommended default is one authorized group manager, seven-day expiry, and standard administrative recovery using dedicated authority, MFA/re-authentication, delay, notification, and 2-of-N approval. Business ownership remains separate from any future encryption-key hand-over.

The generic workflow and policy briefing is recorded in `govoplan-core#276`. Campaign should consume that contract rather than implement local transfer semantics. Recommended default is one authorized group manager, seven-day expiry, and standard administrative recovery using dedicated authority, MFA/re-authentication, delay, notification, and 2-of-N approval. Business ownership remains separate from any future encryption-key hand-over.
Author
Owner

Completed through the generic platform workflow in Core f0898fc and Campaign integration/UI in 5f75035.

Campaign owners can propose a transfer; the target accepts or declines. A reader can request ownership; the current owner approves/declines and the requester performs final acceptance. Actions are cancellable, expiring, idempotent and audit/event visible. Group acceptance uses dedicated authority, and exceptional recovery is a separate high-assurance path. The legacy direct owner mutation route now returns a diagnostic conflict instead of bypassing the workflow.

Completed through the generic platform workflow in Core `f0898fc` and Campaign integration/UI in `5f75035`. Campaign owners can propose a transfer; the target accepts or declines. A reader can request ownership; the current owner approves/declines and the requester performs final acceptance. Actions are cancellable, expiring, idempotent and audit/event visible. Group acceptance uses dedicated authority, and exceptional recovery is a separate high-assurance path. The legacy direct owner mutation route now returns a diagnostic conflict instead of bypassing the workflow.
zemion removed the codex/needs-human
status
needs-info
labels 2026-07-30 17:46:59 +02:00
Author
Owner

Codex State: note

Summary

  • Decision confirmed: campaign ownership transfer follows the generic delegated acceptance, expiry, and administrative recovery/quorum model in Core #276.
## Codex State: note ### Summary - Decision confirmed: campaign ownership transfer follows the generic delegated acceptance, expiry, and administrative recovery/quorum model in Core #276.
Author
Owner

Codex State: note

Summary

  • Decision confirmed: campaign ownership transfer follows the generic delegated acceptance, expiry, and administrative recovery/quorum model in Core #276.
## Codex State: note ### Summary - Decision confirmed: campaign ownership transfer follows the generic delegated acceptance, expiry, and administrative recovery/quorum model in Core #276.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-campaign#21