add-ideas/govoplan-docs
1
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

[Feature] Documentation experience: workflows, reference, and patterns #15

New Issue
Open
opened 2026-07-09 13:24:39 +02:00 by zemion · 5 comments
zemion commented 2026-07-09 13:24:39 +02:00
Owner
Copy Link

Problem

The docs module already starts from the configured system, but the presentation still needs a clearer information architecture. Users need task-oriented guidance and short field explanations. Admins need the same workflows plus structure/reference mapping to API fields, permissions, routes, policy sources, and configuration keys. Both audiences need reusable explanations for shared UI patterns such as field help markers, disabled-action blockers, advanced panels, wizards, and policy provenance.

Proposed Capability

Implement the documentation experience described in docs/DOCUMENTATION_EXPERIENCE_CONCEPT.md:

  • Workflows: outcome-oriented "I want to..." topics with audience-aware steps.
  • Reference: screen and field structure topics, with API/configuration/permission mappings in admin view.
  • Patterns: reusable explanations for platform UI behavior.
  • Help Center: a documentation-focused interface served by the same configured-system docs module, with route-aware and field-aware entry points from the application.

Ownership

  • Owning repository: govoplan-docs
  • Related module repositories: govoplan-core, govoplan-access, later each feature module that contributes docs metadata
  • Extension point or integration boundary: module manifests, runtime documentation providers, route metadata, field/reference DTOs, core WebUI help components

Acceptance Criteria

  • Docs topics can be grouped as workflow, reference, pattern, or system documentation without breaking existing configured/available/evidence classification.
  • User and admin views render different detail levels from the same configured-system context.
  • The docs WebUI exposes Workflows, Reference, Patterns, and This system modes.
  • Inline field help, route help, and blocked-action explanations can link to stable docs topics.
  • At least one access-administration workflow, one field/reference mapping, and one design-pattern topic are seeded.
  • Admin reference can show UI label, route/module, API method/path, API field, permission/scope, configuration or policy key, and safety/provenance notes where available.
  • User reference hides API and internal identifiers unless explicitly meaningful to the user.
  • Tests cover topic grouping, audience filtering, link/anchor generation, and configured/available/evidence behavior.

Verification Target

  • cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m unittest tests.test_module_system
  • cd /mnt/DATA/git/govoplan-core && ./scripts/check-focused.sh before closing if core contracts or cross-module WebUI behavior changed.
  • Manual check: open /docs, switch user/admin mode, confirm workflow/reference/pattern navigation and contextual links.

Implementation Notes

Use DocumentationTopic.metadata for the first topic-kind slice. Add typed DTOs only after the first seeded topics prove the shape. Keep feature-module content contributed through manifests/providers/DTOs; the docs module should render and classify it without importing feature-module internals.

<!-- codex-manual-fingerprint:docs-experience-concept-2026-07-09 --> ## Problem The docs module already starts from the configured system, but the presentation still needs a clearer information architecture. Users need task-oriented guidance and short field explanations. Admins need the same workflows plus structure/reference mapping to API fields, permissions, routes, policy sources, and configuration keys. Both audiences need reusable explanations for shared UI patterns such as field help markers, disabled-action blockers, advanced panels, wizards, and policy provenance. ## Proposed Capability Implement the documentation experience described in `docs/DOCUMENTATION_EXPERIENCE_CONCEPT.md`: - Workflows: outcome-oriented "I want to..." topics with audience-aware steps. - Reference: screen and field structure topics, with API/configuration/permission mappings in admin view. - Patterns: reusable explanations for platform UI behavior. - Help Center: a documentation-focused interface served by the same configured-system docs module, with route-aware and field-aware entry points from the application. ## Ownership - Owning repository: `govoplan-docs` - Related module repositories: `govoplan-core`, `govoplan-access`, later each feature module that contributes docs metadata - Extension point or integration boundary: module manifests, runtime documentation providers, route metadata, field/reference DTOs, core WebUI help components ## Acceptance Criteria - [ ] Docs topics can be grouped as workflow, reference, pattern, or system documentation without breaking existing configured/available/evidence classification. - [ ] User and admin views render different detail levels from the same configured-system context. - [ ] The docs WebUI exposes Workflows, Reference, Patterns, and This system modes. - [ ] Inline field help, route help, and blocked-action explanations can link to stable docs topics. - [ ] At least one access-administration workflow, one field/reference mapping, and one design-pattern topic are seeded. - [ ] Admin reference can show UI label, route/module, API method/path, API field, permission/scope, configuration or policy key, and safety/provenance notes where available. - [ ] User reference hides API and internal identifiers unless explicitly meaningful to the user. - [ ] Tests cover topic grouping, audience filtering, link/anchor generation, and configured/available/evidence behavior. ## Verification Target - `cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m unittest tests.test_module_system` - `cd /mnt/DATA/git/govoplan-core && ./scripts/check-focused.sh` before closing if core contracts or cross-module WebUI behavior changed. - Manual check: open `/docs`, switch user/admin mode, confirm workflow/reference/pattern navigation and contextual links. ## Implementation Notes Use `DocumentationTopic.metadata` for the first topic-kind slice. Add typed DTOs only after the first seeded topics prove the shape. Keep feature-module content contributed through manifests/providers/DTOs; the docs module should render and classify it without importing feature-module internals.
zemion added the
type
feature
status
ready
area/api
area/webui
area/docs
codex/ready
 labels 2026-07-09 13:24:39 +02:00
