[Feature] Configuration package for permit-to-payment workflows #214

Closed
opened 2026-07-07 21:15:47 +02:00 by zemion · 2 comments
Owner

Turn the reference permit journey into an importable/exportable configuration package once the participating modules exist.

Sources:

  • docs/GOVERNMENT_OPERATIONS_VISION.md
  • docs/CONFIGURATION_PACKAGES.md

Acceptance criteria:

  • package manifest can declare required/optional modules and capabilities
  • participating modules expose provider contracts for owned fragments
  • preflight reports missing modules, missing data, conflicts, and policy problems
  • import asks only for deployment-specific data
  • export redacts secrets and records provenance
  • admin UI can guide an operator through dry-run, apply, result, and rollback state
Turn the reference permit journey into an importable/exportable configuration package once the participating modules exist. Sources: - `docs/GOVERNMENT_OPERATIONS_VISION.md` - `docs/CONFIGURATION_PACKAGES.md` Acceptance criteria: - package manifest can declare required/optional modules and capabilities - participating modules expose provider contracts for owned fragments - preflight reports missing modules, missing data, conflicts, and policy problems - import asks only for deployment-specific data - export redacts secrets and records provenance - admin UI can guide an operator through dry-run, apply, result, and rollback state
Author
Owner

Starting an autonomous implementation slice. The generic configuration-package engine and the permit-to-payment participant modules now exist, so I will add the canonical package manifest/fragments, deployment-data preflight, secret-redacted provenance export, guided dry-run/apply/result/rollback behavior, owner documentation, and regression coverage. No external provider or product-policy decision is required for this bounded reference package.

Starting an autonomous implementation slice. The generic configuration-package engine and the permit-to-payment participant modules now exist, so I will add the canonical package manifest/fragments, deployment-data preflight, secret-redacted provenance export, guided dry-run/apply/result/rollback behavior, owner documentation, and regression coverage. No external provider or product-policy decision is required for this bounded reference package.
Author
Owner

Implemented and released across the coordinated v0.1.35 slice.

Delivered:

  • Core v0.1.35: declared $data deployment bindings, fail-closed resolution before provider preflight, stop-on-blocker apply behavior, explicit rollback/recovery state, and export provenance with secret-key redaction.
  • Access v0.1.20: API serialization for rollback/provenance plus complete EN/DE operator documentation.
  • Admin v0.1.19: generated requirement inputs (including password/number/boolean controls), package+data+tenant review fingerprinting, stale-preflight protection, fragment-derived export scope, provenance export, and localized recovery outcomes.
  • Forms v0.1.20: module-owned forms.configuration provider with tenant/authority/conflict checks, digest-idempotent import, tenant-local draft creation, source provenance, and portable export.
  • Workspace v0.1.35: executable Anwohnerparkausweis product package with required/optional modules and capabilities, deployment-only responsibility-group inputs, Access role/group/binding fragments, a digest-bound German Form definition, and an activated resident-permit review workflow including decision and EUR 30 payment-verification steps.

Verification:

  • complete focused gate passed
  • 68/68 manifest architecture declarations
  • 128 Core module-system tests and all focused backend module suites
  • Access 77, Forms 19, Admin 15 plus structural UI tests
  • 63 WebUI module permutations; full product 505.8 KiB raw / 159.7 KiB gzip within budget
  • 8/8 Playwright accessibility/interaction conformance tests

Published commits/tags:

  • Core 1c3ee9e / v0.1.35
  • Access 206873b / v0.1.20
  • Admin ed424c7 / v0.1.19
  • Forms 727c70f / v0.1.20
  • Workspace 7c92565 / v0.1.35

All acceptance criteria are covered. Additional Services/Cases/Payments/Tasks configuration fragments remain optional follow-on expansion; their runtime capabilities already participate in the pinned product journey and are not hidden prerequisites for this bounded package.

Implemented and released across the coordinated v0.1.35 slice. Delivered: - Core v0.1.35: declared `$data` deployment bindings, fail-closed resolution before provider preflight, stop-on-blocker apply behavior, explicit rollback/recovery state, and export provenance with secret-key redaction. - Access v0.1.20: API serialization for rollback/provenance plus complete EN/DE operator documentation. - Admin v0.1.19: generated requirement inputs (including password/number/boolean controls), package+data+tenant review fingerprinting, stale-preflight protection, fragment-derived export scope, provenance export, and localized recovery outcomes. - Forms v0.1.20: module-owned `forms.configuration` provider with tenant/authority/conflict checks, digest-idempotent import, tenant-local draft creation, source provenance, and portable export. - Workspace v0.1.35: executable Anwohnerparkausweis product package with required/optional modules and capabilities, deployment-only responsibility-group inputs, Access role/group/binding fragments, a digest-bound German Form definition, and an activated resident-permit review workflow including decision and EUR 30 payment-verification steps. Verification: - complete focused gate passed - 68/68 manifest architecture declarations - 128 Core module-system tests and all focused backend module suites - Access 77, Forms 19, Admin 15 plus structural UI tests - 63 WebUI module permutations; full product 505.8 KiB raw / 159.7 KiB gzip within budget - 8/8 Playwright accessibility/interaction conformance tests Published commits/tags: - Core 1c3ee9e / v0.1.35 - Access 206873b / v0.1.20 - Admin ed424c7 / v0.1.19 - Forms 727c70f / v0.1.20 - Workspace 7c92565 / v0.1.35 All acceptance criteria are covered. Additional Services/Cases/Payments/Tasks configuration fragments remain optional follow-on expansion; their runtime capabilities already participate in the pinned product journey and are not hidden prerequisites for this bounded package.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-core#214