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

docs(postbox): define function-bound encrypted vault semantics

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-21 20:49:20 +02:00
parent a3c809c391
commit 5d141a0eaa
2 changed files with 67 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@@ -22,9 +22,18 @@ Core owns auth, tenants, RBAC evaluation, database/session primitives, module di
## Role-bound postboxes
A role-bound postbox is linked to an organizational unit and one or more roles. A person can access that postbox while their identity has an effective matching role in that organizational unit. Access is not tied to a login mailbox, personal email address, or static user assignment.
A function-bound postbox is linked to an organizational unit and one or more
institutional functions. It can exist with zero, one, or several current
incumbents. A person can access it only while their identity has an effective
assignment or time-bounded delegation in that organizational context. Access
is not tied to a login mailbox, personal email address, or static user
assignment.
When the role assignment changes, postbox access changes with it. The postbox keeps durable message and evidence history, while authorization remains derived from current platform role state.
When the assignment changes, postbox access and encrypted key grants change
with it. The postbox keeps durable content and evidence history through
vacancy, hand-over, and delegation; multiple incumbents receive independently
auditable access. Revocation prevents future platform key access but cannot
erase plaintext already fetched or exported.
## Module integration