zemion commented 2026-07-09 13:25:41 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Documented the documentation experience concept for workflow, reference, and pattern docs.
  • Created and synced the page-limited wiki entry for Repo-docs-DOCUMENTATION-EXPERIENCE-CONCEPT.

Changed Files

  • docs/DOCUMENTATION_EXPERIENCE_CONCEPT.md
  • README.md
  • docs/DOCUMENTATION_LAYER_CONCEPT.md

Verification

  • git diff --check

Next / Blocked

  • Implement topic-kind grouping and the Help Center navigation modes.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Documented the documentation experience concept for workflow, reference, and pattern docs. - Created and synced the page-limited wiki entry for Repo-docs-DOCUMENTATION-EXPERIENCE-CONCEPT. ### Changed Files - `docs/DOCUMENTATION_EXPERIENCE_CONCEPT.md` - `README.md` - `docs/DOCUMENTATION_LAYER_CONCEPT.md` ### Verification - `git diff --check` ### Next / Blocked - Implement topic-kind grouping and the Help Center navigation modes. Suggested status label: `status/in-progress`
zemion commented 2026-07-09 15:05:07 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Implemented topic-kind grouping in the docs context API while preserving configured/available/evidence layers.
  • Added access-owned workflow and field/reference topics plus a docs-owned field-help design pattern topic.
  • Reworked the docs WebUI into Help Center modes: Workflows, Reference, Patterns, and This system.

Changed Files

  • src/govoplan_docs/backend/api/v1/routes.py
  • src/govoplan_docs/backend/manifest.py
  • webui/src/api/docs.ts
  • webui/src/features/docs/DocsPage.tsx
  • webui/src/i18n/generatedTranslations.ts
  • tests/test_docs_context.py
  • /mnt/DATA/git/govoplan-access/src/govoplan_access/backend/manifest.py
  • /mnt/DATA/git/govoplan-core/tests/test_api_smoke.py

Verification

  • PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context
  • cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available
  • cd /mnt/DATA/git/govoplan-core/webui && npm run build
  • cd /mnt/DATA/git/govoplan-core && ./scripts/check-focused.sh

Next / Blocked

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Implemented topic-kind grouping in the docs context API while preserving configured/available/evidence layers. - Added access-owned workflow and field/reference topics plus a docs-owned field-help design pattern topic. - Reworked the docs WebUI into Help Center modes: Workflows, Reference, Patterns, and This system. ### Changed Files - `src/govoplan_docs/backend/api/v1/routes.py` - `src/govoplan_docs/backend/manifest.py` - `webui/src/api/docs.ts` - `webui/src/features/docs/DocsPage.tsx` - `webui/src/i18n/generatedTranslations.ts` - `tests/test_docs_context.py` - `/mnt/DATA/git/govoplan-access/src/govoplan_access/backend/manifest.py` - `/mnt/DATA/git/govoplan-core/tests/test_api_smoke.py` ### Verification - `PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context` - `cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available` - `cd /mnt/DATA/git/govoplan-core/webui && npm run build` - `cd /mnt/DATA/git/govoplan-core && ./scripts/check-focused.sh` ### Next / Blocked - Try the running dev UI at http://127.0.0.1:5174/docs?mode=workflows Suggested status label: `status/in-progress`
zemion commented 2026-07-09 15:31:09 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Reworked the docs Help Center from mode switches to an audience toggle plus collapsible navigation tree.
  • Each tree node now opens a page with a right-side page outline; related topics link to the corresponding page.
  • Moved the help center surface onto the existing off-white panel tone.

Changed Files

  • webui/src/features/docs/DocsPage.tsx
  • webui/src/i18n/generatedTranslations.ts
  • ../govoplan-core/webui/src/styles/layout.css

Verification

  • govoplan-docs: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context
  • govoplan-core: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available
  • govoplan-core/webui: npm run build

Next / Blocked

  • Review current seeded topics and add missing workflow/reference/pattern content per module.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Reworked the docs Help Center from mode switches to an audience toggle plus collapsible navigation tree. - Each tree node now opens a page with a right-side page outline; related topics link to the corresponding page. - Moved the help center surface onto the existing off-white panel tone. ### Changed Files - `webui/src/features/docs/DocsPage.tsx` - `webui/src/i18n/generatedTranslations.ts` - `../govoplan-core/webui/src/styles/layout.css` ### Verification - `govoplan-docs: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context` - `govoplan-core: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available` - `govoplan-core/webui: npm run build` ### Next / Blocked - Review current seeded topics and add missing workflow/reference/pattern content per module. Suggested status label: `status/in-progress`
zemion commented 2026-07-09 15:44:36 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Adjusted the Help Center tree so navigation no longer exposes workflow/reference/pattern as top-level categories.
  • Tree nodes are now all clickable pages; the chevron alone expands and collapses children.
  • The tree renderer supports nested topic nodes through topic parent metadata.

