[Feature] Add reporting visualization and publication providers #6

Open
opened 2026-07-30 18:17:54 +02:00 by zemion · 1 comment
Owner

Context

Add charts and durable report publication after the semantic and interactive table layers exist.

Acceptance criteria

  • Define a chart renderer provider contract independent of one charting library.
  • Ship an accessible bounded initial chart catalogue with tabular fallbacks.
  • Let modules announce additional renderers without direct imports.
  • Support saved chart views and Dashboard contributions.
  • Schedule immutable report revisions with bound parameters and source freshness checks.
  • Publish idempotently through declared Files, Mail, or other target capabilities and retain delivery evidence.
  • Keep unavailable optional targets visible only with an actionable capability explanation.

Depends on #5. Architecture reference: docs/SUPERX_CAPABILITY_ASSESSMENT.md.

## Context Add charts and durable report publication after the semantic and interactive table layers exist. ## Acceptance criteria - [ ] Define a chart renderer provider contract independent of one charting library. - [ ] Ship an accessible bounded initial chart catalogue with tabular fallbacks. - [ ] Let modules announce additional renderers without direct imports. - [ ] Support saved chart views and Dashboard contributions. - [ ] Schedule immutable report revisions with bound parameters and source freshness checks. - [ ] Publish idempotently through declared Files, Mail, or other target capabilities and retain delivery evidence. - [ ] Keep unavailable optional targets visible only with an actionable capability explanation. Depends on #5. Architecture reference: `docs/SUPERX_CAPABILITY_ASSESSMENT.md`.
Author
Owner

Codex State: progress

Summary

  • The renderer-neutral chart model, mandatory accessible table fallback, saved visualization state, schedules, immutable publication records, idempotent publication capability, evidence retention and unavailable-capability handling are implemented locally.

Verification

  • 7 Reporting tests passed; Ruff passed; Core WebUI production build passed.

Next / Blocked

  • Retain this issue for richer concrete chart renderer packages, Dashboard widget contributions, and first Files/Mail publication adapters with target delivery/recovery evidence.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - The renderer-neutral chart model, mandatory accessible table fallback, saved visualization state, schedules, immutable publication records, idempotent publication capability, evidence retention and unavailable-capability handling are implemented locally. ### Verification - `7 Reporting tests passed; Ruff passed; Core WebUI production build passed.` ### Next / Blocked - Retain this issue for richer concrete chart renderer packages, Dashboard widget contributions, and first Files/Mail publication adapters with target delivery/recovery evidence. Suggested status label: `status/in-progress`
zemion added
status
in-progress
and removed
status
ready
labels 2026-08-01 14:56: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-reporting#6