[Architecture] Define formal institutional decision semantics #33

New Issue

2026-08-01T00:00:52+02:00

zemion commented

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

Outcome

Create one formal outcome contract that can be reconstructed, reviewed, corrected, revoked, delivered, published, and linked to observed effects across Cases, Committee, and other domains.

Parent: #29

Decision record

Include subject/type, competent authority and mandate/jurisdiction, draft/options, facts, evidence, legal/rule versions, interpretation and reasoning, operative result, conditions, effective interval, downstream requested/observed effects, delivery/publication, remedy/review, correction, revocation, and provenance.

Boundary

Approvals owns review gates and separation of duties. Poll owns responses. Committee owns meeting, deliberation, and votes. Workflow Engine coordinates. Policy evaluates constraints. Audit records events. The Decisions capability owns the formal institutional outcome and lifecycle.

Start with a shared DTO/provider contract. Create govoplan-decisions when persistence and reuse outside one domain pass the repository threshold.

Acceptance criteria

One Committee or Case path separates proposal, approval/vote, formal outcome, dispatch, observed effect, and later correction.
Effective-time authority, actor/representation, facts, rule versions, reasoning, and evidence are inspectable.
Immutable history and explicit supersession preserve prior legal/institutional state.
Review/remedy, publication/redaction, retention, and access behavior are defined.
Automation can prepare or recommend, but the responsible human/system decision and assurance level remain explicit.

## Outcome Create one formal outcome contract that can be reconstructed, reviewed, corrected, revoked, delivered, published, and linked to observed effects across Cases, Committee, and other domains. Parent: https://git.add-ideas.de/GovOPlaN/govoplan/issues/29 ## Decision record Include subject/type, competent authority and mandate/jurisdiction, draft/options, facts, evidence, legal/rule versions, interpretation and reasoning, operative result, conditions, effective interval, downstream requested/observed effects, delivery/publication, remedy/review, correction, revocation, and provenance. ## Boundary Approvals owns review gates and separation of duties. Poll owns responses. Committee owns meeting, deliberation, and votes. Workflow Engine coordinates. Policy evaluates constraints. Audit records events. The Decisions capability owns the formal institutional outcome and lifecycle. Start with a shared DTO/provider contract. Create `govoplan-decisions` when persistence and reuse outside one domain pass the repository threshold. ## Acceptance criteria - One Committee or Case path separates proposal, approval/vote, formal outcome, dispatch, observed effect, and later correction. - Effective-time authority, actor/representation, facts, rule versions, reasoning, and evidence are inspectable. - Immutable history and explicit supersession preserve prior legal/institutional state. - Review/remedy, publication/redaction, retention, and access behavior are defined. - Automation can prepare or recommend, but the responsible human/system decision and assurance level remain explicit.

zemion added the module/committee module/approvals module/policy module/audit module/cases module/workflow area/governance area/security

area/api module/decisions labels 2026-08-01 00:00:52 +02:00

zemion referenced this issue

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

[Epic] Adopt the institutional governance target architecture #29

zemion referenced this issue from GovOPlaN/govoplan-cases

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

[Feature] Implement the govoplan-cases MVP #1

zemion commented

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

Codex State: progress

Summary

Core now defines a strict formal Decision DTO/provider contract with authority context, facts/evidence, rule versions, reasoning, operative result, requested/observed effects, delivery/publication, review/remedy, supersession, and protected serialization.
Committee proves proposal/approval-to-formal-outcome creation through optional mandate and decision capabilities.

Verification

Core semantic round-trip/redaction tests and Committee decision-path tests pass.

Next / Blocked

Persist immutable lifecycle history and prove dispatch, observed effect, correction/review, publication/redaction, and a second consuming domain before closing.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Core now defines a strict formal Decision DTO/provider contract with authority context, facts/evidence, rule versions, reasoning, operative result, requested/observed effects, delivery/publication, review/remedy, supersession, and protected serialization. - Committee proves proposal/approval-to-formal-outcome creation through optional mandate and decision capabilities. ### Verification - `Core semantic round-trip/redaction tests and Committee decision-path tests pass.` ### Next / Blocked - Persist immutable lifecycle history and prove dispatch, observed effect, correction/review, publication/redaction, and a second consuming domain before closing. Suggested status label: `status/in-progress`

zemion added

and removed

labels 2026-08-01 03:35:42 +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:59 +02:00

Codex State: done

Summary

Formal Decisions now preserve competent authority, responsible actor, automation assurance, facts, rule/evidence versions, reasoning, requested/observed effects, delivery/publication, remedy/review, and information governance.
Immutable OCC-guarded revisions enforce transitions and explicit supersession, correction, and revocation provenance; Committee is the first reconstructable consuming path.

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-decisions only after a second consumer and persistent lifecycle cross the repository threshold.

## Codex State: done ### Summary - Formal Decisions now preserve competent authority, responsible actor, automation assurance, facts, rule/evidence versions, reasoning, requested/observed effects, delivery/publication, remedy/review, and information governance. - Immutable OCC-guarded revisions enforce transitions and explicit supersession, correction, and revocation provenance; Committee is the first reconstructable consuming path. ### 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-decisions only after a second consumer and persistent lifecycle cross the repository threshold.

zemion closed this issue

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

zemion commented

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

Codex State: done

govoplan-decisions now owns immutable formal-decision revisions and protected reconstruction. Authority, subjects, facts, and legal bases cannot be silently rewritten; corrections, revocations, supersession, requested/observed effects, delivery/publication, remedy, and review references remain reconstructable. Committee records through decisions.registry when installed.

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-decisions` now owns immutable formal-decision revisions and protected reconstruction. Authority, subjects, facts, and legal bases cannot be silently rewritten; corrections, revocations, supersession, requested/observed effects, delivery/publication, remedy, and review references remain reconstructable. Committee records through `decisions.registry` when installed. - `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#33