[Feature] Enforce information-governance adoption across module object types #40

New Issue

2026-08-05T16:21:19+02:00

zemion commented

2026-08-05 16:21:19 +02:00

Outcome

Every module-owned object type applies temporal browsing, purpose-aware access, retention/legal-hold behavior, and institutional acting context consistently and can prove the claim from tests and documentation.

Current baseline

Core contract version 1 defines contract_only, partial, enforced, and not_applicable declarations. Runtime metadata, strict inventory, manifest checks and signed catalogs retain those claims. The 2026-08-05 all-contract-only baseline is historical. A targeted current-manifest extraction and strict manifest check on 2026-09-08 found 72 modules / 288 dimensions: 7 enforced, 281 contract_only, 0 partial. Cases enforces temporal, purpose and institutional dimensions while retaining an explicit retention limitation; Records enforces all four. See Cases #6, the owning module manifests/tests, and the reconciliation in #39. Broad reference-package adoption and target evidence remain incomplete; this issue stays open. These are source enforcement declarations, not a target certification.

Temporal read adoption already has the focused child issue #39.

Work packages

Inventory owned object types and classify every read, decision, external effect, retention action, and institutional reference.
Apply valid-time and recorded-time selection only to historical/display reads; current authorization always remains current.
Carry declared purpose through authorization, external effects, evidence, and audit without using free-form purpose text as proof by itself.
Implement retention schedules, holds, appraisal/disposition gates, and immutable evidence where applicable.
Resolve tenant, organization, function, acting/delegation, and source-authority context explicitly.
Declare object types, evidence, and limitations in each module manifest.
Add route/query/effect tests and module-owned user/admin documentation.

Acceptance criteria

Reference-package modules have no applicable contract_only dimensions.
Every enforced claim names executable evidence that strict manifest checks can resolve.
Historical selection cannot restore expired permission, delegation, routing, policy, or execution authority.
Unsupported dimensions are shown as limitations rather than implied globally.
Signed package catalogs and target evidence preserve the exact adoption claims.

Architecture: docs/strategy/STRATEGY_STATUS.md and govoplan-core/docs/INFORMATION_GOVERNANCE_ADOPTION.md.

## Outcome Every module-owned object type applies temporal browsing, purpose-aware access, retention/legal-hold behavior, and institutional acting context consistently and can prove the claim from tests and documentation. ## Current baseline Core contract version 1 defines `contract_only`, `partial`, `enforced`, and `not_applicable` declarations. Runtime metadata, strict inventory, manifest checks and signed catalogs retain those claims. The 2026-08-05 all-contract-only baseline is historical. A targeted current-manifest extraction and strict manifest check on **2026-09-08** found **72 modules / 288 dimensions: 7 enforced, 281 contract_only, 0 partial**. Cases enforces temporal, purpose and institutional dimensions while retaining an explicit retention limitation; Records enforces all four. See [Cases #6](https://git.add-ideas.de/GovOPlaN/govoplan-cases/issues/6), the owning module manifests/tests, and the reconciliation in #39. Broad reference-package adoption and target evidence remain incomplete; this issue stays open. These are source enforcement declarations, not a target certification. Temporal read adoption already has the focused child issue #39. ## Work packages - Inventory owned object types and classify every read, decision, external effect, retention action, and institutional reference. - Apply valid-time and recorded-time selection only to historical/display reads; current authorization always remains current. - Carry declared purpose through authorization, external effects, evidence, and audit without using free-form purpose text as proof by itself. - Implement retention schedules, holds, appraisal/disposition gates, and immutable evidence where applicable. - Resolve tenant, organization, function, acting/delegation, and source-authority context explicitly. - Declare object types, evidence, and limitations in each module manifest. - Add route/query/effect tests and module-owned user/admin documentation. ## Acceptance criteria - Reference-package modules have no applicable `contract_only` dimensions. - Every `enforced` claim names executable evidence that strict manifest checks can resolve. - Historical selection cannot restore expired permission, delegation, routing, policy, or execution authority. - Unsupported dimensions are shown as limitations rather than implied globally. - Signed package catalogs and target evidence preserve the exact adoption claims. Architecture: `docs/strategy/STRATEGY_STATUS.md` and `govoplan-core/docs/INFORMATION_GOVERNANCE_ADOPTION.md`.

zemion added the module/policy area/db area/governance area/security

area/api area/webui module/core labels 2026-08-05 16:21:19 +02:00

zemion commented

2026-08-05 16:49:52 +02:00

Codex State: progress

Summary

Introduced the four-dimension manifest contract for temporal, purpose, retention, and institutional-context behavior; maturity claims now require enforcement evidence.
The initial 65-module inventory intentionally reports all 260 dimension declarations as contract_only, so rollout work remains visible instead of being overstated.

Changed Files

docs/INFORMATION_GOVERNANCE_ADOPTION.md
tools/inventory/platform-interface-inventory.py

Verification

tools/checks/check-manifest-shapes.py --strict: 65/65 manifests valid
tools/inventory/platform-interface-inventory.py --strict: 260 contract_only, 0 partial/enforced
tools/checks/check-focused.sh: passed, including 50 WebUI module permutations

Next / Blocked

