[Feature] Add approval-template administration UI #2

New Issue

2026-08-02T04:10:32+02:00

zemion commented

2026-08-02 04:10:32 +02:00

Context

Approval instances have a user-facing queue, while template creation, revision, publication, and escalation remain API-only. The endpoint-surface inventory in GovOPlaN #26 classifies this as a missing administration surface.

Acceptance criteria

Add permission-aware template list, create, revise, compare, and publish views.
Explain immutable published revisions and effective policy/provenance.
Surface escalation only for transitions allowed by the active template and policy.
Preserve the headless API for module-defined approval flows.
Cover malformed templates, concurrent revisions, forbidden actions, and optional-module permutations.
Update administrator/user documentation and endpoint-surface declarations.

## Context Approval instances have a user-facing queue, while template creation, revision, publication, and escalation remain API-only. The endpoint-surface inventory in GovOPlaN #26 classifies this as a missing administration surface. ## Acceptance criteria - Add permission-aware template list, create, revise, compare, and publish views. - Explain immutable published revisions and effective policy/provenance. - Surface escalation only for transitions allowed by the active template and policy. - Preserve the headless API for module-defined approval flows. - Cover malformed templates, concurrent revisions, forbidden actions, and optional-module permutations. - Update administrator/user documentation and endpoint-surface declarations.

zemion added the module/approvals area/governance

labels 2026-08-02 04:10:32 +02:00

zemion commented

2026-08-03 20:41:07 +02:00

Closure audit (2026-08-03)

The immutable template create/revise/publish runtime and request escalation backend are implemented, while the existing WebUI only covers approval requests and decisions. This issue is not yet closable: the API lists only current template revisions, has no bounded history/compare response, and no template or escalation administration surface exists.

Shortest closure path:

Add bounded template history and compare APIs over the existing immutable revisions.
Add a permission-aware template list/editor/revision comparison/publication panel.
Surface escalation only when current request/template state permits it, then add malformed, stale, forbidden, and module-permutation tests and update docs/declarations.

## Closure audit (2026-08-03) The immutable template create/revise/publish runtime and request escalation backend are implemented, while the existing WebUI only covers approval requests and decisions. This issue is **not yet closable**: the API lists only current template revisions, has no bounded history/compare response, and no template or escalation administration surface exists. Shortest closure path: 1. Add bounded template history and compare APIs over the existing immutable revisions. 2. Add a permission-aware template list/editor/revision comparison/publication panel. 3. Surface escalation only when current request/template state permits it, then add malformed, stale, forbidden, and module-permutation tests and update docs/declarations.

zemion commented

2026-08-04 01:13:47 +02:00

Codex State: done

Summary

Added approval-template revision history, comparison, and template administration surfaces.

Changed Files

commit 7f64247

Verification

7 focused Python tests and Approval Templates WebUI test passed; all-module startup smoke passed.

## Codex State: done ### Summary - Added approval-template revision history, comparison, and template administration surfaces. ### Changed Files - `commit 7f64247` ### Verification - `7 focused Python tests and Approval Templates WebUI test passed; all-module startup smoke passed.`

zemion closed this issue

2026-08-04 01:13:48 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-approvals#2