[Feature] Expose hierarchy and function-type resolution for function-scoped consumers #5

New Issue

2026-07-28T18:59:04+02:00

zemion commented

2026-07-28 18:59:04 +02:00

Outcome

Organizations exposes enough normalized structure for Postbox and other modules to address a function type across organizational units and to evaluate explicitly bounded ancestor/descendant rules without importing organization models.

Existing foundation

organizations.directory already resolves concrete units/functions and can enumerate functions below a unit. Function types and richer hierarchy queries are not yet part of the public Core capability.

Acceptance criteria

Add Core-owned refs and capability methods for organization unit types and function types.
Resolve concrete functions by function type and unit scope, and units by type/structure scope.
Provide tenant-safe batch ancestor/descendant/path resolution with maximum depth and cycle diagnostics.
Preserve structure/relation provenance where a tenant has parallel hierarchies; do not assume one universal parent chain for every purpose.
Return inactive/missing state explicitly so consumers can explain why an address is unavailable.
Emit versioned unit/function/type lifecycle events suitable for directory invalidation.
Do not import Postbox or IDM implementations.
Tests cover parallel structures, bounded ancestry, moved/deactivated units, function-type matching, and tenant isolation.

Consumer

This is a P1 foundation for function-scoped Postbox templates and bounded parent-copy routing.

## Outcome Organizations exposes enough normalized structure for Postbox and other modules to address a function type across organizational units and to evaluate explicitly bounded ancestor/descendant rules without importing organization models. ## Existing foundation `organizations.directory` already resolves concrete units/functions and can enumerate functions below a unit. Function types and richer hierarchy queries are not yet part of the public Core capability. ## Acceptance criteria - Add Core-owned refs and capability methods for organization unit types and function types. - Resolve concrete functions by function type and unit scope, and units by type/structure scope. - Provide tenant-safe batch ancestor/descendant/path resolution with maximum depth and cycle diagnostics. - Preserve structure/relation provenance where a tenant has parallel hierarchies; do not assume one universal parent chain for every purpose. - Return inactive/missing state explicitly so consumers can explain why an address is unavailable. - Emit versioned unit/function/type lifecycle events suitable for directory invalidation. - Do not import Postbox or IDM implementations. - Tests cover parallel structures, bounded ancestry, moved/deactivated units, function-type matching, and tenant isolation. ## Consumer This is a P1 foundation for function-scoped Postbox templates and bounded parent-copy routing.

zemion added the module/idm module/organizations module/postbox area/api codex/ready area/governance area/db

labels 2026-07-28 18:59:04 +02:00

zemion referenced this issue from GovOPlaN/govoplan-postbox

2026-07-28 18:59:04 +02:00

[Feature] Add function-scoped Postbox templates and stable unit-specific addresses #17

zemion referenced this issue from GovOPlaN/govoplan-postbox

2026-07-28 18:59:05 +02:00

[Feature] Add bounded hierarchy copy, visibility, escalation, and vacancy routing rules #18

zemion referenced this issue from GovOPlaN/govoplan-campaign

2026-07-28 18:59:05 +02:00

[Feature] Add Postbox as a governed Campaign delivery channel #81

zemion referenced this issue from GovOPlaN/govoplan-postbox

2026-07-28 18:59:06 +02:00

[Feature] Implement function-organization Postbox access through IDM, Organizations, and Core contracts #3

zemion referenced this issue from GovOPlaN/govoplan-postbox

2026-07-28 19:03:42 +02:00

[User Story] Deliver campaign messages to organizational function postboxes #16

zemion commented

2026-07-30 03:27:32 +02:00

Codex State: done

Summary

Added a backward-compatible, Core-owned organizations.hierarchyDirectory capability alongside the existing direct directory contract.
Implemented tenant-safe type/function resolution and explicit structure-scoped ancestor, descendant, and path batches with bounded depth, provenance, cycle diagnostics, and inactive/missing state.
Organization unit/function/type/structure/relation changes now emit versioned commit-coupled lifecycle events for consumer invalidation.

Changed Files

src/govoplan_organizations/backend/directory.py
src/govoplan_organizations/backend/api/v1/routes.py
src/govoplan_core/core/organizations.py

Verification

Organizations hierarchy/lifecycle suite: 5 tests passed; Ruff passed.
Affected Core Organizations/IDM compatibility suite: 20 tests passed.

Next / Blocked

Postbox #18 can now consume this capability for bounded parent-copy routing.

## Codex State: done ### Summary - Added a backward-compatible, Core-owned organizations.hierarchyDirectory capability alongside the existing direct directory contract. - Implemented tenant-safe type/function resolution and explicit structure-scoped ancestor, descendant, and path batches with bounded depth, provenance, cycle diagnostics, and inactive/missing state. - Organization unit/function/type/structure/relation changes now emit versioned commit-coupled lifecycle events for consumer invalidation. ### Changed Files - `src/govoplan_organizations/backend/directory.py` - `src/govoplan_organizations/backend/api/v1/routes.py` - `src/govoplan_core/core/organizations.py` ### Verification - `Organizations hierarchy/lifecycle suite: 5 tests passed; Ruff passed.` - `Affected Core Organizations/IDM compatibility suite: 20 tests passed.` ### Next / Blocked - Postbox #18 can now consume this capability for bounded parent-copy routing.

zemion closed this issue

2026-07-30 03:27:32 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-organizations#5