GovOPlaN/govoplan-campaign
1
0
Fork 0
Code Issues 46 Pull Requests Actions Packages Projects Releases Wiki Activity

[Task] Audit and migrate Campaign interfaces to the product-wide pattern language #74

New Issue
Open
opened 2026-07-20 14:41:31 +02:00 by zemion · 3 comments
zemion commented 2026-07-20 14:41:31 +02:00
Owner
Copy Link

Parent Program

GovOPlaN meta #11 establishes the whole-system interface pattern language. Campaign is the first full-domain pilot.

Goal

Turn the Campaign workspace into a coherent reference implementation for placement, hierarchy, visuals, wording, progressive disclosure, validation, review, asynchronous progress, and evidence without coupling it to the postponed Workflow runtime.

Acceptance Criteria

  • Inventory every Campaign route, page, panel, overlay, dialog, and important state with its user task, archetype, sensitivity/consequence, current shared components, and known deviations.
  • Map each deviation to a canonical pattern and an existing or new bounded issue.
  • Define one stable Campaign information architecture and placement vocabulary for primary/secondary/destructive actions, context, status, problems, help, and provenance.
  • Audit wording for task orientation, consistent nouns/verbs, clear consequences, blocked-action explanations, and translation-key ownership.
  • Treat #59/#73 as the preview/detail-overlay pattern, #63 as review-stage/intervention, #62 as asynchronous delivery progress, #65/Core #263 as filtering, and #35 as guided entry.
  • Cover loading, empty, error, partial, stale, offline/retry, permission-denied, and destructive-confirmation states.
  • Cover keyboard order, focus restoration, accessible names/status announcements, responsive layout, and zoom.
  • Produce a rollout matrix with current/target pattern, owner, dependency, issue, priority, and verification evidence.
  • Extract a generic Core primitive only when the contract is proven and has a second consumer or clear platform ownership.
  • Add focused behavior/accessibility tests for migrated critical surfaces; visual checks supplement rather than replace them.

Initial Implementation Order

  1. Isolate/integrate #67.
  2. Implement/verify #59 and #73 together.
  3. Resolve #63 vocabulary and intervention matrix.
  4. Implement #62 send mode/progress.
  5. Fix #66 skipped-delivery semantics.
  6. Implement #68/#70 recipient bulk/search UX.
  7. Resolve #65 after Core #263.
  8. Return to #60/#61 after attachment-policy decisions.
## Parent Program GovOPlaN meta #11 establishes the whole-system interface pattern language. Campaign is the first full-domain pilot. ## Goal Turn the Campaign workspace into a coherent reference implementation for placement, hierarchy, visuals, wording, progressive disclosure, validation, review, asynchronous progress, and evidence without coupling it to the postponed Workflow runtime. ## Acceptance Criteria - [ ] Inventory every Campaign route, page, panel, overlay, dialog, and important state with its user task, archetype, sensitivity/consequence, current shared components, and known deviations. - [ ] Map each deviation to a canonical pattern and an existing or new bounded issue. - [ ] Define one stable Campaign information architecture and placement vocabulary for primary/secondary/destructive actions, context, status, problems, help, and provenance. - [ ] Audit wording for task orientation, consistent nouns/verbs, clear consequences, blocked-action explanations, and translation-key ownership. - [ ] Treat #59/#73 as the preview/detail-overlay pattern, #63 as review-stage/intervention, #62 as asynchronous delivery progress, #65/Core #263 as filtering, and #35 as guided entry. - [ ] Cover loading, empty, error, partial, stale, offline/retry, permission-denied, and destructive-confirmation states. - [ ] Cover keyboard order, focus restoration, accessible names/status announcements, responsive layout, and zoom. - [ ] Produce a rollout matrix with current/target pattern, owner, dependency, issue, priority, and verification evidence. - [ ] Extract a generic Core primitive only when the contract is proven and has a second consumer or clear platform ownership. - [ ] Add focused behavior/accessibility tests for migrated critical surfaces; visual checks supplement rather than replace them. ## Initial Implementation Order 1. Isolate/integrate #67. 2. Implement/verify #59 and #73 together. 3. Resolve #63 vocabulary and intervention matrix. 4. Implement #62 send mode/progress. 5. Fix #66 skipped-delivery semantics. 6. Implement #68/#70 recipient bulk/search UX. 7. Resolve #65 after Core #263. 8. Return to #60/#61 after attachment-policy decisions.
zemion commented 2026-07-20 14:43:32 +02:00
Author
Owner
Copy Link

Parent program: add-ideas/govoplan#11. Docs implementation child: add-ideas/govoplan-docs#15. Existing UI doctrine: add-ideas/govoplan-core#227; admin/configuration child: Core #225.

Parent program: add-ideas/govoplan#11. Docs implementation child: add-ideas/govoplan-docs#15. Existing UI doctrine: add-ideas/govoplan-core#227; admin/configuration child: Core #225.
zemion commented 2026-07-20 15:30:07 +02:00
Author
Owner
Copy Link

The pattern language and whole-system surface inventory are drafted locally, and Campaign #59/#73 are implemented as the first concrete pilot. Focused UI tests, structural i18n audit, the Campaign-only production build, documentation link checks, and diff checks pass. The audit issue remains open for baseline integration, review/intervention wording (#63), send/progress (#62), report filtering (#65), and guided entry (#35).

<!-- codex-progress-interface-pilot-2026-07-20 --> The pattern language and whole-system surface inventory are drafted locally, and Campaign #59/#73 are implemented as the first concrete pilot. Focused UI tests, structural i18n audit, the Campaign-only production build, documentation link checks, and diff checks pass. The audit issue remains open for baseline integration, review/intervention wording (#63), send/progress (#62), report filtering (#65), and guided entry (#35).
zemion commented 2026-07-22 09:48:30 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Completed and closed the bounded send/progress, coherent report filtering, excluded-outcome, durable operator queue, synchronous-send safety, and aggregate-report slices (#62, #65, #66, #78, #79, #80; Core #263).
  • The interface inventory now records the implemented evidence and exact commits.

Verification

  • Campaign backend, focused WebUI suites, Core production build/i18n, version, manifest, dependency, and migration gates all pass.

Next / Blocked

  • Continue the broader Campaign wording/accessibility/consequence audit; #63 still owns intervention vocabulary and #35 the guided first-Campaign journey.
  • Non-blocking technical follow-ups: normalize literal wildcard semantics between report search/header filters and introduce a dedicated paginated operator projection if deployments accumulate many Campaign versions.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Completed and closed the bounded send/progress, coherent report filtering, excluded-outcome, durable operator queue, synchronous-send safety, and aggregate-report slices (#62, #65, #66, #78, #79, #80; Core #263). - The interface inventory now records the implemented evidence and exact commits. ### Verification - `Campaign backend, focused WebUI suites, Core production build/i18n, version, manifest, dependency, and migration gates all pass.` ### Next / Blocked - Continue the broader Campaign wording/accessibility/consequence audit; #63 still owns intervention vocabulary and #35 the guided first-Campaign journey. - Non-blocking technical follow-ups: normalize literal wildcard semantics between report search/header filters and introduce a dedicated paginated operator projection if deployments accumulate many Campaign versions. Suggested status label: `status/in-progress`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dataflow
GovOPlaN Dataflow module behavior or integration.
module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-campaign#74
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?