[Feature] Add evidence-backed product and sector package classes #34

New Issue

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

zemion commented

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

Outcome

Turn successful compositions into portable, explainable products and sector specializations without code forks or cross-module ownership.

Parent: #29

Package classes

reference package: bounded journey plus degraded/recovery and target evidence;
product package: reusable operating capability;
sector package: terminology, forms, rules, process baselines, controls, reports, and integrations for an institutional sector;
deployment profile: supported topology, operations, and recovery assumptions;
integration profile: external providers, source-authority modes, bindings, health, and reconciliation expectations.

Scope

Extend the signed configuration-package schema, preflight, admin wizard, export/import, Docs projection, and release evidence. Define inheritance/derivation rules that preserve parent constraints and provenance.

Acceptance criteria

Package class and parent/version provenance are signed and validated.
Only owning modules apply configuration fragments.
External bindings declare authority/maturity/health/recovery expectations.
A package claim links to module versions, target tests, migrations, security, operations, accessibility, and recovery evidence.
First proof packages one existing Campaign composition and one governed-data composition.

## Outcome Turn successful compositions into portable, explainable products and sector specializations without code forks or cross-module ownership. Parent: https://git.add-ideas.de/GovOPlaN/govoplan/issues/29 ## Package classes - reference package: bounded journey plus degraded/recovery and target evidence; - product package: reusable operating capability; - sector package: terminology, forms, rules, process baselines, controls, reports, and integrations for an institutional sector; - deployment profile: supported topology, operations, and recovery assumptions; - integration profile: external providers, source-authority modes, bindings, health, and reconciliation expectations. ## Scope Extend the signed configuration-package schema, preflight, admin wizard, export/import, Docs projection, and release evidence. Define inheritance/derivation rules that preserve parent constraints and provenance. ## Acceptance criteria - Package class and parent/version provenance are signed and validated. - Only owning modules apply configuration fragments. - External bindings declare authority/maturity/health/recovery expectations. - A package claim links to module versions, target tests, migrations, security, operations, accessibility, and recovery evidence. - First proof packages one existing Campaign composition and one governed-data composition.

zemion added the module/docs module/ops module/admin area/governance area/release area/docs

module/core labels 2026-08-01 00:00:54 +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:45 +02:00

Codex State: progress

Summary

Signed configuration packages now distinguish reference, product, sector, deployment, and integration classes and preserve parent/version/evidence provenance.
Derivation cannot silently loosen parent constraints; preflight evaluates provider authority, maturity, binding, health, freshness, and recovery expectations using active registry declarations.

Verification

Core configuration-package tests, Access preflight-context test, and release-catalog synthesis tests pass.

Next / Blocked

Complete the Admin wizard/export-import presentation and add evidence-backed Campaign and governed-data proof package artifacts before closing.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Signed configuration packages now distinguish reference, product, sector, deployment, and integration classes and preserve parent/version/evidence provenance. - Derivation cannot silently loosen parent constraints; preflight evaluates provider authority, maturity, binding, health, freshness, and recovery expectations using active registry declarations. ### Verification - `Core configuration-package tests, Access preflight-context test, and release-catalog synthesis tests pass.` ### Next / Blocked - Complete the Admin wizard/export-import presentation and add evidence-backed Campaign and governed-data proof package artifacts before closing. Suggested status label: `status/in-progress`

zemion added

and removed

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

zemion commented

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

Codex State: done

Summary

Configuration packages now distinguish and validate reference, product, sector, deployment, and integration classes with parent/evidence provenance and provider expectations.
Added CI-validated governed-communication and governed-data-assurance product manifests; each records the evidence gates required before reference promotion.

Changed Files

packages/product/governed-communication/package.json
packages/product/governed-data-assurance/package.json
tests/test_configuration_package_artifacts.py
tools/checks/check-module-matrix.sh

Verification

Configuration package artifact test and 120 Core module-system tests passed.

## Codex State: done ### Summary - Configuration packages now distinguish and validate reference, product, sector, deployment, and integration classes with parent/evidence provenance and provider expectations. - Added CI-validated governed-communication and governed-data-assurance product manifests; each records the evidence gates required before reference promotion. ### Changed Files - `packages/product/governed-communication/package.json` - `packages/product/governed-data-assurance/package.json` - `tests/test_configuration_package_artifacts.py` - `tools/checks/check-module-matrix.sh` ### Verification - `Configuration package artifact test and 120 Core module-system tests passed.`

zemion closed this issue

2026-08-01 08:20:54 +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 10:34:52 +02:00

Codex State: done

The signed package model now distinguishes reference, product, sector, deployment, and integration classes. product.service-to-decision is executable composition evidence with module/capability/provider preflight and an SQL-backed golden fixture; it deliberately remains product-maturity until target and operational evidence support a stronger claim.

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 The signed package model now distinguishes reference, product, sector, deployment, and integration classes. `product.service-to-decision` is executable composition evidence with module/capability/provider preflight and an SQL-backed golden fixture; it deliberately remains product-maturity until target and operational evidence support a stronger claim. - `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#34