[User Story] Work through configurable product areas and task-local Quick Access #46

Closed
opened 2026-08-06 17:26:04 +02:00 by zemion · 3 comments
Owner

User story

As a person doing institutional work, I want GovOPlaN to organize authorized tools around recognizable work, services, records, communication and outcomes, and keep a small configurable set of task-local tools available, so that I can complete and resume work without understanding package topology or losing access to less frequent functions.

As a system or tenant administrator, I want sensible product-area and Quick Access defaults, availability ceilings, forced entries and ordering. As a user, I want to choose and order permitted Quick Access categories and product destinations.

Accepted product rules

  • The complete permission-derived catalogue remains available as All available tools; scrolling is not itself a defect.
  • Quick Access is the optional govoplan-quick-access module. Core owns contribution contracts; contributors do not import it.
  • Initial categories are Work, Calendar, Messages and Files.
  • Messages composes Mail, Postbox and future chat presentation without merging channel state or semantics.
  • System, tenant and user configuration resolves availability and ordering inside Policy/View ceilings. Presentation never grants authority.
  • Product areas are configurable with sensible baseline defaults and may retain familiar direct pins such as Calendar or Files.
  • A workflow may focus a View and Quick Access set while preserving explicit escape and return.

Work packages

  • Core #283: product-surface/product-area contract and migration.
  • Core #285: task-local contribution and return-context contract.
  • Quick Access #1: configuration, effective resolution, rail and drawer.
  • Views: configurable product-area and Quick Access projection.
  • Contributor slices in Tasks, Calendar, Mail, Postbox and Files.

Architecture: govoplan/docs/QUICK_ACCESS_AND_PRODUCT_AREAS.md.

## User story As a person doing institutional work, I want GovOPlaN to organize authorized tools around recognizable work, services, records, communication and outcomes, and keep a small configurable set of task-local tools available, so that I can complete and resume work without understanding package topology or losing access to less frequent functions. As a system or tenant administrator, I want sensible product-area and Quick Access defaults, availability ceilings, forced entries and ordering. As a user, I want to choose and order permitted Quick Access categories and product destinations. ## Accepted product rules - The complete permission-derived catalogue remains available as **All available tools**; scrolling is not itself a defect. - Quick Access is the optional `govoplan-quick-access` module. Core owns contribution contracts; contributors do not import it. - Initial categories are Work, Calendar, Messages and Files. - Messages composes Mail, Postbox and future chat presentation without merging channel state or semantics. - System, tenant and user configuration resolves availability and ordering inside Policy/View ceilings. Presentation never grants authority. - Product areas are configurable with sensible baseline defaults and may retain familiar direct pins such as Calendar or Files. - A workflow may focus a View and Quick Access set while preserving explicit escape and return. ## Work packages - Core #283: product-surface/product-area contract and migration. - Core #285: task-local contribution and return-context contract. - Quick Access #1: configuration, effective resolution, rail and drawer. - Views: configurable product-area and Quick Access projection. - Contributor slices in Tasks, Calendar, Mail, Postbox and Files. Architecture: `govoplan/docs/QUICK_ACCESS_AND_PRODUCT_AREAS.md`.
Author
Owner

Implemented the first production-shaped product-presentation slice.

  • Added the canonical architecture and updated the strategy, product input, Views, core-ideas, and reference-journey documents.
  • Added Core product-area and Quick Access contribution contracts.
  • Initialized govoplan-quick-access and integrated it into local/deployment/release tooling.
  • Added configurable immutable View presentation and first Tasks, Calendar, Mail, Postbox, and Files contributions.

Commits: govoplan@f3cfd1b, govoplan-core@32c234f, govoplan-quick-access@3fbbb84, govoplan-views@b9a92c7.

Verified by the consolidated focused suite, 54 existing optional-module permutations, explicit Quick Access isolated/provider builds, the full-product build, all 67 manifest contracts, isolated migrations, and a fresh composed startup.

This umbrella remains open for broader product-language/classification migration and the governed active-object/return-context slice tracked by Core #283/#285.

Implemented the first production-shaped product-presentation slice. - Added the canonical architecture and updated the strategy, product input, Views, core-ideas, and reference-journey documents. - Added Core product-area and Quick Access contribution contracts. - Initialized `govoplan-quick-access` and integrated it into local/deployment/release tooling. - Added configurable immutable View presentation and first Tasks, Calendar, Mail, Postbox, and Files contributions. Commits: `govoplan@f3cfd1b`, `govoplan-core@32c234f`, `govoplan-quick-access@3fbbb84`, `govoplan-views@b9a92c7`. Verified by the consolidated focused suite, 54 existing optional-module permutations, explicit Quick Access isolated/provider builds, the full-product build, all 67 manifest contracts, isolated migrations, and a fresh composed startup. This umbrella remains open for broader product-language/classification migration and the governed active-object/return-context slice tracked by Core #283/#285.
Author
Owner

