[Feature] Explain module maturity, source authority, and institutional boundaries #19

Closed
opened 2026-08-01 00:00:54 +02:00 by zemion · 2 comments
Owner

Outcome

Let users, administrators, operators, and auditors understand the effective configured architecture instead of inferring it from installed repository names.

Parent: GovOPlaN/govoplan#29
Depends on: GovOPlaN/govoplan-core#279

Scope

Project architecture layer/kind, evidence-backed maturity, owned/non-owned concepts, source-authority mode, provider maturity/health/limits, known gaps, reference packages, and inspection/recovery links from module manifests and runtime providers.

Acceptance criteria

  • Role-aware pages distinguish installed, enabled, configured, target-tested, supported, and unavailable capabilities.
  • Source authority and external-system outage/conflict behavior are visible where relevant.
  • Missing candidate modules do not advertise functionality, but configured compatibility modes are explained.
  • Protected object metadata and diagnostics remain permission- and purpose-filtered.
  • Static user/admin baselines and configured/evidence layers remain valid in module permutations.
## Outcome Let users, administrators, operators, and auditors understand the effective configured architecture instead of inferring it from installed repository names. Parent: https://git.add-ideas.de/GovOPlaN/govoplan/issues/29 Depends on: https://git.add-ideas.de/GovOPlaN/govoplan-core/issues/279 ## Scope Project architecture layer/kind, evidence-backed maturity, owned/non-owned concepts, source-authority mode, provider maturity/health/limits, known gaps, reference packages, and inspection/recovery links from module manifests and runtime providers. ## Acceptance criteria - Role-aware pages distinguish installed, enabled, configured, target-tested, supported, and unavailable capabilities. - Source authority and external-system outage/conflict behavior are visible where relevant. - Missing candidate modules do not advertise functionality, but configured compatibility modes are explained. - Protected object metadata and diagnostics remain permission- and purpose-filtered. - Static user/admin baselines and configured/evidence layers remain valid in module permutations. <!-- codex-docs-architecture-authority-projection-2026-07-31 -->
Author
Owner

Codex State: progress

Summary

  • Docs now projects module layer/kind, maturity/evidence, ownership boundaries, known limits, source-authority modes, provider behavior, and reference packages into role-aware architecture/provider pages and summaries.
  • Static baselines remain conditional and protected provider diagnostics are not copied into public documentation payloads.

Verification

  • Docs backend suite: 18 passed; workspace module permutation validation passed.

Next / Blocked

  • Wire broader configured provider bindings and live health/freshness results into the runtime projection before treating declared provider support as an effective configured state.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Docs now projects module layer/kind, maturity/evidence, ownership boundaries, known limits, source-authority modes, provider behavior, and reference packages into role-aware architecture/provider pages and summaries. - Static baselines remain conditional and protected provider diagnostics are not copied into public documentation payloads. ### Verification - `Docs backend suite: 18 passed; workspace module permutation validation passed.` ### Next / Blocked - Wire broader configured provider bindings and live health/freshness results into the runtime projection before treating declared provider support as an effective configured state. Suggested status label: `status/in-progress`
zemion added
status
in-progress
and removed
status
ready
labels 2026-08-01 03:35:44 +02:00
Author
Owner

Codex State: done

Summary

  • Docs now projects evidence-backed architecture/provider declarations and tenant-aware configured provider state.
  • User projections omit binding identifiers and diagnostics; admin projections retain sanitized binding health, freshness, conflict, and recovery details.

Changed Files

  • src/govoplan_docs/backend/api/v1/routes.py
  • webui/src/features/docs/DocsPage.tsx
  • README.md

Verification

  • 19 Docs tests and workspace TypeScript compile passed; module permutations remain covered by Core.
## Codex State: done ### Summary - Docs now projects evidence-backed architecture/provider declarations and tenant-aware configured provider state. - User projections omit binding identifiers and diagnostics; admin projections retain sanitized binding health, freshness, conflict, and recovery details. ### Changed Files - `src/govoplan_docs/backend/api/v1/routes.py` - `webui/src/features/docs/DocsPage.tsx` - `README.md` ### Verification - `19 Docs tests and workspace TypeScript compile passed; module permutations remain covered by Core.`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-docs#19