GovOPlaN/govoplan
1
0
Fork 0
Code Issues 10 Pull Requests Actions 3 Packages Projects Releases Wiki Activity

[User Story] Task-focused Views reduce GovOPlaN to the interface needed for the current job #17

New Issue
Open
opened 2026-07-28 18:59:03 +02:00 by zemion · 2 comments
zemion commented 2026-07-28 18:59:03 +02:00
Owner
Copy Link

User story

As a user performing a defined task, I want GovOPlaN to show the modules, navigation entries, sections, and actions relevant to that task so that I can work with much less interface clutter while remaining able to understand, leave, and return to the focused context.

As an administrator, I want to publish, assign, default, and limit Views so that task-specific interfaces remain governed and consistent. As a workflow designer, I want workflow steps to activate an appropriate View without turning presentation choices into authorization.

Product rules

  • A View is a reversible filter over authorized interface surfaces, not a permission boundary.
  • Modules announce stable, filterable surfaces through versioned Core contracts and use shared Core hooks to respect the effective View.
  • Administrators can impose a View or limit the selectable set; users can personalize only inside the effective ceiling.
  • Workflows can activate and further narrow a View for an instance or step, and provide a clear way to leave and resume focused mode.
  • Hiding a parent surface hides dependent children. The first release does not support arbitrary CSS/component selectors.
  • Direct links distinguish “outside the current View” from “not authorized”.
  • When Views is not installed, the current interface behaves exactly as it does today.

Work packages

Acceptance criteria

  • An administrator can publish and assign a View that narrows at least two installed modules down to selected navigation, sections, and actions.
  • A user can select an allowed View, see why an item is constrained, temporarily leave it, and return.
  • A workflow step can activate a pinned View revision and restore it after navigation/reload.
  • No View configuration can expose a route, action, tenant, or resource denied by normal authorization.
## User story As a user performing a defined task, I want GovOPlaN to show the modules, navigation entries, sections, and actions relevant to that task so that I can work with much less interface clutter while remaining able to understand, leave, and return to the focused context. As an administrator, I want to publish, assign, default, and limit Views so that task-specific interfaces remain governed and consistent. As a workflow designer, I want workflow steps to activate an appropriate View without turning presentation choices into authorization. ## Product rules - A View is a reversible filter over authorized interface surfaces, not a permission boundary. - Modules announce stable, filterable surfaces through versioned Core contracts and use shared Core hooks to respect the effective View. - Administrators can impose a View or limit the selectable set; users can personalize only inside the effective ceiling. - Workflows can activate and further narrow a View for an instance or step, and provide a clear way to leave and resume focused mode. - Hiding a parent surface hides dependent children. The first release does not support arbitrary CSS/component selectors. - Direct links distinguish “outside the current View” from “not authorized”. - When Views is not installed, the current interface behaves exactly as it does today. ## Work packages - [`govoplan-views` initialization and module implementation](https://git.add-ideas.de/GovOPlaN/govoplan/issues/16) - [Core versioned surface/runtime contract](https://git.add-ideas.de/GovOPlaN/govoplan-core/issues/271) - [Policy inheritance, limits, and provenance](https://git.add-ideas.de/GovOPlaN/govoplan-policy/issues/9) - [Workflow step activation and restoration](https://git.add-ideas.de/GovOPlaN/govoplan-workflow/issues/7) - [Existing focused workflow user story](https://git.add-ideas.de/GovOPlaN/govoplan-workflow/issues/3) ## Acceptance criteria - An administrator can publish and assign a View that narrows at least two installed modules down to selected navigation, sections, and actions. - A user can select an allowed View, see why an item is constrained, temporarily leave it, and return. - A workflow step can activate a pinned View revision and restore it after navigation/reload. - No View configuration can expose a route, action, tenant, or resource denied by normal authorization.
zemion commented 2026-07-28 21:09:15 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • The first usable product slice is now live on main: modules announce stable surfaces, administrators can publish and assign governed Views, users can select available Views, and the shell/module UI respects the projection.
  • The user story remains open because workflow step activation/restoration and Policy-owned narrowing ceilings are still outstanding work packages.

Verification

  • 26 manifests, 20 WebUI modules, and 103 surfaces validated

Next / Blocked

  • Implement Policy ceilings and explainable per-surface limitation provenance in govoplan-policy#9.
  • Implement workflow instance/step activation and restoration in govoplan-workflow#7.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - The first usable product slice is now live on main: modules announce stable surfaces, administrators can publish and assign governed Views, users can select available Views, and the shell/module UI respects the projection. - The user story remains open because workflow step activation/restoration and Policy-owned narrowing ceilings are still outstanding work packages. ### Verification - `26 manifests, 20 WebUI modules, and 103 surfaces validated` ### Next / Blocked - Implement Policy ceilings and explainable per-surface limitation provenance in govoplan-policy#9. - Implement workflow instance/step activation and restoration in govoplan-workflow#7. Suggested status label: `status/in-progress`
zemion added
status
in-progress
 and removed
status
ready
 labels 2026-07-28 21:10:19 +02:00
zemion commented 2026-07-28 22:14:01 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Refined the Views editor with shared SelectionList and ExplorerTree components, explicit module expansion controls, and a full-width assignment section independent of the selected definition.
  • Added personal and group-owned View definitions in Settings with scope-aware authorization; publishing automatically makes an owned View available to its owner.
  • Kept tenant administrators able to inspect and manage tenant, group, and user definitions while preventing personal/group editors from crossing account or membership boundaries.

Changed Files

  • govoplan-views@3de8d4a
  • govoplan-core@324c26d
  • govoplan-dashboard@2250d69

Verification

  • govoplan-views: 15 tests passed
  • tools/checks/check-focused.sh: passed, including 114 core tests and all WebUI module permutations
  • full-product WebUI build: passed

Next / Blocked

  • Policy ceilings/provenance and workflow activation/restoration remain tracked by govoplan-policy#9 and govoplan-workflow#7.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Refined the Views editor with shared SelectionList and ExplorerTree components, explicit module expansion controls, and a full-width assignment section independent of the selected definition. - Added personal and group-owned View definitions in Settings with scope-aware authorization; publishing automatically makes an owned View available to its owner. - Kept tenant administrators able to inspect and manage tenant, group, and user definitions while preventing personal/group editors from crossing account or membership boundaries. ### Changed Files - `govoplan-views@3de8d4a` - `govoplan-core@324c26d` - `govoplan-dashboard@2250d69` ### Verification - `govoplan-views: 15 tests passed` - `tools/checks/check-focused.sh: passed, including 114 core tests and all WebUI module permutations` - `full-product WebUI build: passed` ### Next / Blocked - Policy ceilings/provenance and workflow activation/restoration remain tracked by govoplan-policy#9 and govoplan-workflow#7. 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
area/governance
area/security
area/webui
codex/ready
module/core
module/policy
module/views
module/workflow
priority
p1
status
in-progress
type
user-story
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#17
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?