[Architecture] Define mandate, jurisdiction, and institutional authority semantics #30

New Issue

2026-07-31T23:59:09+02:00

zemion commented

2026-07-31 23:59:09 +02:00

Outcome

Answer why an institution, unit, or function is competent to act for a subject, territory, population, decision/signature type, and effective interval, independently of organization structure, incumbency, RBAC, and policy constraints.

Parent: #29

Boundary

Organizations owns units/functions.
IDM owns effective incumbency and delegation facts.
Access owns roles, permissions, and acting-context authorization.
Policy constrains use.
Mandates owns task/competence/jurisdiction/authority basis and effective history.

First proof

Define a versioned DTO/provider contract and use it in one Case or Decision path to answer: who was competent at the relevant time, through which function, under which basis, jurisdiction, and authority ceiling?

Repository threshold

Do not create govoplan-mandates until the proof requires independent persistence, lifecycle, security/operations behavior, release cadence, and at least two consumers or one complete reference process. Preserve the contract and stable IDs if extraction follows.

Acceptance criteria

Effective-dated task, jurisdiction, authority, basis, organization/function, and provenance are represented.
Historical resolution is deterministic and explainable.
Mandates never grants application permissions or copies organization/identity records.
Change, suspension, replacement, and conflict semantics are defined.
Admin/user/operator documentation and migration rules accompany the first persisted slice.

## Outcome Answer why an institution, unit, or function is competent to act for a subject, territory, population, decision/signature type, and effective interval, independently of organization structure, incumbency, RBAC, and policy constraints. Parent: https://git.add-ideas.de/GovOPlaN/govoplan/issues/29 ## Boundary - Organizations owns units/functions. - IDM owns effective incumbency and delegation facts. - Access owns roles, permissions, and acting-context authorization. - Policy constrains use. - Mandates owns task/competence/jurisdiction/authority basis and effective history. ## First proof Define a versioned DTO/provider contract and use it in one Case or Decision path to answer: who was competent at the relevant time, through which function, under which basis, jurisdiction, and authority ceiling? ## Repository threshold Do not create `govoplan-mandates` until the proof requires independent persistence, lifecycle, security/operations behavior, release cadence, and at least two consumers or one complete reference process. Preserve the contract and stable IDs if extraction follows. ## Acceptance criteria - Effective-dated task, jurisdiction, authority, basis, organization/function, and provenance are represented. - Historical resolution is deterministic and explainable. - Mandates never grants application permissions or copies organization/identity records. - Change, suspension, replacement, and conflict semantics are defined. - Admin/user/operator documentation and migration rules accompany the first persisted slice.

zemion added the module/policy module/access module/idm module/organizations area/governance

area/api module/mandates module/core labels 2026-07-31 23:59:09 +02:00

zemion referenced this issue

2026-08-01 00:00:54 +02:00

[Epic] Adopt the institutional governance target architecture #29

zemion commented

2026-08-01 03:33:01 +02:00

Codex State: progress

Summary

Core now defines strict effective-dated MandateDefinition, resolution request/result DTOs, conflict/suspension/replacement semantics, and a capability protocol.
Committee proves a bounded authority-resolution consumer without importing optional domain tables.

Verification

Core institutional contract and Committee decision-path tests pass.

Next / Blocked

Persist mandate lifecycle/history only when the repository threshold is met; add deterministic historical resolution, migration, and admin/operator surfaces before closing.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Core now defines strict effective-dated MandateDefinition, resolution request/result DTOs, conflict/suspension/replacement semantics, and a capability protocol. - Committee proves a bounded authority-resolution consumer without importing optional domain tables. ### Verification - `Core institutional contract and Committee decision-path tests pass.` ### Next / Blocked - Persist mandate lifecycle/history only when the repository threshold is met; add deterministic historical resolution, migration, and admin/operator surfaces before closing. Suggested status label: `status/in-progress`

zemion added

and removed

labels 2026-08-01 03:35:40 +02:00

zemion referenced this issue

2026-08-01 08:21:48 +02:00

[Epic] Adopt the institutional governance target architecture #29

zemion commented

2026-08-01 08:34:53 +02:00

Codex State: done

Summary

Core now defines deterministic, tenant-safe, effective-time Mandate resolution across task, authority, unit, function, jurisdiction, subject, status, and conflicts.
Immutable lifecycle revisions enforce OCC and permitted draft/active/suspended/replaced/retired transitions; Committee proves the contract without optional-module table imports.

Changed Files

govoplan-core/src/govoplan_core/core/institutional.py
govoplan-committee/src/govoplan_committee/backend/decision_path.py

Verification

Core institutional contract: 11 tests passed
Committee full suite: 3 tests passed

Next / Blocked

Create govoplan-mandates only when independent persistence, operations, and reuse cross the documented repository threshold.

## Codex State: done ### Summary - Core now defines deterministic, tenant-safe, effective-time Mandate resolution across task, authority, unit, function, jurisdiction, subject, status, and conflicts. - Immutable lifecycle revisions enforce OCC and permitted draft/active/suspended/replaced/retired transitions; Committee proves the contract without optional-module table imports. ### Changed Files - `govoplan-core/src/govoplan_core/core/institutional.py` - `govoplan-committee/src/govoplan_committee/backend/decision_path.py` ### Verification - `Core institutional contract: 11 tests passed` - `Committee full suite: 3 tests passed` ### Next / Blocked - Create govoplan-mandates only when independent persistence, operations, and reuse cross the documented repository threshold.

zemion closed this issue

2026-08-01 08:34:54 +02:00

zemion commented

2026-08-01 10:34:51 +02:00

Codex State: done

govoplan-mandates is now the persistent owner of effective-dated mandate, jurisdiction, competence, conflict, legal-basis, and evidence history. Its bounded SQL resolver is deterministic and fail-closed; Committee consumes mandates.resolver and retains the exact resolved revision.

tools/checks/check-focused.sh: passed, including 35 WebUI permutations and full-product bundle budgets.
Architecture manifest gate: 60/60 declarations; static contract graph: 60 modules, 98 providers, 54 requirements.
Release migration audit: valid graph including the four new module heads.
SQL-backed institutional golden journey, configuration-package preflight, module tests, Ruff, and startup smoke: passed.

Source push/tagging remains a separate release action.

## Codex State: done `govoplan-mandates` is now the persistent owner of effective-dated mandate, jurisdiction, competence, conflict, legal-basis, and evidence history. Its bounded SQL resolver is deterministic and fail-closed; Committee consumes `mandates.resolver` and retains the exact resolved revision. - `tools/checks/check-focused.sh`: passed, including 35 WebUI permutations and full-product bundle budgets. - Architecture manifest gate: 60/60 declarations; static contract graph: 60 modules, 98 providers, 54 requirements. - Release migration audit: valid graph including the four new module heads. - SQL-backed institutional golden journey, configuration-package preflight, module tests, Ruff, and startup smoke: passed. Source push/tagging remains a separate release action.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#30