Changed Files

  • webui/src/features/docs/DocsPage.tsx
  • webui/src/i18n/generatedTranslations.ts
  • ../govoplan-core/webui/src/styles/layout.css

Verification

  • govoplan-docs: git diff --check -- webui/src/features/docs/DocsPage.tsx webui/src/i18n/generatedTranslations.ts
  • govoplan-core: git diff --check -- webui/src/styles/layout.css
  • govoplan-docs: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context
  • govoplan-core: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available
  • govoplan-core/webui: npm run build

Next / Blocked

  • Review the resulting module/topic tree in the running UI and decide which content branches should be renamed or seeded first.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Adjusted the Help Center tree so navigation no longer exposes workflow/reference/pattern as top-level categories. - Tree nodes are now all clickable pages; the chevron alone expands and collapses children. - The tree renderer supports nested topic nodes through topic parent metadata. ### Changed Files - `webui/src/features/docs/DocsPage.tsx` - `webui/src/i18n/generatedTranslations.ts` - `../govoplan-core/webui/src/styles/layout.css` ### Verification - `govoplan-docs: git diff --check -- webui/src/features/docs/DocsPage.tsx webui/src/i18n/generatedTranslations.ts` - `govoplan-core: git diff --check -- webui/src/styles/layout.css` - `govoplan-docs: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context` - `govoplan-core: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available` - `govoplan-core/webui: npm run build` ### Next / Blocked - Review the resulting module/topic tree in the running UI and decide which content branches should be renamed or seeded first. Suggested status label: `status/in-progress`
zemion commented 2026-07-09 16:06:46 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Added a human-facing documentation taxonomy to the Help Center tree: About GovOPlaN, Working with GovOPlaN, Advanced, Modules, admin-only Administration, and conditional Troubleshooting and support.
  • Working with GovOPlaN is a nested branch with Basics and Common tasks, so workflow/pattern remain internal rendering metadata instead of navigation categories.
  • Modules remains a top-level overview with per-module subtrees; topic parent metadata still supports deeper nesting.

Changed Files

  • webui/src/features/docs/DocsPage.tsx
  • webui/src/i18n/generatedTranslations.ts

Verification

  • govoplan-docs: git diff --check -- webui/src/features/docs/DocsPage.tsx webui/src/i18n/generatedTranslations.ts
  • govoplan-docs: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context
  • govoplan-core: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available
  • govoplan-core/webui: npm run build

Next / Blocked

  • Review category names in the running UI, then seed missing content under each branch.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Added a human-facing documentation taxonomy to the Help Center tree: About GovOPlaN, Working with GovOPlaN, Advanced, Modules, admin-only Administration, and conditional Troubleshooting and support. - Working with GovOPlaN is a nested branch with Basics and Common tasks, so workflow/pattern remain internal rendering metadata instead of navigation categories. - Modules remains a top-level overview with per-module subtrees; topic parent metadata still supports deeper nesting. ### Changed Files - `webui/src/features/docs/DocsPage.tsx` - `webui/src/i18n/generatedTranslations.ts` ### Verification - `govoplan-docs: git diff --check -- webui/src/features/docs/DocsPage.tsx webui/src/i18n/generatedTranslations.ts` - `govoplan-docs: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest tests.test_docs_context` - `govoplan-core: PYTHONPATH=/mnt/DATA/git/govoplan-core/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-docs/src:/mnt/DATA/git/govoplan-tenancy/src ./.venv/bin/python -m unittest tests.test_api_smoke.ApiSmokeTests.test_docs_context_and_ops_status_are_available` - `govoplan-core/webui: npm run build` ### Next / Blocked - Review category names in the running UI, then seed missing content under each branch. Suggested status label: `status/in-progress`
zemion added the
module/docs
 label 2026-07-10 19:50:59 +02:00
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/deployment
Deployment, release, operations, or runtime packaging.
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/approvals
GovOPlaN Approvals module behavior or integration.
module/assets
GovOPlaN Assets module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/booking
GovOPlaN Booking 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/certificates
GovOPlaN Certificates module behavior or integration.
module/committee
GovOPlaN Committee module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/consultation
GovOPlaN Consultation module behavior or integration.
module/contracts
GovOPlaN Contracts module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/docs
GovOPlaN documentation layer behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/facilities
GovOPlaN Facilities 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/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
module/grants
GovOPlaN Grants module behavior or integration.
module/helpdesk
GovOPlaN Helpdesk 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/inspections
GovOPlaN Inspections module behavior or integration.
module/issue-reporting
GovOPlaN Issue Reporting module behavior or integration.
module/learning
GovOPlaN Learning 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/procurement
GovOPlaN Procurement module behavior or integration.
module/records
GovOPlaN Records module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/resources
GovOPlaN Resources 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/transparency
GovOPlaN Transparency module behavior or integration.
module/web
GovOPlaN public website, product page, or publication content.
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/module-roadmap
Created from GovOPlaN module and integration roadmap planning.
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/api
area/docs
area/webui
codex/ready
module/docs
status
ready
type
feature
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: add-ideas/govoplan-docs#15
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?