[Feature] Add unified Postbox projections and explicit hierarchy-copy routing #24

New Issue

2026-07-28T23:01:06+02:00

zemion commented

2026-07-28 23:01:06 +02:00

Outcome

Users can group visible postboxes without merging ownership, and administrators can configure bounded linked-copy routing through organization hierarchy.

Acceptance criteria

Groupings preserve source postbox, receipt, retention, classification, and audit state.
Linked-copy routing is opt-in and records selected structure, target function mapping, maximum depth, stop conditions, classification gate, loop protection, and delivery-time route snapshots.
Copy, attention/escalation metadata, and shared visibility remain distinct behaviors.
Organization changes never retroactively expose historical messages.

## Outcome Users can group visible postboxes without merging ownership, and administrators can configure bounded linked-copy routing through organization hierarchy. ## Acceptance criteria - Groupings preserve source postbox, receipt, retention, classification, and audit state. - Linked-copy routing is opt-in and records selected structure, target function mapping, maximum depth, stop conditions, classification gate, loop protection, and delivery-time route snapshots. - Copy, attention/escalation metadata, and shared visibility remain distinct behaviors. - Organization changes never retroactively expose historical messages.

zemion added the module/organizations area/webui module/postbox area/governance codex/ready

labels 2026-07-28 23:01:06 +02:00

zemion commented

2026-07-29 00:19:21 +02:00

Codex State: progress

Unified source-preserving group projections are implemented, including safe retention of temporarily hidden preferences. The persistence model reserves explicit route/copy snapshots, but hierarchy propagation remains disabled by default. Linked-copy evaluation and administration remain under #18 because copy/escalation/visibility and vacancy policy must stay explicit.

## Codex State: progress Unified source-preserving group projections are implemented, including safe retention of temporarily hidden preferences. The persistence model reserves explicit route/copy snapshots, but hierarchy propagation remains disabled by default. Linked-copy evaluation and administration remain under #18 because copy/escalation/visibility and vacancy policy must stay explicit.

zemion added

and removed

labels 2026-07-29 00:20:19 +02:00

zemion commented

2026-07-31 15:21:56 +02:00

Closing as complete. This tracker duplicated the now-completed hierarchy-routing slice in #18 and the implemented source-preserving grouping foundation in #19.

Current evidence:

Groupings retain source Postbox identities and never merge message/receipt state.
Linked copies are opt-in and persist structure/relation, target-function/template mapping, maximum depth, stop conditions, classification/producer/retention gates, loop/deduplication diagnostics, and delivery-time path snapshots.
Copy, attention escalation, and shared visibility are separate policy sections.
Routed copies are distinct messages with independent receipts; historical access follows the frozen target/path rather than later hierarchy changes.
Dry-run and service tests cover no route, depth limits, parallel structures, cycles, duplicate paths, vacancy escalation, classification/producer/expiry gates, and tenant isolation.

Verification on 2026-07-31:

Postbox backend suite: 24 tests passed.
Postbox WebUI structure test passed.

Closing as complete. This tracker duplicated the now-completed hierarchy-routing slice in #18 and the implemented source-preserving grouping foundation in #19. Current evidence: - Groupings retain source Postbox identities and never merge message/receipt state. - Linked copies are opt-in and persist structure/relation, target-function/template mapping, maximum depth, stop conditions, classification/producer/retention gates, loop/deduplication diagnostics, and delivery-time path snapshots. - Copy, attention escalation, and shared visibility are separate policy sections. - Routed copies are distinct messages with independent receipts; historical access follows the frozen target/path rather than later hierarchy changes. - Dry-run and service tests cover no route, depth limits, parallel structures, cycles, duplicate paths, vacancy escalation, classification/producer/expiry gates, and tenant isolation. Verification on 2026-07-31: - Postbox backend suite: 24 tests passed. - Postbox WebUI structure test passed.

zemion closed this issue

2026-07-31 15:21:57 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-postbox#24