Adopt the contract object type by object type, beginning with the three reference journeys; record concrete tests/evidence before promoting a dimension.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Introduced the four-dimension manifest contract for temporal, purpose, retention, and institutional-context behavior; maturity claims now require enforcement evidence. - The initial 65-module inventory intentionally reports all 260 dimension declarations as contract_only, so rollout work remains visible instead of being overstated. ### Changed Files - `docs/INFORMATION_GOVERNANCE_ADOPTION.md` - `tools/inventory/platform-interface-inventory.py` ### Verification - `tools/checks/check-manifest-shapes.py --strict: 65/65 manifests valid` - `tools/inventory/platform-interface-inventory.py --strict: 260 contract_only, 0 partial/enforced` - `tools/checks/check-focused.sh: passed, including 50 WebUI module permutations` ### Next / Blocked - Adopt the contract object type by object type, beginning with the three reference journeys; record concrete tests/evidence before promoting a dimension. Suggested status label: `status/in-progress`

zemion commented

2026-08-24 19:29:05 +02:00

Records governance progress: govoplan-records v0.1.23 (a2dd280) now enforces purpose-bound restricted access end to end. Revisioned, effective-dated grants cover account, membership, group, role, function assignment, and delegation subjects; read/write/manage actions are checked against an exact declared purpose; current authorization governs historical reads and idempotent replays; list/search/detail/write/lifecycle operations fail closed; and the last active manager cannot be revoked while a record remains restricted. Search uses the fixed records.search purpose, DSAR output minimizes grant data, and the shared WebUI now supports restricted creation plus grant/revoke administration with bilingual help and documentation.

Evidence: 27 Records tests, migration-head validation, Python lint, TypeScript and i18n checks, strict endpoint/help inventory, all 72 manifest checks, all cross-module backend/migration suites, 63 WebUI module permutations, and 13 Playwright conformance scenarios passed. Governance inventory is now contract_only=284 and enforced=4, with no remaining partial dimension. Root composition commit: 29d03aa.

This epic remains open for the 284 contract-only adoption items.

Records governance progress: govoplan-records v0.1.23 (a2dd280) now enforces purpose-bound restricted access end to end. Revisioned, effective-dated grants cover account, membership, group, role, function assignment, and delegation subjects; read/write/manage actions are checked against an exact declared purpose; current authorization governs historical reads and idempotent replays; list/search/detail/write/lifecycle operations fail closed; and the last active manager cannot be revoked while a record remains restricted. Search uses the fixed records.search purpose, DSAR output minimizes grant data, and the shared WebUI now supports restricted creation plus grant/revoke administration with bilingual help and documentation. Evidence: 27 Records tests, migration-head validation, Python lint, TypeScript and i18n checks, strict endpoint/help inventory, all 72 manifest checks, all cross-module backend/migration suites, 63 WebUI module permutations, and 13 Playwright conformance scenarios passed. Governance inventory is now contract_only=284 and enforced=4, with no remaining partial dimension. Root composition commit: 29d03aa. This epic remains open for the 284 contract-only adoption items.

zemion commented

2026-08-24 20:28:51 +02:00

Cases governance adoption is complete and published: GovOPlaN/govoplan-cases@v0.1.23 (17415d8), composed by root commit 1cec4ee; implementation evidence is tracked in Cases #6.

Cases now enforces temporal browsing, exact-purpose restricted access, current authorization for historical reads, and institutional context. Retention remains explicitly contract-only until schedules, legal holds, appraisal, and disposition gates exist. Workspace governance totals after this slice: enforced=7, contract_only=281. The full focused gate passed, including all module suites, 63 WebUI permutations, and 13 browser conformance tests.

Cases governance adoption is complete and published: `GovOPlaN/govoplan-cases@v0.1.23` (`17415d8`), composed by root commit `1cec4ee`; implementation evidence is tracked in Cases #6. Cases now enforces temporal browsing, exact-purpose restricted access, current authorization for historical reads, and institutional context. Retention remains explicitly contract-only until schedules, legal holds, appraisal, and disposition gates exist. Workspace governance totals after this slice: `enforced=7`, `contract_only=281`. The full focused gate passed, including all module suites, 63 WebUI permutations, and 13 browser conformance tests.

zemion commented

2026-08-24 20:30:05 +02:00

Cases governance adoption is complete and published: GovOPlaN/govoplan-cases@v0.1.23 (17415d8), composed by root commit 1cec4ee; implementation evidence is tracked in Cases #6.

Cases now enforces temporal browsing, exact-purpose restricted access, current authorization for historical reads, and institutional context. Retention remains explicitly contract-only until schedules, legal holds, appraisal, and disposition gates exist. Workspace governance totals after this slice: enforced=7, contract_only=281. The full focused gate passed, including all module suites, 63 WebUI permutations, and 13 browser conformance tests.

Cases governance adoption is complete and published: `GovOPlaN/govoplan-cases@v0.1.23` (`17415d8`), composed by root commit `1cec4ee`; implementation evidence is tracked in Cases #6. Cases now enforces temporal browsing, exact-purpose restricted access, current authorization for historical reads, and institutional context. Retention remains explicitly contract-only until schedules, legal holds, appraisal, and disposition gates exist. Workspace governance totals after this slice: `enforced=7`, `contract_only=281`. The full focused gate passed, including all module suites, 63 WebUI permutations, and 13 browser conformance tests.

zemion referenced this issue

2026-09-08 05:27:54 +02:00

[Feature] Complete temporal read-context adoption across effective-dated modules #39

zemion referenced this issue

2026-09-08 05:27:54 +02:00

[Feature] Complete temporal read-context adoption across effective-dated modules #39

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#40