Codex State: progress

Published the first versioned product-surface slice.

  • Core v0.1.40 (6e518fa) defines and validates product_surfaces, composes shared identities, resolves authorization and View visibility, preserves stable aliases, emits bounded route telemetry, and provides the central unavailable/degraded presentation.
  • Mail v0.1.25 (ecc1283) and Postbox v0.1.22 (aff2623) now contribute the shared communication.messages surface: stable /messages, migration alias /inbox, owner routes /mail and /postbox, and shared German/English product language.
  • Workspace v0.1.40 (3766e26) publishes the aligned release and architecture state.
  • The complete focused gate passes: 72 manifest contracts, backend suites, 63 WebUI module permutations, full-product bundle (159.1/160 KiB gzip), and 8 Playwright conformance tests.

This issue remains open for additional product-surface promotions, product-area navigation migration, and the reference journey acceptance criterion.

## Codex State: progress Published the first versioned product-surface slice. - Core v0.1.40 (`6e518fa`) defines and validates `product_surfaces`, composes shared identities, resolves authorization and View visibility, preserves stable aliases, emits bounded route telemetry, and provides the central unavailable/degraded presentation. - Mail v0.1.25 (`ecc1283`) and Postbox v0.1.22 (`aff2623`) now contribute the shared `communication.messages` surface: stable `/messages`, migration alias `/inbox`, owner routes `/mail` and `/postbox`, and shared German/English product language. - Workspace v0.1.40 (`3766e26`) publishes the aligned release and architecture state. - The complete focused gate passes: 72 manifest contracts, backend suites, 63 WebUI module permutations, full-product bundle (159.1/160 KiB gzip), and 8 Playwright conformance tests. This issue remains open for additional product-surface promotions, product-area navigation migration, and the reference journey acceptance criterion.
Author
Owner

Implemented and published in the coordinated product-surface release:

  • Core ac40774 / v0.1.44: stable primary product navigation, permission-derived All available tools, View-independent escape, owner-route active state, configured ordering, deferred catalogue UI, centralized EN/DE product labels and unavailable explanations.
  • Tasks 5c186b5 / v0.1.22: Work at /work backed by /tasks.
  • Calendar 3e5fc05 / v0.1.23: Calendar at /agenda backed by /calendar.
  • Files 2baa8f2 / v0.1.25: Files at /documents backed by /files.
  • Root 6fb928d / v0.1.44: architecture, release pins and immutable package metadata.

The existing Messages composition remains the fourth initial category. Owner routes stay usable as deep links and in All available tools; ordinary primary navigation no longer requires package-topology knowledge. Documentation contributions cover the English and German user/admin behavior.

Verification: 72/72 manifest shapes; Tasks 16, Calendar 152, Files 169 and Core 681 backend tests; 63 WebUI module permutations; 13 Playwright conformance journeys including bilingual product navigation, View escape, keyboard/accessibility and resident-permit scenarios; full tools/checks/check-focused.sh; release lock resolves contributor tags to exact commits; remote branches and tags verified.

Implemented and published in the coordinated product-surface release: - Core `ac40774` / `v0.1.44`: stable primary product navigation, permission-derived **All available tools**, View-independent escape, owner-route active state, configured ordering, deferred catalogue UI, centralized EN/DE product labels and unavailable explanations. - Tasks `5c186b5` / `v0.1.22`: **Work** at `/work` backed by `/tasks`. - Calendar `3e5fc05` / `v0.1.23`: **Calendar** at `/agenda` backed by `/calendar`. - Files `2baa8f2` / `v0.1.25`: **Files** at `/documents` backed by `/files`. - Root `6fb928d` / `v0.1.44`: architecture, release pins and immutable package metadata. The existing Messages composition remains the fourth initial category. Owner routes stay usable as deep links and in All available tools; ordinary primary navigation no longer requires package-topology knowledge. Documentation contributions cover the English and German user/admin behavior. Verification: 72/72 manifest shapes; Tasks 16, Calendar 152, Files 169 and Core 681 backend tests; 63 WebUI module permutations; 13 Playwright conformance journeys including bilingual product navigation, View escape, keyboard/accessibility and resident-permit scenarios; full `tools/checks/check-focused.sh`; release lock resolves contributor tags to exact commits; remote branches and tags verified.
zemion removed the
status
in-progress
label 2026-08-24 18:32:08 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#46